Files
shard-wiki/spec
tegwick fa7adab239 research: Foswiki deep dive (store abstraction, ext API); UC-42/43
Deep dive into Foswiki focused on its deltas from TWiki (not the shared
lineage): the pluggable Foswiki::Store backend (RcsWrap/RcsLite/PlainFile)
behind a versioned interface via Foswiki::Meta, the OO/MVC core rewrite,
Foswiki::Func + registerTagHandler, DataForms + MetaDataPlugin multi-record,
and WysiwygPlugin TML<->HTML round-trip. The store abstraction is logged as
prior art for shard-wiki's own adapter contract (SHARD-WP-0002).

Catalog (now 43 UCs):
- UC-42 read/write a non-Markdown shard via lossless syntax translation
  (Markdown-first for prose; Foswiki WysiwygPlugin is proof)
- UC-43 tolerate a shard's storage-backend swap (RCS<->PlainFile) under a
  stable identity
- enrich UC-39 (multi-record metadata) and UC-40 (PlainFile direct-attach)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-13 23:27:24 +02:00
..

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.