Files

tegwick dbc42f05db research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77

SHARD-WP-0003 T5. The home case: a forge wiki is a separate .wiki.git repo of
Markdown -> page model, history, coordination journal map 1:1 with near-zero
adapter. git-clone universal across all three; wiki content API
capability-varying (GitLab/Gitea yes, GitHub git-only). git IS the canonical
store (not a mirror), so write-by-commit is safe -- resolves the UC-68/Q22
race for this case. UC-76 (clone .wiki.git attach), UC-77 (forge wiki API,
capability varies). Enriched UC-40/02/68/38. Marks T5 done.
Feeds SHARD-WP-0002 T14/T11.

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

2026-06-14 19:40:46 +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: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77

2026-06-14 19:40:46 +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.