Reorder architecture sidebar using weights: stages first, then foundation, epistemology, design, implications, reference

- Add :WEIGHT: extraction to build script (from Org PROPERTIES into Hugo TOML frontmatter)
- Shorten architecture _index.org staged progression to a single-line summary pointing to stages/ directory
- Weight order (sidebar now reads in this order):
  stages/ (10-20) — the roadmap, early so references make sense
  lisp-foundation.org (21) — why Lisp
  knowledge-layers/ (30-32) — how the system knows
  design-decisions through neuro-comparison (40-45) — design
  systemic-effects (50) — implications
  org-knowledge-base through repo-organization (60-64) — reference
- Rebuild: 148 files, 0 errors

projects/passepartout/architecture/_index.org

@@ -130,16 +130,9 @@ The social protocol is not a blockchain. DAG-based ordering handles causality; d
 
 **The staged progression.**
 
-The full architecture — gate-verified Lisp machine on custom silicon — is the destination. The staged roadmap describes how each successive replacement eliminates a class of threat:
+The full architecture — gate-verified Lisp machine on custom silicon — is the destination. The staged roadmap (see the [[file:/stages.org][stages]] directory for full detail) describes how each successive replacement eliminates a class of threat:
 
-- Stage 0: Conventional Linux, Python agent (Hermes), SQLite knowledge store (gbrain). The starting point. Zero days exist; patches are manual.
-- Stage 1: Message-level authentication via the social protocol. Communication becomes provable.
-- Stage 2: The gate operates as a software layer over the host OS. Shell commands, LLM proposals, and network messages all pass through the same decision procedure. Root is eliminated as an attack path.
-- Stage 3: The host OS is replaced by a bare-metal Lisp image. One address space, one evaluator, no MMU to attack.
-- Stage 4: LLM inference moves into the Lisp process. No API calls across network boundaries. The LLM becomes a function in the same evaluated graph.
-- Stage 5: Neural weights stored as plist-native data structures. The gap between symbolic and neural representations closes.
-- Stage 6: Verified fine-tuning. Every weight update is gate-checked against policy.
-- Stage 7: What remains. Physical theft, electronic warfare, holes in the specification itself, and the fallibility of the LLM oracle. Limits of computation, not of this design.
+Stage 0 (current: Linux + Python agent + SQLite), Stage 1 (social protocol + provable communication), Stage 2 (the gate as software — root eliminated), Stage 3 (bare-metal Lisp image — no MMU), Stage 4 (in-process LLM inference), Stage 5 (neural weights as plist data), Stage 6 (verified fine-tuning), Stage 7 (what remains — physical, political, oracular limits).
 
 Each stage is independently useful. Stage 0 is running today. The migration is progressive component swap, not a cut-over.