coulomb/shard-wiki
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
shard-wiki/spec
History
tegwick 1ad70a9c8a spec(SHARD-WP-0006 T4): incremental-equivalence correctness + I-2 verification (§8.7) 
Fixes B-4. Incremental delta is not additive: a change processes bucket
exits (retract unsupported edges) + entries (add) + propagation across
equivalence neighbours, not just new candidates. Adds an I-2 verification
mechanism: per-partition Merkle-style digest + background consistency-checker
vs sampled fold → scoped self-healing recompute on drift. I-2 now
eventually-verified, not asserted.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 02:02:33 +02:00
..
ArchitectureBlueprint.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
CoreArchitectureBlueprint.md spec(SHARD-WP-0006 T4): incremental-equivalence correctness + I-2 verification (§8.7) 2026-06-15 02:02:33 +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: CoreArchitectureBlueprint — whole-system architecture from research 2026-06-15 00:41:14 +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)
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.