coulomb/shard-wiki
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
shard-wiki/spec
History
tegwick a2f15806f5 spec(SHARD-WP-0001): yawex-derived federation requirements (ADR-01..06); workplan done 
Delivers spec/FederationRequirements.md — six ADR-ready design notes mapping
the yawex prior art onto the hardened CoreArchitectureBlueprint:
ADR-01 cross-shard resolution (yawex PageLookUp states as a checklist, keyed
on identity), ADR-02 namespace/path + shard roles (path=placement not identity),
ADR-03 derived views core-vs-adapter (BackLinks/RecentChanges/AllPages/SiteMap
core, Search hybrid), ADR-04 concrete provenance envelope fields, ADR-05 overlay/
patch/append lifecycle, ADR-06 wikilink+red-link extension (model core, render UI).
Resolves findings open-Qs #1-#3; access-model thread ratified. Flips WP-0001 done.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 02:19:43 +02:00
..
ArchitectureBlueprint.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
CoreArchitectureBlueprint.md spec(SHARD-WP-0006 T5): track §C as O-8..O-12; refresh decisions/traceability; close-out 2026-06-15 02:03:58 +02:00
FederationRequirements.md spec(SHARD-WP-0001): yawex-derived federation requirements (ADR-01..06); workplan done 2026-06-15 02:19:43 +02:00
ProductRequirementsDocument.md spec: promote federation UCs; add SHARD-WP-0002 architecture workplan 2026-06-08 14:55:13 +02:00
README.md spec(SHARD-WP-0001): yawex-derived federation requirements (ADR-01..06); workplan done 2026-06-15 02:19:43 +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: Strudel.cc live-coding REPL deep dive; SHARD-WP-0004 T5 2026-06-15 00:04:16 +02:00

README.md

spec/

Specification files that guide and guardrail implementation.

Background on document types: InfoTechPrimers on coulomb.social.

File Status Role
CoreArchitectureBlueprint.md draft for review Whole-system architecture — layers, abstractions, load-bearing decisions (synthesised from all research)
FederationRequirements.md draft for review yawex-derived union/federation design notes — resolution, namespace, derived views, provenance, overlay, links (ADR-01…06; SHARD-WP-0001)
ProductRequirementsDocument.md draft scaffold What the product must deliver
TechnicalSpecificationDocument.md draft scaffold How the system is built
UseCaseCatalog.md draft 84 use cases promoted from c2 + yawex + ~23-system research
ArchitectureBlueprint.md draft Access, history, and identity sub-blueprint (the L0–L4 authorization ladder; referenced by CoreArchitectureBlueprint §9)

Promote material from research/ and reviewed items from demand/ into spec before treating it as implementation authority.