Bitspark constellation

DECISIONS

Architecture decision records

The cross-cutting decisions that shape how the constellation is built and relates — each one a record of context, the choice, and its consequences. Listed from atlas's adr/.

0001 atlas: a cross-repo structure layer, orthogonal to design
accepted

2026-06-02

0002 repo manifests: each system declares its own place and edges
accepted

2026-06-02

0003 errata for 0001/0002, and the cross-repo docs graph
accepted

2026-06-03

0004 substrate-release coordination: a publisher-emitted release BOM + verified per-repo adoption
accepted

2026-06-04

0005 topology-driven views & cross-repo propagation: generate the invariant shape, author the lesson, lint the seam
accepted

2026-06-04

0006 continuous substrate channels: auto-minted content-addressed releases + a moving channel pointer + an automated co-resolution loop
accepted

2026-06-04

0007 Substrate releases are atomic and convergent: one logical version per component, every dependent on it, every ecosystem published together
accepted

2026-06-04

0008 substrate release model (expert-refined): component & constellation releases, signed channel pointers, atomic advertisement, scoped-expiring skew exceptions, the release verdict, and the catalog-epoch trust root
accepted

2026-06-04

0009 the pin trinity: one per-repo lock + one `pin explain` for the design / atlas / substrate refs a repo runs against
accepted

2026-06-04

0010 the three coupling planes: live release metadata / a pinned verifier protocol / actuators on a release train
proposed

2026-06-07

0011 the constellation is a generated evidence ledger: collect / normalize / compare / report, never invent
accepted

2026-06-07

0012 the substrate-theory basis, and where the constellation's constitution lives
proposed

2026-06-07

0013 capability and realization as candidate theories; artifact folded into realization
proposed

2026-06-07

0014 the unified development process: vendored byte-identity for identity-critical files, linted convention for locally-varying files, one drift gate
proposed

2026-06-09

0015 cross-repo issue orchestration: native cross-repo sub-issues supersede the prose `Part of` convention
proposed

2026-06-09

0016 stele is the fact substrate; arche decomposes into primitive services
accepted

2026-06-10

0017 the adstrate: the off-record referent tier (CAS, cell, wire)
accepted

2026-06-13

0018 the adstrate becomes first-class: `layer: "adstrate"` + the Latin naming convention
accepted

2026-06-13

0019 private members render in the public projections without a dead repo link
accepted

2026-06-13

0020 release tags are off-main, immutable, and BOM-anchored
accepted

2026-06-14

0021 adstrate access is space-governed: reach the payload only through its spaced binding
accepted

2026-06-14

0022 adstrate storage is space-partitioned: the space owns the bytes, not just the binding
accepted

2026-06-14

0023 release identity is the content digest; the epoch date is an atlas-owned label
accepted

2026-06-14

0024 adstrate writes go through the fact interface too: the caller binds, the occupant confirms custody
accepted

2026-06-14

0025 producer announcements are append-only content-addressed events; the BOM is their materialized projection
accepted

2026-06-15

0026 the runtime plane: per-environment desired-state lives in atlas, in `runtime.json`, in place
accepted

2026-06-14

0027 0027 — release-identity vocabulary: the *component release* is the atomic unit; a repo tag is only a batch label
accepted

2026-06-17

0028 the authority model is single-root: one logical truth, no operational authority; federation is subtree delegation
accepted

2026-06-18

0029 the adstrate is the integration runtime (kosmos); providers are connected services
accepted

2026-06-18

0030 authority is fact-derived and decided once by the runtime; a provider is a pure realizer
accepted

2026-06-18

0031 the runtime control plane is a fact-derived judgment–realization loop: fact-executed before fact-authored, durable before autonomous
accepted

2026-06-20

0032 the service base API: a uniform `…z` + identity surface every member serves
accepted

2026-06-21

0033 the live plane is substrate-native: subscribe to stele `watch` for facts; per-service buses publish only rebuildable projections, never authoritative fact logs
proposed

2026-06-21

0034 logos-db is a theory-agnostic engine; theories attach per-judgment through one seam
proposed

2026-07-01

0035 the constellation namespace: top-level space allocation is registry-governed
proposed

2026-07-03

The Bitspark constellation — how the systems are built and relate.

GitHub