History

tegwick f21b7b5259 spec(SHARD-WP-0005 T9): known scaling risks & open problems; close-out Adds §12 'Known scaling risks & open problems' (O-1..O-7 with chosen direction + revisit trigger); renumbers §13-17. Refreshes §14 decisions (several earlier 'open' items now decided), §16 traceability (links the review + per-finding section map), and I-1..I-13. Flips SHARD-WP-0005 done. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-15 01:43:14 +02:00
..
ArchitectureBlueprint.md	Reorganize documentation into canonical repository layout	2026-06-08 13:55:27 +02:00
CoreArchitectureBlueprint.md	spec(SHARD-WP-0005 T9): known scaling risks & open problems; close-out	2026-06-15 01:43:14 +02:00
ProductRequirementsDocument.md	spec: promote federation UCs; add SHARD-WP-0002 architecture workplan	2026-06-08 14:55:13 +02:00
README.md	spec: CoreArchitectureBlueprint — whole-system architecture from research	2026-06-15 00:41:14 +02:00
TechnicalSpecificationDocument.md	Promote c2 and yawex research into UseCaseCatalog (UC-01–UC-25)	2026-06-08 14:14:46 +02:00
UseCaseCatalog.md	research: Strudel.cc live-coding REPL deep dive; SHARD-WP-0004 T5	2026-06-15 00:04:16 +02:00

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.