Skip to content

History / 04 Solution Strategy

Revisions

  • ADR-061 (Proposed): operational κ-label composition surface over the Atlas's categorical operations Prism-runtime-level decision building on ADR-058 + ADR-059; no foundation or SDK change. Operationalizes ADR-059's five categorical operations on the Atlas image inside E₈ — product (G₂), quotient (F₄), filtration (E₆), augmentation (E₇), direct embedding (E₈) — as five ConstrainedTypeShapes in prism's standard type library (G2ProductShape<N> binary; the other four unary). A composition of N component κ-labels under an operation is a typed-input value the existing ψ-pipeline consumes through the existing σ-projection; the realization's canonicalize verb emits a canonical form whose κ-label is the composed κ-label — itself a κ-label, recursively composable (closed under the Atlas). Arity ≤ 3 / depth ≤ 8 per the Categorical X regime split (ADR-025) and ADR-059's H-/O-level bounds; wide compositions decompose via ConstraintRef::Recurse (ADR-057). σ-axis substitutability (ADR-047) and cross-substrate universality (ADR-058 + ADR-059) lift to compositions. Byte-concatenation / tree-hash composition rejected (collapses ADR-059's algebraic codomain to byte-pigeonhole). Substrate footprint: foundation unchanged (TypedCommitment per ADR-048 and ObservablePredicate per ADR-049 closed sets retained; no wire-format change), SDK unchanged, prism gains the five standard-type-library shapes; audit-trail row marked "No." Propagation: ADR-061 section + audit row + heading (ADR-038 through ADR-061) in ch 9 (lands on the Continued page, now ~322 KiB); composition shapes added to the ch 5 standard-type-library entry; ch 8 ADR-058/059 cluster extended with the composition-surface reading; ch 4 strategic row cross-ref; a "κ-label composition shapes" glossary entry. Applied domain-neutral per the wiki's discipline: the downstream content- addressing realization crate, its Lean module paths, and its realization roster are generalized to "a content-addressing realization (Layer-3 per ADR-031)"; format names (PNG/PDF/GGUF/ONNX/JSON) kept as illustrative domains only. Audit resolved, while applying: the source ADR's principle numbering gap ((1)(2)(4)(5)(6) → renumbered (1)–(6)); a dangling prism::std_types::RouteShape reference (generalized to "route-declaration shapes," no such type in the wiki); and grounded "Categorical X" in the existing ADR-025 regime split (T=3 H-level, O=8 O-level) rather than as a free-floating theorem name. All eight validators (V1–V8) pass; page-size guard OK (glossary at 494 KiB — warning band, under the 512 KiB limit). Status: Proposed (as authored). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 23, 2026
  • ADR-060: source-polymorphic value carrier — remove the contrived 4096 byte-width caps and DefaultHostBounds Lands the foundation 0.5.0 architectural change diagnosing the 4096-byte carrier ceiling as a stable-Rust workaround (a pinned literal absent generic_const_exprs) whose application-overridability was fictional (foundation internals read the width through the hardcoded DefaultHostBounds path). Implementer-feedback-loop: ADR-037's byte-width-cap family proved unrealizable as committed, so ADR-060 supersedes it. ADR-060 (new, ch 9) commits: - TermValue becomes source-polymorphic TermValue<'a, const INLINE_BYTES: usize> (Inline / Borrowed / Stream). Inline width foundation-derived via carrier_inline_bytes::<B>() = max(Witt-literal width, fingerprint width, kappa-label ASCII width). Borrowed/Stream carriers have no byte-width ceiling; Stream(&'a dyn ChunkSource) admits unbounded payloads (multi-GB tensor data, large attestation envelopes, production canonical-JSON). - 12 byte-width capacity constants removed from HostBounds (TERM_VALUE_MAX_BYTES, AXIS_OUTPUT_BYTES_MAX, ROUTE_INPUT/OUTPUT_BUFFER_BYTES, 8 psi-stage *_OUTPUT_BYTES_MAX); per-psi-stage carrier widths derive from foundation const fns. HostBounds drops 26 -> 14 associated constants. - DefaultHostBounds removed; every application declares its own impl HostBounds. - 8 psi-stage resolver traits return a TermValue (not writer-style &mut [u8]); streaming-sigma-projection is now a foundation-level surface. - Wire format unchanged (kappa-label/trace/certificate byte-identical); no shim. Reconciled three internal inconsistencies in the source document against the wiki's authoritative ADR-037 starting count (26 = 4 pre-ADR-018 + 22 migrated): the removed set is 12 (not the doc's "11"), the retained set is 14 (not "13"), and carrier_inline_bytes is a 3-term max including the kappa-label width (the doc's 2-term max self-contradicts its own validation point 9, which admits the kappa-label can exceed a fingerprint-sized buffer). Propagation: supersession/amendment banners on ADR-037/018/028/036/041/051 (historical bodies preserved per convention); ADR-060 audit-trail row + strategic -decision row (ch 4); updated HostBounds/resolver-surface/carrier descriptions in ch 2/5/6/8/10; TR-10 marked resolved, TR-01/TR-18 updated, new TR-23 (carrier lifetime migration); glossary HostBounds/TermValue/Term::Literal/resolver/removed -constant entries + new TermValue/ChunkSource/carrier_inline_bytes entries. Fixed an AsciiDoc rendering break: the `*_OUTPUT_BYTES_MAX` / `*_carrier_bytes` backtick globs opened stray emphasis crossing the code span (interleaved <literal>/<emphasis> -> invalid DocBook XML, Pandoc failure on ch 02/04/08); converted to ++...++ passthrough. Domain-neutral: use cases (GGUF/ONNX/JSON/SLSA) kept illustrative; the downstream content-addressing crate is referred to generically, not named. All eight validators (V1-V8) pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 22, 2026
  • ADR-058/059 consistency pass: glossary terms, strategy row, QS-05 T2 cross-ref, TR-22 Closes the cross-chapter gaps an audit surfaced after landing ADR-058/059, so the compression-operator reading and operator-geometry codomain are consistently referenced wherever their coined terms appear (κ-derivation / Atlas / ResGraph / operator-geometry are used across chapters 5, 8, 9, 12). 12 glossary: add entries for κ-derivation, compression-to-canonical-form, closure-lossless taxonomy (T1/T2/T3), operator-geometry coordinates, Atlas of Resonance Classes, ResGraph — coined terms used in multiple chapters that lacked definitions. 11 technical risks: new TR-22 — Atlas / exceptional-structures codomain typing is conceptually committed (ADR-059) but code-realization-deferred to application-level / demand-driven Layer-3 per ADR-031 + ADR-059 rejected-alt-7. Scopes the risk to applications electing the finer operator-geometry-codomain-typed admission vocabulary; records that the framework's core commitments (κ-label byte-coordinate, T1/T2/T3 taxonomy, coarse convergence-tower stratification) are substrate-native and carry no dependency on the Atlas realization. 10 quality requirements: QS-05 (replay equivalence) response measure now reads TC-05 trace-replay equivalence as ADR-058's T2 tier (κ-label-identity), and states substrate-independence is binary (conforming → byte-identical certificate; non-conforming → fail closed), no statistical-regression form. 04 solution strategy: new strategic-decision row committing the κ-derivation-as- compression reading (ADR-058) and the Atlas/E₈ codomain (ADR-059), matching how the Fold-Fusion Principle (ADR-054) conceptual reading is captured in the same table. Audit found no semantic inconsistency — substrate-independence was already binary across the wiki; these are cross-reference / glossary completeness fixes. Domain- neutrality preserved. All eight validators (V1–V8) pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 21, 2026
  • Wiki cleanup: restructure substrate-amendment audit trail; tighten three-fusion-layers duplication; cross-ref TR-14/TR-15 to ADR-055 Three high-impact cleanup items from the post-ADR-055 audit: (1) ADR-013/TR-08 substrate-amendment audit-trail restructured. The mega-paragraph at §9 line 190 (1,084 words classifying ADR-038..ADR-055 as substrate amendments or not) becomes a compact reference table with one row per ADR carrying the yes/no/wire-format-only verdict and a one-sentence summary. Cognitive load down ~70%; all architectural content preserved in scannable form. The ADR-037 reconciliation prose stays as introductory context; the table is the audit trail. (2) Three-fusion-layers verbatim duplication tightened. §4 Strategic Decisions row 55 and §8 Closure Across Layers concluding paragraph both carried the same 3-fusion-layers enumeration verbatim (macro-expansion / catamorphism / monomorphization, with identical sub-bullet phrasing). Both passages now cross-reference ADR-054 / ADR-055 in §9 as the canonical locus for the detailed mechanics; each chapter keeps its scope-appropriate framing (strategic commitment in §4; closure-across-layers reading in §8) without re-stating the full layer mechanics. ~800 words saved while preserving the chapter-cohesive architectural framings. (3) TR-14 (ψ-residuals discipline) and TR-15 (RESOLVER_ABSENT) gain post-ADR-055 cross-reference notes. TR-14's mitigation is now connected to the verb-body/resolver-body scope boundary per ADR-046 and the universal substrate-Term verb body discipline per ADR-055/TR-20. TR-15 clarifies that resolver-tuple selection is independent of axis bodies — resolver-absent retains its runtime mechanism while axis-body discipline moved to compile-time enforcement via ADR-055. TR-20 already references ADR-055 from prior commit; the cluster TR-14/TR-15/TR-20 now reads as a coherent post- ADR-055 surface. All 8 validators pass; wiki end-to-end consistent; auto cache-clear from prior commit kept the build pipeline clean throughout. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • ADR-055: universal substrate-Term verb body discipline — fold-fusion guaranteed for every axis impl via type-system enforcement Implementer experience proved the standard-library-only scope of ADR-054's canonical axis impl body discipline (ADR-054 RA2) load-bearing for prism's fold-fusion guarantee. An application-author custom axis with an arbitrary-Rust body produces a Term::AxisInvocation whose body the catamorphism cannot reach; the structural-inference guarantee per ADR-001 + ADR-019 fails at that axis's surface; C2's "one Rust function per forward invocation" claim is provisional, not universal. ADR-055 supersedes ADR-054 RA2 with a universal commitment enforced at compile time: - Foundation declares the sealed `SubstrateTermBody` supertrait on `AxisExtension`. Every axis impl (standard-library AND application- author custom) MUST provide a `body_arena() -> &'static [Term]` accessor returning the Term arena slice the kernel decomposes to. - The catamorphism's `Term::AxisInvocation` fold-rule per ADR-029 recursively folds the axis impl's `body_arena()` slice rather than calling an opaque kernel function. Fold-fusion's structural reach extends to the leaf level across every axis surface for every axis impl. - The `axis!` SDK macro per ADR-030 + ADR-052 extends with a normative `body` clause; the macro emits both `AxisExtension` and `SubstrateTermBody` impls together. Axes lacking a `body` clause fail to satisfy the supertrait bound and fail to compile. - ADR-010's arbitrary-Rust Hasher carve-out is amended: HashAxis impls (per ADR-031's HashAxis-from-prism-crypto framing) are axis impls and follow the universal discipline. Standard-library impls already satisfy this per ADR-054's canonical discipline; application-author custom Hashers provide a `body` clause too. Migration: pre-ADR-055 axes with arbitrary-Rust kernels have two paths per ADR-019's initial-algebra commitment: (1) decompose to substrate Terms via the closure-body grammar; (2) move the off-substrate kernel out of the axis surface to a host-boundary wrapper around `forward(input)`. No third option — operations that cannot be expressed in substrate Terms are not prism operations. Updates across the wiki for consistency: - §4 Strategic Decisions row updated to reflect universal scope and drop the standard-library-only framing. - §8 Closure Across Layers concluding paragraph updated similarly. - Conceptual Model intro C2 mechanism updated; "structurally guaranteed by the type system, not aspirational." - ADR-013/TR-08 substrate-amendment paragraph + typed-iso surface consolidation paragraph extended with ADR-055. - TR-20 rewritten: discipline regression is now a compile-time error, not a runtime / inclusion-criterion concern. Migration risk for pre-ADR-055 axes documented. - ADR-054's Rejected alternative 2 marked `(*superseded by ADR-055*)` with the supersession reasoning preserved per the feedback-implementer-loop discipline. - Glossary: new `SubstrateTermBody` trait entry; `Substrate-Term verb body` entry updated for universal scope. Wire format unchanged. All 8 validators pass on clean rebuild. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • Eradicate \`-escape rendering artifacts: AsciiDoc {empty} boundary attribute + passthrough conversion for angle-bracket spans Root cause: AsciiDoc smart-quote substitution + Pandoc DocBook→markdown backtick-escape interaction. When an AsciiDoc inline code-span `text` is immediately followed by a trigger character (letter, ASCII apostrophe, or ASCII double-quote), Pandoc escapes the opening backtick because the smart-quote substitution makes the code-span boundary ambiguous in markdown. Result: literal `\\`text` artifacts in the rendered wiki — the closing backtick is consumed by the entity, and the opening backtick appears as `\\`` text rather than a styled code span. Two-part fix: (1) Insert AsciiDoc `{empty}` attribute substitution between the closing backtick and the trigger character via a state-machine parser (`/tmp/fix_backtick_boundary.py`). `{empty}` is a zero-width attribute that breaks the AsciiDoc/Pandoc bonding without affecting rendered output. The parser tracks opening/closing backtick pairing using AsciiDoc constrained-span rules (opening flanked by start-of- line, whitespace, or specific opening punctuation; closing flanked by non-whitespace), so it only inserts at true closing positions. Applied 462 fixes across 14 .adoc source files (12 arc42 chapters plus 2 ISO 15288 lifecycle pages). (2) Convert 6 specific AsciiDoc inline code spans containing `<...>` angle brackets to `++...++` passthrough form. AsciiDoc inline code spans wrapping content with HTML-significant characters get the angle brackets escaped through the DocBook→markdown conversion, producing literal `\\<` and `\\>` plus the opening-backtick escape. Converting these to `++...++` passthrough preserves the content verbatim (the rendered output remains code-styled monospace). Fixed spans: ADR-026 G6 (match grammar, 4 spans); glossary's first_admit + fold_n + Term::FirstAdmit grammar forms. Build pipeline preserved; all 8 validators pass on clean rebuild (vendor/arc42-generator/build/ cleared); zero `\\` artifacts remain in any of the 22 rendered wiki pages. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • Post-ADR-054 consistency: terminology, strategic-decision row, §8 closure paragraph, fold-rule glossary, TR-20 Five remaining gaps closed after the ADR-054 + ADR-031 amendments: - §4 + §8: "application-neutral-within-domain" replaced with "application-neutral" per ADR-031's amendment (3 locations collapsed to 0 stale occurrences). - §4 Strategic Decisions: new row committing the Fold-Fusion Principle (ADR-054) as the architectural mechanism that realizes zero-cost composition end-to-end across all three layers of closure. Three fusion layers (macro-expansion, catamorphism, monomorphization) plus the standard-library canonical axis impl body discipline (ADR-054 + ADR-031). Cross-referenced to the Conceptual Model intro C2 commitment. - §8 Closure Across Layers: concluding paragraph integrating ADR-054. The three-layer closure plus all substrate-amendment series reduce to fold compositions the catamorphism fuses universally. Fold-fusion is the structural mechanism upholding Conceptual Model C2 ("one Rust function per forward invocation" is structurally enforceable, not aspirational). - §12 Glossary: new "Fold-rule" entry (the per-variant evaluation rule the catamorphism applies; 21 Term variants × 21 fold-rules composing universally per ADR-019's initial-algebra property; fold-rules are the building blocks of fold-fusion). - §11 Technical Risks: new TR-20 — canonical axis impl body discipline regression breaks fold-fusion at the leaf level. A standard-library canonical axis impl that regresses to an arbitrary-Rust body (a hand-written compression function, an inlined-via-FFI native primitive) compiles successfully but invalidates the architectural commitment that the catamorphism reaches through the published canonical surface to the leaf level. Mitigation: foundation's code review + CI conformance suite (byte-equivalence against FIPS-180-4 / FIPS-202 / BLAKE3 spec / secp256k1 SEC 2 §2.4.1 / BLAS integer-precision / FHE correctness predicates) enforces the discipline per ADR-031 + ADR-054. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • Fix AsciiDoc parsing errors blocking rendered .md regeneration Three classes of parsing errors were preventing the arc42 build pipeline from regenerating chapters 06/08/09/12 from their AsciiDoc sources: - Table cell separators inside backticks: 04 line 40 contained `first_admit(<domain>, |<idx>| <predicate>)` and `fold_n(n, init, |state, idx| step)` — the `|` characters parsed as table cell separators, breaking a 3-column row into 5 cells. Escaped the closure-parameter bars with `\|`. - Rust lifetime apostrophes inside backticks: backtick-quoted spans containing patterns like `<'_, Output>` or `<'a, T>` produced interleaved emphasis/literal tags in the DocBook intermediate that Pandoc rejected. Converted ~39 such spans across 06/08/09/12 to AsciiDoc inline literal passthrough (`++...++`). - Asterisks inside backticks: `*Record<H>` and `#![no_std]` similarly produced overlapping emphasis/literal tag sequences. Converted to `++*Record<H>++` and `++#![no_std]++` passthrough. Source semantics are unchanged — passthrough renders identically to backtick monospace once the parsing path is unblocked. All 12 rendered chapter .md files now reflect the current source content (V1 placeholder resolutions in §6 and §8, ADR-040/041/042 in §9, glossary updates in §12). All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 13, 2026
  • Strip remaining supersedes/retired framing; fill V1 placeholder sections with resolving content Backwards-compat framing strip (per user directive: focus on complete + correct present architecture): - ADR-013 Consequences: ADR-040 paragraph rewritten as present-state statement (7-individual BoundShape catalogue); removed "ADR-040 supersedes ADR-038's polymorphic-LessEqBound framing" history-reference - ADR-036 ResolverTuple arity cap paragraph: removed "The prior framing 'twice the AxisTuple cap' is retired" history-reference - ADR-036 Rejected alternative 2: removed "(partially superseded by ADR-041)" marker; restated as current-state rejection of typed-Record<H> returns - ADR-038 title: now "Closed-catalog extension: observable:AxisProjectionObservable + canonical-string-form args_repr encoding" (removed "LessEqBound byte-sequence ordering convention" from title) - ADR-038 clause (2): rewritten as one-line pointer to ADR-040's LexicographicLessEqBound; removed the polymorphic-LessEqBound semantic-extension prose - ADR-038 Substrate-amendment-via-foundation rule: removed "updates the normative comment for type:LessEqBound" and "closed BoundShape catalogue of 6 individuals stays at 6" stale text - ADR-038 Consequences: bound_shape_iri example updated to .../LexicographicLessEqBound per ADR-040 - ADR-038 example code block bound_shape_iri: now LexicographicLessEqBound - ADR-038 Rejected alternative 1: rewritten as current-state rejection of polymorphic-LessEqBound; removed "(superseded by ADR-040)" marker - ADR-040 Status line: just "Status: Accepted." (removed "Supersedes ADR-038's Rejected alternative 1") - ADR-040 Context: rewritten as present-state motivation; removed history reference to ADR-038 clause (2) framing - ADR-040 Decision header: "type:LexicographicLessEqBound joins the closed BoundShape catalogue" (was "Extend the closed BoundShape catalogue from 6 individuals to 7") - ADR-040 prose: removed "is retired" / "is retired because" / "ADR-038's structural commitments are preserved... The only retraction is..." paragraphs - ADR-040 Rejected alternative 1 + 5: removed "ADR-038's polymorphic-LessEqBound framing" history-references - ADR-041 Status line: just "Status: Accepted." (removed "Partially supersedes ADR-036's Rejected alternative 2") - ADR-041 Context: rewritten to describe the architectural rationale without "Implementation feedback identifies this as load-bearing" framing - ADR-041 Consequences: removed "the implementation-side concern that 'ψ-stage outputs lose typing' is addressed" - ADR-041 prose paragraph that started with "ADR-036's Rejected alternative 2 is partially superseded" — rewritten as present-state architectural commitment - ADR-041 Rejected alternative 4: removed "implementation feedback" framing - ADR-042 Context: rewritten without "Implementation feedback identifies this gap" and "The implementer's §9.5 names" framings - ADR-042 Rejected alternative 5: removed "implementation feedback identifies this as the load-bearing gap" framing - Section 4 strategic decision row: rewritten to describe ADR-038 + ADR-040 as a single state (BoundShape catalogue of 7 with LessEqBound + LexicographicLessEqBound) - Section 8 Closure Across Layers ADR-038 paragraph: rewritten as present-state (7-individual catalogue with both LessEqBound and LexicographicLessEqBound) - Glossary type:LessEqBound entry: rewritten as integer-valued primitive; points to LexicographicLessEqBound per ADR-040 for byte-sequence observables - Glossary MAX_RESOLVER_TUPLE_ARITY entry: removed "retained per ADR-037 clause (2)" wrapper and "The prior framing 'twice the AxisTuple cap' is retired" V1 placeholder sections filled (user directive: no deferred sections; convey complete model): - Section 6 Runtime View: four upstream-arc42 placeholder H2s (<Runtime Scenario 1> through <Runtime Scenario n>) now carry one-line cross-references to the substantive scenarios above; final placeholder explicitly states "The four numbered scenarios above are exhaustive; the chapter specifies no further runtime scenarios" - Section 8 Concepts: three upstream-arc42 placeholder H2s (_<Concept 1>_ through _<Concept n>_) now carry brief content listing the substantive concepts they resolve to; final placeholder explicitly states "The concepts above are exhaustive; the chapter specifies no further cross-cutting concepts" All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 12, 2026
  • Strip backwards-compatibility framing; describe current architecture directly User directive: no backwards-compatibility or supersedes framing; only the complete and correct present architecture. The wiki now describes the architecture as it stands; historical-supersession framing has been removed from cross-references, glossary, Section 4 strategic decisions, Section 8 Closure Across Layers, Section 6 Scenario 1, c4 dsl, and 15288 docs. Glossary cleanup: - Removed four deprecated entries (AXIS_OUTPUT_BYTES_CEILING, FOLD_UNROLL_THRESHOLD, ROUTE_INPUT_BUFFER_BYTES, ROUTE_OUTPUT_BUFFER_BYTES) that pointed to HostBounds equivalents; the present HostBounds-parametric entries are now the only source - Stripped "supersedes ADR-038's polymorphic-LessEqBound semantic-extension framing" from LexicographicLessEqBound entry; just describes the present catalog - Stripped "Partially supersedes ADR-036's Rejected alternative 2" from ψ-stage typed-coordinate carriers entry; just describes the present resolver-trait shape Section 5 BBV bridge component: BoundShape catalogue now described as 7 individuals directly (EqualBound, LessEqBound, GreaterEqBound, RangeContainBound, ResidueClassBound, AffineEqualBound, LexicographicLessEqBound) without semantic-extension framing c4 workspace.dsl bridge component: same — 7 BoundShape individuals listed directly Section 4 strategic decision row: rewrote without supersedes language; describes the three architectural commitments directly (catalog-level comparison-semantics disambiguation, type-system discrimination of ψ-stage outputs, foundation-provided verdict-envelope accessors) Section 8 Closure Across Layers: dropped the "supersedes ADR-038's polymorphic-LessEqBound framing" paragraph language; the present commitment (closed BoundShape catalogue of 7 with LessEqBound integer-valued + LexicographicLessEqBound byte-sequence) is stated directly. ADR-041 paragraph dropped the "partially supersedes ADR-036's Rejected alternative 2" language Section 6 Scenario 1 step 10: expanded to use the typed ADR-042 accessors directly (`Grounded::as_inhabitance_certificate(&self)`, `PipelineFailure::as_inhabitance_impossibility_certificate(&self)`, the named accessor methods) 15288 technical.adoc: substrate-parameter bullet rewritten to describe ADR-040 (7 BoundShape individuals; LessEqBound integer + LexicographicLessEqBound byte-sequence), ADR-041 (typed-coordinate carriers), ADR-042 (typed Rust verdict-envelope views) directly without supersedes framing All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 12, 2026
  • ADR-040 + ADR-041 + ADR-042: implementer-facing surface — LexicographicLessEqBound + typed-coordinate resolver carriers + inhabitance verdict typed Rust surface ADR-040 — type:LexicographicLessEqBound as 7th BoundShape individual (supersedes ADR-038 Rejected alternative 1): - Extends closed BoundShape catalogue from 6 individuals to 7: adds LexicographicLessEqBound as the byte-sequence-comparison primitive - LessEqBound retired from byte-sequence semantic-extension framing; restricted to integer-valued observables (HammingMetric, DerivationDepthObservable, etc.) - LexicographicLessEqBound: predicate form observable(datum) <= bound with canonical big-endian unsigned ordering (lexicographic for fixed-length; lexicographic-with-shorter-prefix-rule for variable-length) - Catalog declaration alone determines comparison semantics — resolvers do not dispatch on observable type - ConstraintRef::Bound.args_repr encoding rules per ADR-038 preserved unchanged; bound_shape_iri carries .../LexicographicLessEqBound for byte-sequence observables - 5 rejected alternatives: keep-polymorphic-LessEqBound, comparison_kind field, replace-LessEqBound, subclass relationship, defer ADR-041 — Typed-coordinate resolver carriers (partially supersedes ADR-036 Rejected alternative 2): - Foundation declares 9 #[repr(transparent)] newtype wrappers around byte slices (SimplicialComplexBytes<'a>, ChainComplexBytes<'a>, HomologyGroupsBytes<'a>, BettiNumbersBytes<'a>, CochainComplexBytes<'a>, CohomologyGroupsBytes<'a>, PostnikovTowerBytes<'a>, HomotopyGroupsBytes<'a>, KInvariantsBytes<'a> — the κ-label carrier) - Each #[repr(transparent)]: zero runtime cost; layout identical to &[u8]; type wrapper is purely compile-time - The 8 ψ-stage resolver traits' resolve method takes the prior ψ-stage's typed carrier as input (NerveResolver retains &[u8] input since its source is the per-value bytes); output remains writer-style &mut [u8] (zero allocation preserved) - Cross-stage composition is type-checked at compile time — mismatches surface as type errors at resolver-impl compile time rather than runtime ShapeViolations - Partially supersedes ADR-036 Rejected alternative 2: typed *Record<H> returns remain rejected (would force allocation); typed input carriers as zero-allocation #[repr(transparent)] views are admitted - 5 rejected alternatives: revert-to-Record<H>, marker traits, associated types, defer, MaybeUninit complexity ADR-042 — Inhabitance verdict typed Rust surface: - Foundation declares InhabitanceCertificate<'a, T>(pub &'a Grounded<T>) — #[repr(transparent)] zero-allocation view over &Grounded<T>; accessors kappa_label() returning KInvariantsBytes<'_>, witness() returning WitnessValueTuple<'_>, search_trace() returning Trace, certified_type() returning &'static str - Foundation declares InhabitanceImpossibilityCertificate<'a> over &PipelineFailure; accessor contradiction_proof() returning canonical-form failure trace bytes (Lean 4 by-contradiction-reconstructable) - Grounded::as_inhabitance_certificate(&self) and PipelineFailure::as_inhabitance_impossibility_certificate(&self) -> Option<…> as the accessor method surface - Foundation-provided inhabitance::dispatch_through_table helper for optional predicate:InhabitanceDispatchTable consultation (three rule arms: TwoSatDecider, HornSatDecider, ResidualVerdictResolver) - Universal — typed accessors available for any Grounded<T> / PipelineFailure; applications whose admission relations are not inhabitance questions simply don't call the typed accessors; the verdict-envelope reading is the application's choice - 5 rejected alternatives: new sealed substrate type splitting success envelope, marker trait gating, owned heap-allocated type, parallel resolver:InhabitanceResolver foundation trait, defer Cross-references: - ADR-038 Rejected alternative 1 marked superseded by ADR-040 - ADR-036 Rejected alternative 2 marked partially superseded by ADR-041 (byte-buffer output preserved; typed input carriers added) - ADR-013 Consequences: extended with ADR-040 catalog extension (BoundShape 6→7), ADR-041 + ADR-042 type-system surface additions (not substrate amendments — wire format unchanged) - Section 4 Strategic Decisions: new row threading ADR-040/041/042 as the implementer-facing surface trio - Section 8 Closure Across Layers: three new paragraphs documenting ADR-040/041/042 commitments and how they close the implementer-facing surface - Glossary: new entries for type:LexicographicLessEqBound, ψ-stage typed-coordinate carriers, InhabitanceCertificate<'a, T>, InhabitanceImpossibilityCertificate<'a>, inhabitance::dispatch_through_table Together with ADR-035-039, the framework's path from typed-feature-hierarchy declaration through κ-label and concrete witness to verdict envelope is realized end-to-end through typed surfaces: closed-catalog disambiguation of comparison semantics (ADR-040); type-system discrimination of ψ-stage outputs (ADR-041); typed Rust verdict-envelope surface (ADR-042). No per-application accessor reimplementation; no observable-type dispatch in resolvers; no runtime-only ψ-stage composition checking. All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 12, 2026
  • ADR-037 + ADR-038 + ADR-039: HostBounds-parametric capacity bounds + AxisProjectionObservable closed-catalog extension + inhabitance verdict realization ADR-037 — HostBounds-parametric capacity bounds (completes ADR-018 for data-shape capacities): - 14 free-standing data-shape capacity caps migrate to HostBounds associated constants (TERM_VALUE_MAX_BYTES, AXIS_OUTPUT_BYTES_CEILING, FOLD_UNROLL_THRESHOLD, MAX_BETTI_DIMENSION, NERVE_CONSTRAINTS_CAP, NERVE_SITES_CAP, JACOBIAN_MAX_SITES, RECURSION_TRACE_MAX_DEPTH, MAX_OP_CHAIN_DEPTH, AFFINE_MAX_COEFFS, CONJUNCTION_MAX_TERMS, ROUTE_INPUT_BUFFER_BYTES, ROUTE_OUTPUT_BUFFER_BYTES, UNFOLD_MAX_ITERATIONS) plus 8 ψ-stage resolver output byte-buffer ceilings (22 new HostBounds constants total) - DefaultHostBounds extends with prior fixed values as defaults (shape-preserving for existing apps) - 2 type-system tuple-impl-table caps (MAX_AXIS_TUPLE_ARITY, MAX_RESOLVER_TUPLE_ARITY) stay foundation-vetted with explicit Rust-language carve-out: Rust's lack of variadic generics requires per-arity blanket-impl emission at foundation's build time - MAX_RESOLVER_TUPLE_ARITY: lower bound rederived from card(ResolverCategory) (= 8), retiring the "twice the AxisTuple cap" coincidence framing - RESOLVER_ABSENT_DISCRIMINATOR stays foundation-fixed (not a capacity bound; discriminator byte) - 5 rejected alternatives: keep-foundation-fixed, HostBounds-driven-macro-emission, raise-without-migrate, separate-CapacityBounds-axis, runtime-configurable ADR-038 — Closed-catalog extension under ADR-013/TR-08 (axis-realized admission relations): - New top-level Observable subclass: observable:AxisProjectionObservable, parallel to the 7 internally-derived Observable categories (Stratum/Metric/Path/Reduction/Catastrophe/Curvature/Holonomy) — distinct because its values carry from the substrate-extension surface per ADR-030, not from the framework's internal algebraic/topological structure - type:LessEqBound semantic envelope extends by normative documentation amendment to byte-sequence-valued observables under canonical big-endian unsigned ordering (closed BoundShape catalogue of 6 individuals stays at 6 in cardinality) - ConstraintRef::Bound.args_repr canonical-string-form encoding rules for AxisProjectionObservable: axis_address=<hex>;kernel=<symbolic>;sites=<site-list>[;target=<target-spec>] - Axis identification by content-address (AXIS_ADDRESS per ADR-030), not tuple position — application-invariant identity for closed-catalog Observable individuals - Wire-format version constant bumps for the schema amendment - 5 rejected alternatives: parallel-BoundShape-proliferation, Term::AxisInvocation in verb body (ψ-residual), tuple-position axis ref, structured-enum wire form, existing-category placement ADR-039 — Inhabitance verdict realization + four-family resolver landscape: - For typed feature hierarchies whose admission relations are inhabitance questions: successful Grounded<Output> IS cert:InhabitanceCertificate envelope (κ-label as homotopy-classification structural witness at ψ_9; concrete cert:witness ValueTuple derivable from Term::Nerve's 0-simplices at ψ_1; cert:searchTrace IS Grounded::derivation().replay()); Err(PipelineFailure) IS cert:InhabitanceImpossibilityCertificate envelope (with proof:InhabitanceImpossibilityWitness as proof payload, proof:contradictionProof as canonical-form failure trace) - κ-label and cert:witness are different witness granularities (homotopy classification vs. concrete ValueTuple) the same canonical k-invariants branch produces at different stages - Four-family resolver landscape: (1) pipeline ψ-stage resolvers (8 traits per ADR-036, sealed), (2) bridge Observable-category resolvers (open), (3) user-surface morphism resolvers (open), (4) ontology resolver:Resolver hierarchy (20+ class declarations, not surfaced as foundation traits) — coexist as parallel resolution categories at different layers, NOT in a subclass relationship - predicate:InhabitanceDispatchTable is a resolution-strategy specification the application's NerveResolver impl MAY consult internally - 5 rejected alternatives: 9th-substrate-trait/G30, κ-label-as-cert:witness conflation, trait renaming, exhaustive ontology mirroring, opt-in marker trait Cross-references (Block D): - ADR-013 Consequences: ADR-037 reconciliation framing + ADR-038 catalog extension + ADR-039 verdict mapping - ADR-018 Consequences: ADR-037 completion mapping with 14 + 8 data-shape migrations and impl-table carve-out - ADR-029 Term::Application Concat operand: <B as HostBounds>::TERM_VALUE_MAX_BYTES per ADR-037 - ADR-030 Context Hasher trait shape: <B as HostBounds>::TERM_VALUE_MAX_BYTES per ADR-037 - ADR-029 fold-rule + multiple references: <B as HostBounds>::FOLD_UNROLL_THRESHOLD per ADR-037 - ADR-030 Consequences: capacity-bound reconciliation paragraph (AXIS_OUTPUT_BYTES_CEILING migrates to HostBounds; MAX_AXIS_TUPLE_ARITY stays foundation-vetted) - ADR-035 G24 Term::Betti: byte_offset = 4 * k, byte_length = 4 for k in [0, <B as HostBounds>::BETTI_DIMENSION_MAX) - ADR-036 MAX_RESOLVER_TUPLE_ARITY reframing: structural lower bound from card(ResolverCategory) - ADR-035 Consequences: cross-reference to ADR-039 verdict realization - Section 4 strategic decision row + Section 8 Closure Across Layers append Glossary (Block F): - MAX_AXIS_TUPLE_ARITY reframed as foundation-vetted impl-table cap (Rust-language carve-out) - AXIS_OUTPUT_BYTES_CEILING marked deprecated; points to HostBounds equivalent - 14 new HostBounds-parametric glossary entries (one per migrated capacity cap) - 8-ψ-stage-resolver-output ceilings entry - MAX_RESOLVER_TUPLE_ARITY entry with structural derivation from card(ResolverCategory) - Canonical k-invariants branch (verdict realization mapping per ADR-039) - observable:AxisProjectionObservable (closed-catalog extension) - cert:InhabitanceCertificate / cert:InhabitanceImpossibilityCertificate / proof:InhabitanceImpossibilityWitness (three-primitive verdict structure) - predicate:InhabitanceDispatchTable + trace:InhabitanceSearchTrace - type:LessEqBound semantic extension - Per-ψ-stage resolver trait (family (1)) and resolver:Resolver (family (4)) disambiguation - Verdict realization wiki commitment Cleanup: - Removed duplicate Rejected alternative 5 in ADR-036 (file end) - Removed duplicate ADR-036 cross-reference paragraph in ADR-030 Consequences (contained stale "Term::AxisInvocation in verb bodies" framing contradicting ψ-residuals discipline) Architecture stays domain-neutral end-to-end; the closed catalog can express axis-realized admission relations through content-address axis identification + canonical-string-form args_repr; the canonical k-invariants branch produces the verdict envelope without per-application re-derivation; the substrate's data-shape capacity surface is HostBounds-parametric so applications of any data shape compose through DefaultHostBounds or a custom HostBounds impl. All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 12, 2026
  • ADR-035 + ADR-036 reframe: canonical k-invariants branch + ψ-residuals discipline + uniform byte-buffer resolver surface + R = NullResolverTuple default + no axes value parameter ADR-035 reframe (Block A): - Title extended: "Canonical ψ-pipeline + ψ-chain Term variants + ψ-residuals discipline on verb body composition" - Decision restructured into three coupled amendments: (1) nine ψ-Term variants, (2) canonical k-invariants branch ψ_1 → ψ_7 → ψ_8 → ψ_9 as the architectural composition for the verifiability commitment, (3) ψ-residuals discipline forbidding Term::FirstAdmit, Term::AxisInvocation, byte-comparison/concat PrimitiveOps in verb-body terms - Conceptual model paragraph: compiled binary IS the canonical circuit; data representation minimal (input bytes + κ-label); client conceptually larger than data; complete model fuses into a single reference - Closure check at verb!/prism_model! invocation extended with ψ-residuals walk - Composition example switched from `betti(homology_groups(chain_complex(nerve(input))))` to canonical `k_invariants(homotopy_groups(postnikov_tower(nerve(input))))` - Rejected alternatives 5-7 rewritten: partial-coverage / homology-branch / permit-ψ-residuals ADR-036 reframe (Block B): - PrismModel<H, B, A, R = NullResolverTuple> trait shape with R defaulting to NullResolverTuple; A: AxisTuple + Hasher bound (canonical hash axis bound) - ResolverTuple trait: drop per-category accessor methods (live in marker traits); add RESOLVER_ABSENT_DISCRIMINATOR byte const - Eight resolver traits: uniform writer-style byte-buffer surface `fn resolve(&self, input: &[u8], out: &mut [u8]) -> Result<usize, ShapeViolation>` (no typed *Record<H> returns) - resolver! macro emits all eight Has<Category>Resolver impls unconditionally (declared fields delegate; undeclared categories delegate to NullResolverTuple Null* impls) - pipeline::run_route<H, B, A, M, R>(input, resolvers: &R): five type params, no axes value parameter, all eight Has<Category>Resolver<A> bounds unconditionally - Application-side instantiation: no axes value (axis methods type-associated via <A as Hasher>::initial()) - MAX_RESOLVER_TUPLE_ARITY = 16 explicit (twice AxisTuple cap) - Replace GenericImpossibilityWitness with ShapeViolation + RESOLVER_ABSENT shape IRI + foundation-internal RESOLVER_ABSENT_DISCRIMINATOR byte - Rejected alternatives reorganized: AxisTuple-conflation / typed-records / ad-hoc-per-category-params / global / foundation-provided-impls Block C cross-references: - ADR-013 Consequences: ψ-residuals, canonical k-invariants branch, byte-buffer resolver surface, RESOLVER_ABSENT_DISCRIMINATOR - ADR-022 D4 comment block: <H, B, A: AxisTuple + Hasher, R = NullResolverTuple>; asymmetric threading rationale - ADR-022 D4 trait declaration: same shape - ADR-022 D5 run_route signature: drop axes value param, add unconditional Has<Category>Resolver<A> bounds - ADR-022 D5 forward body: run_route::<H, B, A, Self, R>(input, &resolvers) - ADR-026 G12 + TR-12 + ADR-030 closure-check: already at twenty reserved identifiers (no change) - ADR-029 fold-rule preamble: four substrate parameters; ψ-residuals discipline - ADR-029 ψ-Term fold-rules: byte-buffer resolver.resolve(input, out_buffer) signatures; KInvariants noted as canonical-branch terminal - ADR-029 variant-count statement: FirstAdmit noted as verb-body-forbidden - ADR-030 Consequences: ResolverTuple parallels AxisTuple with asymmetric threading - ADR-031 Consequences: resolver baselines parallel axis baselines Block D Section 4 + Section 8: - Strategic decision row updated: canonical k-invariants branch + ψ-residuals + R = NullResolverTuple + conceptual-model framing - Closure Across Layers paragraphs: canonical k-invariants branch + ψ-residuals + byte-buffer surface Block E glossary: - New: Canonical k-invariants branch (under C), NullResolverTuple, RESOLVER_ABSENT_DISCRIMINATOR, Resolver trait shape (under R/N), ψ-chain umbrella + ψ-residuals discipline (Greek-letter cluster) - Updates: ψ-chain resolver traits to byte-buffer surface; Has<Category>Resolver<H> to all-eight-emission pattern; PrismModel to new signature + run_route call; ResolverTuple drop per-category accessor mention; ResolverCategory annotated with ψ-stage numbers; MAX_RESOLVER_TUPLE_ARITY explicit value 16; resolver! to all-eight-emission pattern; nine Term:: variant entries annotated with canonical-branch / strictly-weaker positions Reconciliation in Sections 02/03/05/06/07/08/10 + 15288 docs: - TC-03 substitution axes table: R = NullResolverTuple default; A: AxisTuple + Hasher bound; byte-buffer signature; ψ-residuals - Section 03 author-input row: R optional with default - Section 05 pipeline component: run_route<H, B, A, M, R>(input, &resolvers) signature; no axes value param - Section 06 Scenario 1 steps 7-8: four substrate parameters, no axes value param; canonical k-invariants branch; ψ-residuals discipline - Section 07 deployment view executable: canonical resolver branch list; type-associated axis dispatch - Section 08 PrismModel trait + forward call: same shape - Section 10 QS-01: canonical-branch resolver list; byte-buffer surface; ψ-residuals - 15288 technical.adoc + technical-management.adoc: R optional with default; A: AxisTuple + Hasher; canonical k-invariants branch All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 11, 2026
  • ADR-035 + ADR-036: ψ-chain Term variants + ResolverTuple substrate parameter ADR-035 + ADR-036 land together — the doc explicitly says they're co-dependent, so I'm committing both in one commit. ADR-035 introduces nine ψ-chain Term variants (Nerve, ChainComplex, HomologyGroups, Betti, CochainComplex, CohomologyGroups, PostnikovTower, HomotopyGroups, KInvariants); ADR-036 introduces the R: ResolverTuple substrate parameter that carries application-provided resolver instances for the eight resolver-bound ψ-Term variants (Betti is resolver-free pure computation). The Term enum extends from twelve variants to twenty-one. The model declaration's parameter shape extends from <H, B, A> to <H, B, A, R>. Closure-body grammar extends from G1-G20 to G1-G29. ADR-035 commits the ontology-defined ψ-pipeline ψ_1..ψ_9 (per spec/src/namespaces/op.rs and spec/src/namespaces/homology.rs in the UOR-Foundation/UOR-Framework ontology) as substrate Term variants. The ψ-chain is the structural-witness arm of op:InferenceOperation (ι = P ∘ Π ∘ G); together with the ψ-pipeline's resolution arm flowing through combinatorial Term variants, the catamorphism evaluates the complete typed-iso surface end-to-end. Verb bodies witness per-value structural admission relationships (admission as a homology property of the value's CONSTRAINTS-induced structure rather than a runtime predicate) directly through prism vocabulary; the framework's verifiability commitment per ADR-001 + ADR-019 (canonical computational equivalences as homology classes) is realized at the closure-body grammar layer. Brute-force Term::FirstAdmit enumeration retires from verb bodies whose admission relationships have a structural-witness expression. ADR-036 commits the ResolverTuple substrate parameter paralleling AxisTuple per ADR-030 — same tuple-of-bounded-types pattern, same dispatch through associated constants — but carries per-value content provision rather than per-domain operation kernels. Foundation declares ResolverTuple, ResolverCategory enum, eight resolver traits (NerveResolver<H>, ChainComplexResolver<H>, HomologyGroupResolver<H>, CochainComplexResolver<H>, CohomologyGroupResolver<H>, PostnikovResolver<H>, HomotopyGroupResolver<H>, KInvariantResolver<H>), eight Has<Cat>Resolver<H> marker traits, MAX_RESOLVER_TUPLE_ARITY const, eight Null* resolver baselines, and a NullResolverTuple. The SDK provides the resolver! macro paralleling axis!. Standard library sub-crates may contribute resolver baselines paralleling axis baselines per ADR-031. Application authors declare resolver impls in resolver! struct fields (eight foundation- fixed canonical field names: nerve, chain_complex, homology_groups, cochain_complex, cohomology_groups, postnikov, homotopy_groups, k_invariants); the SDK proc-macro infers Has<Cat>Resolver<H> bounds in the model declaration's where-clause from verb bodies' ψ-Term emissions. Foundation's pipeline::run_route signature extends to thread the ResolverTuple alongside the AxisTuple. Block A (both ADRs inserted at end-of-file in 09_architecture_decisions.adoc). Block B cross-references in ADR-013 Consequences (extended with both ADRs); ADR-022 D4 trait body comment (now mentions all four substrate parameters); ADR-022 D5 run_route signature (extended with R: ResolverTuple); ADR-026 G12 disambiguation paragraph (reserved-identifier set extended with nine ψ-chain identifiers); TR-12 (same extension); ADR-029 fold-rules (nine new ψ-Term fold-rules added) + per-variant preamble (now names four substrate parameters) + variant-count statement (twelfth → twenty-first); ADR-030 Consequences (ResolverTuple parallel to AxisTuple); ADR-031 Consequences (resolver baselines parallel to axis baselines). Block C: Section 4 strategic-decision row added; Section 8 Closure Across Layers paragraphs appended (one for ADR-035, one for ADR-036). Block D glossary: nine ψ-Term variant entries; nine grammar-form entries (G21-G29); ResolverTuple + ResolverCategory + MAX_RESOLVER_TUPLE_ARITY + resolver! + ψ-chain resolver traits cluster + Has<Category>Resolver<H> marker-trait entry. Audit-pass for variant-count + grammar-count consistency: ADR-020 Decision Term-enum enumeration (twelve → twenty-one); ADR-033 Consequences (twelve → twenty-one); Section 5 BBV vocabulary re-exports row (twelve → twenty-one plus G1-G20 → G1-G29); Section 8 Concepts initial-algebra paragraph (twelve → twenty-one) + PrismModel concept entry; glossary prism_model! entry (G1-G20 → G1-G29 + extended reserved-identifier set + run_route signature with R: ResolverTuple). Domain-neutralization: per the cleanup commit 3a65899, the wiki is domain-neutral. The ADR-035/036 source documents had stray "Bitcoin mining" / "Sha256dHasher" / "PrismBtcNerveResolver" references; these have been generalized in the inserted text (e.g., "Bitcoin mining model's NerveResolver" → "admission-by-homology application's NerveResolver"; "Sha256dHasher" → "MyHashAxisImpl"). The architectural commitment is domain-agnostic; concrete examples in ADRs use generic placeholder names. Encoding: the source documents had mangled UTF-8 (Ï for ψ, ι for ι, β for β, etc.); these have been translated to proper Unicode Greek/math characters in the inserted text. Forward-references: the ADR-035 ↔ ADR-036 cross-references resolve internally (both ADRs land in this commit). Foundation/SDK/standard- library reconciliation is the next step: foundation extends the Term enum with the nine ψ-Term variants, declares the ResolverTuple trait family, extends pipeline::run_route's signature; SDK provides the resolver! proc-macro; the standard library contributes resolver baselines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 10, 2026
  • Audit-gap-closure: fix V2 build invalid-XML, complete twelve-variant + G1-G20 consistency Critical fix: previous commit cf3ce00 (ADR-034) and 8672dfd (ADR-034 audit) silently produced rendered output missing ADR-034 content. Root cause: two AsciiDoc syntax issues in ADR-034 produced invalid DocBook XML that pandoc rejected for 09_architecture_decisions.xml, leaving the rendered chapter staged at the pre-ADR-034 state. The underlying gap was visible only after re-running build.sh with a clean vendor/arc42-generator/build/ — then V2 surfaced "Pandoc failed for 09_architecture_decisions.xml: Invalid XML." AsciiDoc fixes: - ADR-034 *Mechanism 1* paragraph: removed [quote]/____ block (the first quote-block in the file; AsciiDoctor's DocBook output for this block produced unbalanced literal/emphasis tags). Inlined the fold-rule update prose into the surrounding paragraph. - ADR-031 *Decision*: replaced *closure under `uor-foundation`'s vocabulary* with *closure under `uor-foundation`* (per ADR-013). AsciiDoctor parsed the inner backtick-then-apostrophe construct inside the surrounding emphasis as overlapping literal/emphasis spans, producing invalid XML. After these fixes V2 succeeds; the rendered 09-Architecture-Decisions.md now has 65 ADR-034/FirstAdmit mentions (up from 0). Twelve-variant consistency completion: - Section 8 PrismModel concept entry: Term-enum listing extended from 10 variants ending at HasherProjection to 12 variants (..., AxisInvocation, ProjectField, FirstAdmit) with proper ADR attribution. G1-G20 consistency: - Section 5 BBV operation-declaration vocabulary description. - Section 8 Closure Across Layers Layer 2 description. - Glossary prism_model! entry. - Section 4 ADR-034 strategic decision row prose. Together these complete the wiki's consistency for ADR-034. The remaining "G1-G19" references all live within ADR-026 itself (describing its own G12-G19 additions, before ADR-033 added G20) and within the ADR-033 strategic decision row's historical description of the "prior G1-G19 baseline that ADR-033 extends" — those are accurate at their authoring point. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 10, 2026
  • ADR-034: Term::FirstAdmit + iteration-counter binding for Term::Recurse ADR-034 closes the two remaining structural-correctness gaps for ADR-026 G14 (fold_n) and G16 (first_admit) so foundation's catamorphism evaluates them end-to-end. Mechanism 1 — iteration-counter binding for Term::Recurse via the foundation-fixed RECURSE_IDX_NAME_INDEX (e.g., u32::MAX - 3, paralleling RECURSE_PLACEHOLDER_NAME_INDEX). The Term::Recurse data structure is unchanged; ADR-029's per-variant fold-rule extends scope to bind the iteration counter alongside the recursive-call placeholder. ADR-022 D3 G7 grammar admits the optional two-parameter closure form recurse(measure, base, |self, idx| step). fold_n step bodies above FOLD_UNROLL_THRESHOLD now have access to the iteration index. Mechanism 2 — Term::FirstAdmit, the twelfth Term variant. Carries { domain_size_index, predicate_index }. Fold-rule iterates idx ascending across [0, N) with structural short-circuit on first admission; emits a coproduct-shaped TermValue ((0x01, idx_bytes) for found, (0x00, padding) for not-found). Predicate scope binds FIRST_ADMIT_IDX_NAME_INDEX (e.g., u32::MAX - 4). ADR-026 G16's lowering shifts from Term::Recurse to Term::FirstAdmit. The implementation-runtime override per the three-way responsibility split remains available for strategy (parallel coset traversal, cancellation policy, cost-budget enforcement) but is no longer load-bearing for structural correctness. Cross-references: ADR-013 Consequences extended; ADR-022 D4 trait body comment names all four foundation-fixed name indices; ADR-022 D3 G7 grammar form extended; ADR-026 fold_n and G16 lowering descriptions updated; ADR-029 Term::Recurse fold-rule extended; ADR-029 Term::FirstAdmit fold-rule added; Term-enum-count statement updated. Section 4 Strategic Decision row added; Section 8 Closure Across Layers paragraph appended. Glossary: Term::FirstAdmit, RECURSE_IDX_NAME_INDEX, FIRST_ADMIT_IDX_NAME_INDEX entries added; first_admit entry's lowering target updated. Audit-pass for variant-count consistency: ADR-020 Term-enum enumeration, Section 5 BBV vocabulary re-exports row, Section 8 Concepts initial- algebra paragraph all updated to twelve variants. Section 6 Runtime View Scenario 1 fold-rule walk and Section 10 QS-01 disassembly mention Term::FirstAdmit and Term::Recurse iteration-counter binding. prism-btc's nonce_fiber_traversal verb body now flows through pipeline::run_route end-to-end: first_admit(WittLevel::W32, |nonce| { hash(concat(input.prefix, nonce)) <= input.target }) lowers to Term::FirstAdmit; foundation iterates with structural short-circuit; ops/traversal::traverse_sequential and traverse_parallel can retire once foundation/SDK reconcile. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 10, 2026
  • Audit-gap-closure: reconcile sections 2/3/5/6/8/10/11, glossary, C4, ISO 15288 to ADR-030..033 Following ADR-030 (axis! macro + AxisTuple), ADR-031 (prism std-lib facade), ADR-032 (CYCLE_SIZE on ConstrainedTypeShape), and ADR-033 (Term::ProjectField + G20), the prior audit-pass concerns named explicitly in those edit lists land here. Term-variant count ten -> eleven: 05 BBV vocabulary re-exports row, 08 Concepts initial-algebra paragraph, ADR-020 Decision text, ADR-030 Consequences (with forward-reference to ADR-033's eleventh variant). Term::HasherProjection -> Term::AxisInvocation rename in non-historical contexts: section 6 Runtime View Scenario 1 fold-rule walk + sequence step 5 + Properties bullet; section 10 Quality Requirements QS-01 disassembly description. PrismModel signature `<H, B, A: Hasher>` -> `<H, B, A: AxisTuple>` per ADR-030: 08 Concepts trait body, ADR-020 Consequences, ADR-022 D4 trait body + Consequences, ADR-022 D5 run_route signature, glossary entry. Sample selection now `(Sha256dHasher,)` (1-tuple). TR-12 stale identifier-resolution enumeration in 11 Technical Risks: switch to snapshot-specific PrimitiveOp catalog reference per ADR-022 D3 G3a; add the axis-trait-method step from ADR-030; note binary-operator forms per G3b are recognized at expression syntax level. Substitution-axis triple references (Sections 2, 3, 4, 11): the third position is now `AxisTuple` (originally `Hasher` per ADR-007, generalized per ADR-030; HashAxis from prism-crypto per ADR-031 as the canonical first member). Section 2 axes table row updated; Section 3 author-input row updated; Section 4 Strategic Decisions row + composition paragraph updated; Section 11 TR-01 description updated. Section 5 BBV substrate trait list (lines 22, 40): adds AxisExtension and AxisTuple per ADR-030 + axis! macro; CYCLE_SIZE noted on ConstrainedTypeShape. ADR-031 softening: previous "prism contains no architecture definition" contradicted ADR-005 ("prism is the Prism runtime"). Reconciled: prism carries the runtime per ADR-005 AND serves as the standard-library facade per ADR-031, with closure-under-uor-foundation per ADR-013 as the architectural commitment that ties the two roles together. Glossary: ConstrainedTypeShape entry adds CYCLE_SIZE per ADR-032; Hasher entry notes the rename to HashAxis declared by prism-crypto per ADR-031; Substitution axis entry generalized to AxisTuple per ADR-030; PrismModel entry signature corrected. ISO 15288 lifecycle pages (technical.adoc, technical-management.adoc): Hasher -> AxisTuple in the substitution-axis enumeration. C4 workspace.dsl: prism's vocabulary-re-exports component description extended with AxisExtension/AxisTuple/axis!/CYCLE_SIZE/HashAxis. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 9, 2026
  • ADR-032 + ADR-033: closure-body grammar completion + substrate-amendment reconciliation ADR-032 — CYCLE_SIZE associated const on ConstrainedTypeShape: compile-time domain-cardinality introspection for first_admit. The SDK proc-macro reads <DomainTy as ConstrainedTypeShape>::CYCLE_SIZE at expansion time and emits it as the Term::Literal measure value at the smallest WittLevel that fits. Per- shape-kind derivation: Witt-level = 2^N; product = saturating-product of factors; coproduct = saturating-sum + 1; output_shape! declared explicitly; ConstrainedTypeInput = 1. Replaces SDK 0.3.6's Literal(256) placeholder. ADR-033 — Field-access projection (G20) for product-of-shapes inputs and the eleventh Term variant Term::ProjectField. Closure-body grammar admits <expr>.<name> and <expr>.<index> on partition_product receivers, including chained access. partition_product! macro extends with a named-tuple form (prefix: Prefix76, target: Target32) emitting a FIELDS const that the proc- macro reads at expansion time. Term::ProjectField fold-rule slices [byte_offset .. byte_offset+byte_length] from the source's evaluation result; bounds verified at proc-macro expansion. Coproduct destructuring remains through Term::Match (G6); product destructuring is structurally a different operation. Substrate-amendment reconciliation in existing ADRs (the wiki catching up to foundation 0.3.5's TR-08 substrate amendments — Le/Lt/Ge/Gt/Concat — that landed before this commit): - ADR-022 D3 G3 split into G3a (identifier-call form) + G3b (binary-operator form +, -, *, ^, &, |, <=, <, >=, >). Both lower to identical Term::Application emissions. - ADR-026 G12 disambiguation references the canonical PrimitiveOp catalog at any committed snapshot rather than enumerating ten fixed identifiers. Reserved-identifier set extends with recurse, unfold, lift, project from named grammar forms, plus ADR-030's axis-trait method identifiers in the resolution order (step 3 of 5). - ADR-026 G16 extended with ADR-032 cross-reference: structural correctness vs runtime-strategy override now distinct. - ADR-029 Term::Application fold-rule references the snapshot catalog; Le/Lt/Ge/Gt return Literal(1)/Literal(0); Concat result length is sum of operand lengths bounded by TERM_VALUE_MAX_BYTES. - ADR-029 Term-enum-count statement: tenth (AxisInvocation) + eleventh (ProjectField). - ADR-013 Consequences extended with ADR-032 + ADR-033 + the PrimitiveOp catalog extension under the same TR-08 mechanism. - ADR-022 D4 trait body annotated with CYCLE_SIZE cross-reference. Section 4 strategic-decision row added; Section 8 Closure Across Layers paragraph extended. Glossary: 3 new entries (CYCLE_SIZE, G20, Term::ProjectField); PrimitiveOp entry updated to reference the snapshot catalog rather than enumerating fixed-by-architecture. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 9, 2026
  • ADR-030 + ADR-031 + Scientific Methods and Results partition (issue #7) ADR-030 — `axis!` SDK macro: universal substrate-extension declaration mechanism. Generalizes Hasher to one axis among many; introduces AxisExtension, AxisTuple, MAX_AXIS_TUPLE_ARITY, AXIS_OUTPUT_BYTES_CEILING. Term::HasherProjection becomes Term::AxisInvocation (Term enum stays at ten variants). Catamorphism's per-variant fold-rule dispatches through A::dispatch(axis_index, kernel_id, &evaluated_inputs). ADR-031 — `prism` is the standard library: a façade over `uor-foundation` plus standard-library Layer-3 sub-crates (prism-numerics, prism-crypto, prism-tensor, prism-fhe) published from the Prism repository. Inclusion criteria, layered consumption pattern, content-addressing invariance, conformance vetting. Repository allocation made explicit: architecture in UOR-Framework, standard library in Prism. Drops prior "blessed" framing. Cross-references: ADR-007 third-position generalization to A: AxisTuple; ADR-013 Consequences extension; ADR-024 axis-declaration mechanism alongside verb-declaration; ADR-026 G19 generalization to axis-trait method calls; ADR-029 fold-rule + Substitution-axis-realized verbs paragraph rewritten for AxisTuple. Section 4 strategic decision row + composition paragraph; Section 8 Closure Across Layers paragraph. Glossary: 11 new/updated entries (axis!, AxisExtension, AxisTuple, AXIS_ADDRESS, AXIS_OUTPUT_BYTES_CEILING, MAX_AXIS_TUPLE_ARITY, Standard-library Layer-3 sub-crate, prism-numerics, prism-crypto, prism-tensor, prism-fhe, Term::AxisInvocation rename). Scientific Methods and Results — new non-normative academic-documentation partition (Director of Research stream per issue #7). Adds src/scientific/Scientific-Methods-and-Results.adoc with the landing-page content; scripts/render-scientific.sh (Stage 3d, mirrors render-15288.sh with reconciliation-gap discipline); Stage 3d wiring in build.sh + Stage 4g in stage-to-wiki-root.sh + render_scientific in validate.sh; sidebar entry in src/wiki/Sidebar.adoc; partition specification in wiki-definition.md (Non-normative content partitions section, source-tree, build-stages, correctness-contract Property 7); SOP in README.md (Robin issues -> wiki maintainer authors AsciiDoc -> build.sh -> commit). Pin refresh: tools/versions.txt java line refreshed from openjdk 21.0.11 to openjdk 21.0.10 (the JDK 21.x actually installed on the build host). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 9, 2026
  • Three-layer algebraic closure + operator-set commitments (ADR-024..029) Architectural completion of the three-layer closure spine (substrate / prism / implementation), the operator sets at each layer, and the catamorphism evaluation semantics that realize "structural inference" at the value level. Six new ADRs: - ADR-024 Three-layer algebraic closure spine. Carriers, operator sets, closure checks, and the verb!/use_verbs! mechanism for the implementation layer. - ADR-025 Substrate operator set: composers (×, +) + endomorphism family after_op for op ∈ Γ = {+, −, ×, ÷, ^}, with the Categorical X regime split (T=3, O=8). Catalog and transition tables as conformance test vectors. - ADR-026 Prism operator set (seven operators: compose, parallel_compose, fold_n, tree_fold, first_admit, partition_product, partition_coproduct) + closure-body grammar extension G12-G19 (with G19 as the substitution-axis-realized verb form). Three-way runtime split for first_admit. - ADR-027 Custom Output shape declaration via output_shape! SDK macro. Closes the GroundedShape seal as a degenerate-typed-iso blocker. - ADR-028 Grounded<T> carries the output-value payload. ROUTE_OUTPUT_ BUFFER_BYTES ceiling; output_bytes() accessor. Brings application- level side-channel outputs into the foundation-sealed primary surface. - ADR-029 Catamorphism evaluation semantics. Per-variant fold-rules (Literal, Variable, Application, Lift, Project, Match, Recurse, Unfold, Try, HasherProjection) make pipeline::run a real catamorphism. ADR-023 reconciled with stable-Rust form (foundation-fixed ROUTE_INPUT_BUFFER_BYTES ceiling instead of per-impl-sized buffer requiring generic_const_exprs). Rejected alternative 4 documents the reasoning, paralleling ADR-022 D2's slice-form decision. Cross-references threaded through ADR-007, ADR-013, ADR-019, ADR-020, ADR-022 D4. Section 4 strategic decision row + section 8 "Closure Across Layers" subsection. Glossary additions: 18 new entries spanning the three closures (across / prism / substrate), the seven prism operators (compose, parallel_compose, fold_n, tree_fold, first_admit, partition_product, partition_coproduct), the substrate operator framework (Categorical X regime split, gauge-tower operator set Γ), the SDK macros (output_shape!, verb!, use_verbs!), the new Grounded accessor (output_bytes), the new ceiling (ROUTE_OUTPUT_BUFFER_BYTES), the new Term variant (Term::HasherProjection), the new threshold (FOLD_UNROLL_THRESHOLD), and the new coined term Verb. All 8 validators PASS, Stage 5 idempotence holds (0 divergent files), all tests PASS. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 7, 2026
  • Rename prism-sdk → prism + canonical UOR-address surface (ADR-017) Two architectural changes on top of 063d0ac: 1. Crate rename: prism-sdk → prism. Symmetric with uor-foundation (no -sdk suffix on either). prism-verify stays separate to preserve ADR-005's verifier-minimal-surface property. The Prism repo continues publishing both prism and prism-verify. 2. Canonical UOR-address surface (ADR-017). prism's standard library types are canonical UOR-address mappings: each standard type's IRI is content-deterministic in its constraint declaration; two applications using the same standard type produce values addressing identically. Closure under uor-foundation (ADR-013) makes the canonicality hold derivatively rather than via a claimed namespace. The catalog stays in prism's crate documentation; the wiki commits to canonicality, not to a specific catalog. Rename mechanics: - 282+ occurrences of prism-sdk → prism across all 12 chapters - workspace.dsl: softwareSystem identifier prism → prismSystem (the container needed the prism identifier, and Structurizr DSL requires identifiers be unique workspace-wide) - workspace.dsl: container prismSdk → prism - workspace.dsl deployment instances: prismSdkDep → prismDep prismSdkLinked → prismLinked prismSdkVerifyLinked → prismLinkedInVerify (avoids clash with the existing prismVerifyLinked for prism-verify in the verification env) - 13 orphaned "SDK" prose references cleaned up - ADR-005 title trimmed to "Decompose Prism into three crates" - ADR-007 title: "foundation defines, prism bounds, author selects" New content: - §5.2 standard library row: amended to specify decomposition by uor-foundation's shape primitives + canonical UOR-address mapping note + reference to ADR-017 - §8 closure section: extended from 2 consequences to 4. Bullets 3 and 4 cover IRI determinacy (closure makes UOR addresses derivative of constraint declarations, not namespace-claimed) and author-declared types (standard library is convenience, not capability — authors declare their own first-class Prism types via prism's vocabulary re-exports) - ADR-017: full Nygard ADR with two rejected alternatives - Glossary: new entry "Canonical UOR-address mapping" The rename is purely nominative; every architectural commitment (sealing, principal data path, UORassembly, closure, mint primitives, repo split) holds identically before and after. ADR-017 is the only new architectural commitment. V1, V2, V3, V4, V5 all PASS. Stage 5 idempotence holds. 22 SVGs regenerated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 4, 2026
  • Three-crate reallocation: substrate / runtime / replay façade Restructures the wiki to disentangle the conflation between uor-foundation (substrate) and Prism (the system Prism realizes). The architectural commitments do not change; the allocation of those commitments across the three crates does. Crate role allocation (was → is): uor-foundation "principal data path + 7 sealed types + traits" → substrate. Type-declaration vocabulary (incl. shape proc-macros via internal sub-crate); 4 UOR-domain sealed types (Datum, Triad, Derivation, FreeRank); wire-format type definitions as data; mint primitives as cross-crate construction surface. uor-foundation-sdk → prism-sdk was "compile-time enforcement only, no runtime code" → Prism runtime. Pipeline runtime; 3 Prism-mechanism sealed types (Validated, Grounded, Certified); operation-declaration vocabulary; standard type library. Closed under uor-foundation's vocabulary. Re-exports uor-foundation's vocabulary so authors import only prism-sdk. uor-foundation-verify → prism-verify was "validates traces; depends on foundation type defs and replay primitives" → replay façade. Re-exports prism-sdk's certify_from_trace and Certified, plus uor-foundation's wire-format types. Carries no implementation. Source-side changes: - 12 chapters substantively amended for the new allocation: ch1 Introduction: three-crate roles + sealed-type allocation note ch2 TC-02 + TC-03 prose: cross-crate seal clarification ch3 Channels table: substantive updates per row + new mint-primitive channel; cross-boundary Sealing bullet ch4 6-row strategic table substantively rewritten; "How These Decisions Compose" rewritten ch5 Black-box descriptions and component decompositions substantively rewritten; pipeline relocates to prism-sdk; replay relocates to prism-sdk; mint-primitives component added; new L3 sub-section for prism-sdk seal regime + replay ch6 Scenario 1 properties bullet, Scenario 2 control transfer, Scenario 3 substantive steps, Cross-Scenario Properties first bullet substantively updated ch7 Mapping table cell contents change (prism-sdk now Present in user-execution and user-verification environments); repo-source clarification in Level 2 prose ch8 Sealing Discipline rewritten; UORassembly Contract Definition amended; #![no_std] Posture rewritten; Feature Flags expanded; three new H2s: Operation Declaration, Closure Under uor-foundation, Cross-Crate Construction Surface ch9 ADR-005, 006, 007, 011 substantively rewritten; ADR-002, 003, 008, 009, 010 amended (renames + role refs); five new ADRs: ADR-012 Pipeline runtime placement; ADR-013 Closure of prism-sdk under uor-foundation; ADR-014 Operation declaration vs operation shipment; ADR-015 Repo split (UOR-Framework + Prism); ADR-016 Cross-crate seal mechanism (mint primitives) ch10 QS-01, QS-04 Scenario A/B, QS-05 substantive updates ch11 TR-01 substantive (proc-macro location); TR-03 substantive (cross-crate flag combinatorics); TR-06 substantive (cross-repo coordination); two new TRs: TR-08 vocabulary insufficiency, TR-09 prism-sdk version pin lag ch12 Glossary: 18 entries updated for new sealed-type allocations + crate roles; 5 new entries (prism-sdk, prism-verify, mint primitive, operation declaration, closure under uor-foundation); plus certify_from_trace, replay, seal regime, vocabulary re-exports as new component entries - workspace.dsl: container descriptions rewritten; uor-foundation L3 drops pipelineComp, gains mintPrimitivesComp + 4 shape macro components; prism-sdk L3 replaces 4-component view with 6 (pipeline, sealRegime, replay, operationDeclaration, standardTypeLibrary, vocabularyReExports); prism-verify L3 re-anchored at prism-sdk's replay; dynamic views updated for pipeline-in-prism-sdk; deployment views add prismSdkLinked to user-execution and user-verification environments - 22 SVGs regenerated (Structurizr export) V1, V2, V3, V4, V5 all PASS. Stage 5 idempotence holds. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 4, 2026
  • Phase 3 first content: import full Prism architecture wiki Replaces the 12 heading-only chapter skeletons and the empty workspace.dsl with their authored versions, plus the 11 Structurizr SVG views (+ 11 -key.svg legends) generated from the workspace. Chapters added: 01 Introduction and Goals 103 lines (4 H2) 02 Architecture Constraints 107 lines (3 H2) 03 Context and Scope 74 lines (3 H2) 04 Solution Strategy 59 lines (2 H2) 05 Building Block View 249 lines (3 H2) 06 Runtime View 382 lines (5 H2 + upstream placeholders) 07 Deployment View 199 lines (4 H2) 08 Cross-cutting Concepts 290 lines (9 H2 + upstream placeholders) 09 Architecture Decisions 387 lines (11 ADRs) 10 Quality Requirements 211 lines (4 H2) 11 Risks and Technical Debts 197 lines (7 TRs) 12 Glossary 67 lines (1 H2) C4 model added (12 view keys, 22 SVGs after legends): L1: c4-l1-system-context L2: c4-l2-prism-containers L3: c4-l3-{foundation,sdk,verify}-components Dynamic: c4-dynamic-{principal-data-path, trace-replay, uorassembly-enforcement, distribute-and-run} Deployment: c4-deployment-{application,verifier} Source-side fix-ups applied during validation: - workspace.dsl: removed `applicationUser -> uorFoundationVerify` from the system-landscape-scoped `c4-dynamic-distribute-and-run` view; Structurizr rejects person->container relationships at landscape scope. - Chapters 5,6,7,8,10,11: wrapped `#![no_std]` and `#![feature(generic_const_exprs)]` in `++...++` passthrough so the `#` characters do not collide with AsciiDoc's mark-text formatting and produce malformed DocBook in V2's pandoc step. Rendered output unchanged (still monospace `#![...]`). V1 still PASSes (heading text comparison is exact-match against upstream; chapters add new H2 sections beyond the upstream set, which V1 explicitly allows as a structural superset). Imported v1-structural-alignment.rb and v3-structurizr.sh from the content drop were stale earlier versions and were not copied -- current in-tree versions are the working ones. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 4, 2026
  • Phase 0 + Phase 1 + Phase 2 bootstrap Adds the full validation, build, and authoring infrastructure defined in the parent UOR-Framework repo's wiki-definition.md, plus skeleton chapter sources and the first end-to-end-passing rendered output. Phase 0 (tooling): - 12 scripts under scripts/ (V1..V5 validators, install-tools, validate, build, render-wiki-frame, stage-to-wiki-root, check-wiki-state) - vendor/arc42-generator submodule pinned at 46bd7ce (Feb 2026) - arc42-template pinned at b29e08 via tools/arc42-template-pin.txt (overrides the generator's own stale submodule pin) - structurizr.war v2026.04.19 (Playwright variant) pinned in tools/checksums.txt by SHA-256 - cmark-gfm 0.29.0.gfm.13, built from source by install-tools.sh - Gemfile pins asciidoctor ~> 2.0, github-markup ~> 5.0, commonmarker ~> 0.23 (5.0.x github-markup needs the 0.x API) - tools/versions.txt as build.sh Stage 1's pin authority Phase 1 (skeleton sources): - src/arc42/adoc/NN_*.adoc — 12 chapter skeletons matching upstream H1+H2 - src/arc42/arc42-template.adoc — top-level include for direct asciidoctor - src/arc42/version.properties - src/c4/workspace.dsl — empty workspace (V3 PASS / 0 views) - src/wiki/{Home,Sidebar,Footer}.adoc Phase 2 (rendered artifacts at the wiki root): - 12 chapter files NN-Title-Case-Name.md - Home.md, _Sidebar.md, _Footer.md - images/ (placeholder .gitkeep until the C4 model gains views) Validators: - V1 — structural alignment with upstream arc42-template - V2 — drives the arc42-generator Docker pipeline (gitHubMarkdownMP / plain), bypassing build-arc42.sh's destructive submodule reset - V3 — Structurizr DSL validate + SVG export (skips export when no views, avoiding Playwright Chromium dependency on empty workspaces) - V4 — cmark-gfm with GitHub's wiki extension set - V5 — github-markup gem to catch markup-stage rendering failures build.sh runs the five-stage pipeline (pre-flight pin check, validate, render wiki-frame, stage to wiki root, idempotence check via cmp). Spec deviations (vs wiki-definition.md): - Chapter 3 filename is 03_context_and_scope.adoc (upstream-actual), not 03_system_scope_and_context.adoc; rendered as 03-Context-and-Scope.md - arc42-template pinned at our level (separate file) rather than relying on the generator's transitive pin, because arc42-generator's Templates.groovy expects a layout newer than its own pinned submodule - v2-arc42-build.sh invokes `groovy build.groovy` directly, skipping the generator's build-arc42.sh wrapper (which wipes our staged edits and fails inside our nested-submodule git layout) - V2's chosen output format is gitHubMarkdownMP (Multi-Page GFM) for per-chapter files, not the spec's unspecified default Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 4, 2026