generated from coulomb/repo-seed
tegwick
08a2148079
Resolves B-1+B-3. Coordination-canonical state = an append-only decision log in the git journal (events: overlay/binding/alias/merge); queryable current state = a derived fold (tier-3, indexed). Concurrency: one append authority per space (lease/leader) → totally-ordered per-space log, read-your-writes across instances, HA via re-grantable lease, partition yields to log integrity. Updates §1, §4, §8.1, §8.6, §11. I-6 strengthened (coordination state is now git-addressable history/patch/review), not bypassed. 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.