spec: CoreArchitectureBlueprint — whole-system architecture from research

The optimal architecture synthesised from INTENT + the full research arc:
- Thesis: canonical at the edges, derived in the middle (orchestrator not engine)
- Dual narrow waist: adapter contract (15 capability spectra) + page model
- 6 layers + provenance/capability rails; L4 union/projection is a rebuildable cache
- Federation-model taxonomy (plural/composable); two-axis projection model;
  moldable view registry; identity != placement; computational content in scope
  as page-model+projection, out as execution platform
- Concrete src/ module layout with downward-only dependency rule
- Canonical data flows; policy surface; tradeoffs; full traceability to INTENT/UCs
References ArchitectureBlueprint.md as the L5 authorization sub-blueprint.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

spec/README.md

@@ -6,10 +6,11 @@ Background on document types: InfoTechPrimers on coulomb.social.
 
 | File | Status | Role |
 |------|--------|------|
+| `CoreArchitectureBlueprint.md` | draft for review | **Whole-system architecture** — layers, abstractions, load-bearing decisions (synthesised from all research) |
 | `ProductRequirementsDocument.md` | draft scaffold | What the product must deliver |
 | `TechnicalSpecificationDocument.md` | draft scaffold | How the system is built |
-| `UseCaseCatalog.md` | draft | 25 use cases promoted from c2 + yawex research |
-| `ArchitectureBlueprint.md` | draft | Access, history, and identity architecture |
+| `UseCaseCatalog.md` | draft | 84 use cases promoted from c2 + yawex + ~23-system research |
+| `ArchitectureBlueprint.md` | draft | Access, history, and identity sub-blueprint (the L0–L4 authorization ladder; referenced by CoreArchitectureBlueprint §9) |
 
 Promote material from `research/` and reviewed items from `demand/` into spec
 before treating it as implementation authority.