generated from coulomb/repo-seed
tegwick
04be66161e
Fixes bug B-2. States the guarantee (read-your-writes for journal-owned coordination-canonical state; causal across the derived tier; eventual+ freshness-labelled for sharded inputs). Conflict detection+representation = core mechanism, resolution = policy. Overlay-apply-under-drift semantics (fast-forward / three-way / refuse+re-present) and journal ordering. 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.