generated from coulomb/repo-seed
tegwick
802a80231a
Decision records for the 10 federation topics + the federation-model taxonomy, each with a Decided/Deferred/Open footer: star orchestrator positioning, remix primitives (overlay-default), identity/placement/equivalence + chorus, event-sourced coordination journal + per-space append authority, server-primary incremental union, notify-driven freshness, space lifecycle, reference-not-copy transclusion, detection-core/resolution-policy preset catalog, the federation- ops capability matrix, and the six selectable/composable federation models. References (not duplicates) CoreArchitectureBlueprint + FederationRequirements. 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) |
FederationRequirements.md |
draft for review | yawex-derived union/federation design notes — resolution, namespace, derived views, provenance, overlay, links (ADR-01…06; SHARD-WP-0001) |
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.