generated from coulomb/repo-seed
Fixes B-3/C-3. §9.1 structural per-tenant partitioning of the derived tier (no shared cross-tenant cache; read-time filtering as defence-in-depth; reconciles I-2+L5 per partition); new invariant I-13. §8.1 history stays recoverable AND bounded (gc/repack, squash-compaction of churn preserving recoverable endpoints, per-shard offload, anti-abuse hooks). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
spec/
Specification files that guide and guardrail implementation.
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 | 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.