Files

tegwick 036dbad816 research: Federated Wiki deep dive (journal/fork/neighborhood); UC-70-72

SHARD-WP-0003 T1. Federation model (not a shard candidate): per-page
append-only semantic-action journal with story as derived replay,
fork-with-site-provenance, neighborhood/roster discovery + chorus of forks.
Prior art for shard-wiki's own pillars: coordination journal (UC-71),
overlay-before-mutation (UC-26 fork), union-without-erasure (UC-72).
Attach as REST/file-store hybrid (page JSON + CORS, UC-70). Feeds
SHARD-WP-0002 T1-T5, T11, T13, T16.

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

2026-06-14 19:01:13 +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: Federated Wiki deep dive (journal/fork/neighborhood); UC-70-72

2026-06-14 19:01:13 +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.