generated from coulomb/repo-seed
tegwick
0ee972f2e2
Headless, API-first, agent-optimized native engine = canonical-mode shard backend. Thesis: a page-store kernel with a typed-extension runtime; everything beyond the c2-minimum is a typed extension activated per shard, and the shard's §A capability profile is DERIVED from its active extensions (configuration->capability->conformance). 9 engine invariants (engine-is-one-shard, small kernel, per-shard activation, profile-from-extensions, headless/agent-first, reuse-not-reinvent, typed+verified). Kernel (4 concepts), typed-extension model (typed hooks + deterministic composition + feature-control activation), T2 featureset/conflict-mediation realized, engine-as-shard, agent-first API surface, module sketch, reuse (consumes feature-control/authorization; G1 framework proposal), traceability, decisions/open, stability note. Marks T5 done. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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) |
FederationArchitecture.md |
draft for review | federation design — what the union does: T1–T10 decision records + the federation-model taxonomy (SHARD-WP-0002) |
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 + §A | How the system is built; §A = the normative shard adapter contract (T11–T16, T18; SHARD-WP-0002) |
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.