Files

tegwick e0c3d0699c research: MojoMojo deep dive (Perl Catalyst DB-backed wiki); UC-81

SHARD-WP-0003 T8. Classic relational-DB-backed wiki: Catalyst/DBIx::Class app,
pages + path tree + full history in SQL tables, Markdown body in a column, no
file store and no content API. Anchors the direct-DB-read binding (map schema
-> page model + journal); DB version rows = a third history source beside git
commits and RCS files. UC-81. Enriched UC-02/40/36/34. Marks T8 done.
Feeds SHARD-WP-0002 T14/T13/T11.

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

2026-06-14 20:54:40 +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: MojoMojo deep dive (Perl Catalyst DB-backed wiki); UC-81

2026-06-14 20:54:40 +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.