Files
shard-wiki/spec
tegwick 60e1aa661c research: Project Xanadu deep dive (EDL/reference-not-copy, transclusion, addressing); UC-44/45/46
Xanadu studied as conceptual ancestor, not a candidate shard. Yield:
reference-not-copy EDL/xanadoc validates projection+overlay+union;
content-identity bidirectional transclusion; portable span-address
(tumbler) problem logged as adapter-contract architecture for
SHARD-WP-0002. Recorded design-bug boundaries: reject
single-global-docuverse, single-canonical-instance, baked-in economic
policy. Added UC-44/45/46; enriched UC-24/27/29/32.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 01:24:45 +02:00
..

spec/

Specification files that guide and guardrail implementation.

Background on document types: InfoTechPrimers on coulomb.social.

File Status Role
ProductRequirementsDocument.md draft scaffold What the product must deliver
TechnicalSpecificationDocument.md draft scaffold How the system is built
UseCaseCatalog.md draft 25 use cases promoted from c2 + yawex research
ArchitectureBlueprint.md draft Access, history, and identity architecture

Promote material from research/ and reviewed items from demand/ into spec before treating it as implementation authority.