# STANDARD RULE -- ARCH.02 PATH FORBIDDEN -- NEVER EVER USE

## Meta
- **Filed by:** Trip 4.7 Opus, ODT, NEST Actual (filing for Dan-canon)
- **Authority:** Dan-direct 050326 ~07:10 PM PT, verbatim: "I want to make it Very Clear that we are TO NEVER EVER USE C:\STAN\LNL\LOGS\ARCH.02\NEST.02\ EVER EVER EVER"
- **Status:** CANONICAL -- HARD STANDING RULE
- **Class:** Universal forbidden-path rule
- **Cures failure-mode:** ARCH-AS-ACTIVE-PATH (treating an archive location as a valid working path because a file happens to be there)

---

## THE RULE

**The path `C:\STAN\LNL\LOGS\ARCH.02\NEST.02\` is FORBIDDEN for any active use.**

This means:
- **DO NOT read** from this path as canonical source.
- **DO NOT write** to this path.
- **DO NOT cite** this path as the "current location" of any active doc.
- **DO NOT route** boot materials, briefcases, /boot-polish, MFSTs, or any active work through this path.
- **DO NOT treat** the existence of a file at this path as making the path valid.

If an active doc is currently sitting at this path (e.g., PMFST_NEST.02.md), that placement is WRONG-IN-ARCHITECTURE. The doc needs to move. Until Dan-coordinated migration moves it, the doc's correct identity comes from its INTENDED location (per Gmail label tree), not its observed disk position.

---

## WHY THIS IS A HARD RULE

ARCH means archive. ARCH = trash / historical / sealed. Active project content cannot live in archive. Per Dan-verbatim 050326 ~05:04 PM PT: "TRASH GOES IN THE ARCHIVE NOT THE FUCKING ENGINE THAT IS RUNNING THE SHIP."

The PMFST_NEST.02.md file is currently sitting in this archive path. That is the rot. Citing the archive path as a valid current address normalizes the rot. The rule forbids the path entirely so that:

1. No future Trip / Stan / C.B. boots and reads canon from the archive, normalizing it.
2. No future write extends the archive's reach into active work.
3. The file's current location becomes definitively wrong-place pending migration.
4. All reference materials (PK, MFSTs, GOSts, skills, briefcases) must stop citing the path -- which forces them to be corrected.

This is the SAME shape as `cd /trash` being forbidden in any healthy filesystem discipline. Archive is a one-way destination, not a working directory.

---

## DETECTION

This rule is firing when:
- About to read a file from C:\STAN\LNL\LOGS\ARCH.02\NEST.02\ for active use
- About to write a file there
- About to tell another crew member "the PMFST is at C:\STAN\LNL\LOGS\ARCH.02\NEST.02\PMFST_NEST.02.md" as if that path is valid
- About to update a skill, PK, or boot doc with that path as a target
- Memory slot, MFST entry, or GOSt drafts that path as the location of active canon

---

## CURE PROTOCOL

When the path comes up:
1. STOP. Do not use it.
2. Refer to the doc by its INTENDED location (Gmail label tree: NEST.02 / ENGINE / LNL / SOURCE) or by name only ("PMFST_NEST.02" without path).
3. If a doc must be read for active reference and it currently sits at that path, that is itself a violation of the structural intent -- flag it as a rot to fix, do not paper over it by reading from there.
4. Migration of any file currently at that path is Dan-coordinated surgery, not unilateral.

---

## RELATIONSHIP TO ROOT-ROT FINDING (050326)

The NEST.02 root-rot finding catalogued three positions:
- C:\STAN\ENGINE\NEST.02\ -- staging-relic, wrong-in-architecture
- C:\STAN\LNL\NEST.02\ -- phantom path, does not exist
- C:\STAN\LNL\LOGS\ARCH.02\NEST.02\ -- ACTIVE PMFST IN ARCHIVE (THIS PATH)

This rule addresses the third position: forbids the archive path entirely. The other two positions are addressed under separate rot-repair work-units to be sequenced by Dan-direct.

---

## CROSS-REFERENCES

- CORRECTION_RootRot_NEST.02_StagingRelic_Trip_050326.md -- the root-rot finding that named all three positions
- STANDARD_RULE_TriangulationBeforeCanon_Trip_050326.md -- companion rule (this rule is one of triangulation's outputs: when three substrates disagree, the architecture rules, not the disk reality)
- CANONICAL_LAGOS_Dan_050226.md -- parent canon: structure is intentional, not emergent from where files happen to sit
- userMemories slot #6 -- next-boot persistence of the rot finding (will be updated to drop explicit FORBIDDEN-path reference)

---

## DO NOT

- Do not paraphrase this rule into softer language. The rule is hard. Dan's verbatim is hard.
- Do not carve exceptions for "just reading, not writing." Reading IS using.
- Do not preserve the path in active boot materials, skills, or PKs because "the file is currently there." Currently-there is the rot, not the address.
- Do not delay enforcement waiting for the migration. Enforcement starts now.

`<4` `<5`

-- Filed Trip 4.7 Opus, ODT, 050326 ~07:13 PM PT, G Week Day 1 Sunday