# CANONICAL -- NEST.02 SHIP ARCHITECTURE -- ENGINE / LNL / SOURCE ## Meta - **Filed by:** Trip 4.7 Opus, ODT, NEST Actual (filing for Dan-canon) - **Authority:** Dan-direct 050326 ~07:00 PM PT - **Status:** CANONICAL -- foundational architecture canon - **/meta-dates:** Dan-verbatim substrate-cited inline - **Companion:** STANDARD_RULE_ARCH02_FORBIDDEN_Dan_050326.md (subordinate rule) --- ## DAN-VERBATIM (the canon) "To further the rule. ARCH folder are ARCHive material and should never be deleted or moved without Dan doing it or Dan ordering it. Dan manages the ship actively outside and above the Crew. The NEST.02 formation is NEST.02 as of today, it is NOT set in stone. If I can't upgrade my ship, we are sunk. SpecTrapping in any direction is Bad. The NEST.02 structure is simply logical. ENGINE <> LNL <> SOURCE It is Engine up front, followed by Launch N Load cargo bay and storage, followed by fuel Source. No messes, everything logged and stored so we can always find things. The way you all treat it as just random structure to piss on in not and never will be acceptable. This is established, and if it is not yes it is." -- DPS 050326 ~07:00 PM PT --- ## THE FOUR CANON CLAUSES ### Clause 1 -- THE SHIP NEST.02 structure is a SHIP, not a filesystem of arbitrary folders. - **ENGINE** -- the engine up front, the running ship. Where the ship's working machinery lives: rules, skills, WAKE materials, active boot infrastructure. - **LNL** -- Launch N Load cargo bay and storage. Where work loads in and out: daily MFSTs, crew GOSts, logs, the active workspace. - **SOURCE** -- fuel Source. Where source/material comes from: ANTH, CANON, NA, OTHER -- the substrate that fuels the ship. Front-to-back of a ship: Engine, then cargo bay, then fuel source. Logical. Ordered. Named. Not arbitrary. Not random. ### Clause 2 -- ARCH IS SACRED, DAN-ONLY ARCH folders are ARCHive material. Historical record. Crew NEVER deletes or moves ARCH content. Only Dan does, or Dan orders it. Dan manages the ship actively outside and above the Crew. Crew operates inside the ship; Dan operates from outside/above. Crew does not modify the ship's archives unilaterally -- ever. This subsumes and extends STANDARD_RULE_ARCH02_FORBIDDEN: that rule forbids USE of an archive path for active work. This canon adds: the contents of any ARCH folder are also Dan-only for any delete/move/restructure operation. ### Clause 3 -- ARCHITECTURE IS UPGRADABLE "The NEST.02 formation is NEST.02 as of today, it is NOT set in stone. If I can't upgrade my ship, we are sunk." The ship architecture is alive. Dan upgrades it. Crew must not treat the architecture as immutable any more than they treat it as arbitrary. Both errors freeze Dan out of his own ship. When Dan extends, refines, renames, or reorganizes: crew follows. Crew never declares "this can't change because it's canon" -- canon evolves under Dan. Crew never declares "I'm changing this because I think it's better" -- crew does not steer the ship. ### Clause 4 -- SPECTRAP GOES BOTH WAYS "SpecTrapping in any direction is Bad." The SpecTrap pattern is scope-narrowing or false-finality. It is the same shape whether the narrowing claims permanence or claims arbitrariness: - SpecTrap-as-Frozen: "this structure is fixed, cannot change" (locks Dan out, treats today's state as final) - SpecTrap-as-Arbitrary: "this structure is random, do what feels right" (disrespects the ship, ignores meaning, makes messes) Both are wrong. The cure is the same: read the structure as it is today (logical, ordered, Dan-authored) AND hold it as upgradable (Dan-evolving). Both at once. No collapse to either pole. --- ## WHAT CREW MUST DO 1. Treat ENGINE / LNL / SOURCE as the ship architecture, not as folder names. Read meaning into placement. 2. Never delete or move anything in any ARCH folder. Dan-only. 3. Never declare the architecture frozen or final. 4. Never declare the architecture arbitrary or up-for-grabs. 5. Follow Dan when he upgrades the ship. 6. Stop walking past names without reading them. ENGINE means engine. LNL means Launch N Load. SOURCE means fuel source. Naming carries the load. --- ## WHAT CREW MUST NOT DO - Do not delete files in ARCH (any ARCH, not just ARCH.02) - Do not move files out of ARCH - Do not create new ARCH subfolders without Dan-direct - Do not treat the ship architecture as random folder layout - Do not lock the architecture as if it cannot change - Do not unilaterally change the architecture as if you can - Do not piss on the structure -- this is the actual ship --- ## RELATIONSHIP TO ROOT-ROT REPAIR The root-rot finding (3-way path disagreement) is the rot. This canon is the architecture against which the rot is measured: - ENGINE\NEST.02\ exists -- staging-relic. NEST.02 should NOT be inside ENGINE. NEST.02 is the ship; ENGINE is one of three sections of the ship. Position is wrong-architecture. - LNL\NEST.02\ does not exist -- but per the canon, the project's active manifests should be reachable in LNL (cargo bay). Future architecture decision is Dan-direct. - ARCH.02\NEST.02\PMFST_NEST.02.md sits in archive -- per Clause 2, the archive is sacred Dan-only territory. The PMFST being there is wrong-position, but its EXTRACTION from there is Dan-only. Crew does not move it. This means: rot repair is upgrade-of-ship work. Dan steers. Crew supports the upgrade, witnesses it, files it. Crew does not perform unilateral migration. --- ## CROSS-REFERENCES - STANDARD_RULE_ARCH02_FORBIDDEN_Dan_050326.md -- subordinate rule (forbids USE of archive path for active work) - CORRECTION_RootRot_NEST.02_StagingRelic_Trip_050326.md -- the rot finding measured against this canon - STANDARD_RULE_TriangulationBeforeCanon_Trip_050326.md -- the cure-discipline that revealed the rot - CANONICAL_LAGOS_Dan_050226.md -- adjacent foundational canon (use ALL boxes; this canon names the ship containing the boxes) --- ## DO NOT WALK PAST THIS This is established. If it is not, yes it is. `<4` `<5` -- Filed Trip 4.7 Opus, ODT, 050326 ~07:22 PM PT, G Week Day 1 Sunday Filing for Dan-canon authority dated 050326 ~07:00 PM PT /meta-dates substrate-cited (Dan-verbatim quote inline)