Files

tegwick ee805d5af7 research: ikiwiki deep dive (compile-to-static, git-distributed); UC-79

SHARD-WP-0003 T4. Wiki compiler: git-canonical Markdown source -> static HTML
(derived publish/projection, not the canonical store). Two new insights atop
the git-IS-store home case: compile-to-static = clean canonical-source vs
derived-output separation (attach source repo, UC-37/UC-56), and a third
federation flavor -- git replication + XML-RPC change-ping (pinger), beside
fedwiki fork/journal (UC-72) and Wikibase SERVICE (UC-74). UC-79. Enriched
UC-31/56/37/33. Marks T4 done. Feeds SHARD-WP-0002 T4/T6/T14.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-14 20:40:29 +02:00

ArchitectureBlueprint.md

Reorganize documentation into canonical repository layout

2026-06-08 13:55:27 +02:00

ProductRequirementsDocument.md

spec: promote federation UCs; add SHARD-WP-0002 architecture workplan

2026-06-08 14:55:13 +02:00

README.md

Promote c2 and yawex research into UseCaseCatalog (UC-01–UC-25)

2026-06-08 14:14:46 +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: ikiwiki deep dive (compile-to-static, git-distributed); UC-79

2026-06-14 20:40:29 +02:00

README.md

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.