generated from coulomb/repo-seed
tegwick
0473c3f043
Mine the one research dir not yet promoted (260608-wikiengines-overview) into the catalog. Adds four heterogeneous-backend attachment scenarios the other research didn't surface: - UC-34 attach structured/semantic shard without lossy flattening (SMW, XWiki) - UC-35 attach shard with coarse write granularity (TiddlyWiki single-file) - UC-36 supply git-addressable history to internal-history engine (Confluence) - UC-37 attach static export as read-only backup shard (MediaWiki dump) Adds a `wikiengines` source token + traceability column and a wikiengines mapping subsection. The scan mostly reinforced existing UCs and the L0→L4 ladder; its main yield is adapter-contract constraints tracked in SHARD-WP-0002. 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 |
|---|---|---|
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.