generated from coulomb/repo-seed
tegwick
d65f9e21f3
Adds the normative Shard Adapter Contract as TechnicalSpecificationDocument §A: A.1 versioned capability contract (verbs + orthogonal-core spectra), A.2 verified conformance suite (profiles not self-asserted), A.3 attachment-mode taxonomy + image-is-not-a-store boundary, A.4 page model (incl. computational shapes, identity/placement/equivalence, layered provenance), A.5 history portability, A.6 syntax translation + fidelity report, A.7 addressing/navigation, A.8 gated computational content. Updates TSD references/UC-count/next-work. Flips all 18 WP-0002 tasks + workplan done. Design layer complete. 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) |
FederationArchitecture.md |
draft for review | federation design — what the union does: T1–T10 decision records + the federation-model taxonomy (SHARD-WP-0002) |
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 + §A | How the system is built; §A = the normative shard adapter contract (T11–T16, T18; SHARD-WP-0002) |
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.