Skip to content

History / 08 Concepts

Revisions

  • ADR-061 corrections: per-shape SITE_COUNT, structure-preserving canonical forms, σ-axis homogeneity Applies the architect's corrections to ADR-061 (in the AsciiDoc source; rendered pages regenerated): - Per-shape SITE_COUNT made explicit and consistent across the ADR §(2) bullets and the glossary entry: G2ProductShape = 2 × COMPONENT_LABEL_BYTES (binary); F4QuotientShape / E7AugmentationShape / E8EmbeddingShape = COMPONENT_LABEL_BYTES; E6FiltrationShape = COMPONENT_LABEL_BYTES + 1. - E6 filtration clarified as structure-preserving (not quotient-like): canonical form retains the operand bytes plus a one-byte degree-partition tag (degree-5 vs degree-6). - E7 augmentation clarified as canonical-form-internal: operand normalized to its S₄-orbit canonical representative, no prepended bytes. - E8 embedding clarified as identity on canonical-form bytes; the composed κ-label is distinguished from the operand's by realization-IRI provenance, not digest bytes. - Canonicalize-verb rule sharpened to enumerate all five per-shape rules (lexicographic-min-first for G2; mirror-class lex-min representative for F4; degree-partition tag for E6; S₄-orbit lex-min representative for E7; identity for E8) and to require the canonical form match the shape's SITE_COUNT. - New σ-axis-homogeneity requirement: all operand κ-labels of a composition share the composition's σ-axis (operands under different σ-projections live in different codomain spaces; no cross-σ-axis bridge is committed). Reflected in ADR-061 §(5), the ch 8 concepts summary, and the glossary entry. Cross-surface consistency verified: SITE_COUNT values agree between ADR bullets and glossary; σ-axis homogeneity present in ch 8/9/12. All eight validators pass; page-size guard OK (glossary 494 KiB, warning band, under limit). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 23, 2026
  • 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 + ADR-059: κ-derivation as compression operator + Atlas/E₈ codomain; document kernel::convergence substrate vocabulary the wiki had omitted Lands the architect-provided ADR-058 (κ-derivation IS compression-to-canonical- form; three-tier closure-lossless taxonomy T1/T2/T3; cross-substrate compression universality as a TC-05 closure property) and ADR-059 (Atlas-image-inside-E₈ as the operator-geometry codomain of κ-derivation; Hopf convergence tower as coarse stratification; exceptional groups G₂/F₄/E₆/E₇/E₈ as finer codomain typing). Both are conceptual-reading commitments over existing constructs — audit-trail rows marked "No" wire-format change. Consistency repair before applying: ADR-059's prose asserts kernel::convergence is "existing substrate vocabulary per the building-block view in section 5; per the kernel-component glossary in section 12." That vocabulary was only referenced generically in the wiki ("the convergence machinery" / "convergence algebra") with no trait surface. Verified against the real foundation source (foundation/src/kernel/convergence.rs and spec/src/namespaces/convergence.rs, UOR ontology Amendment 66) that the module and its trait surface (ConvergenceLevel / HopfFiber / ConvergenceResidual / CommutativeSubspace / AssociativeSubalgebra; four levels R/C/H/O at dims {1,2,4,8}; Hopf fibers S⁰/S¹/S³/S⁷; identities existence/feedback/choice/self-reference; persistent β_{2^k−1}=1) are genuine substrate vocabulary the wiki had under-documented. Enriched the section 5 kernel-component description and the section 12 kernel entry with the authoritative trait surface, and added a "Hopf convergence tower" glossary entry — making ADR-059's section-5/12 citations precisely accurate. 08 concepts: two paragraphs after the ADR-057 paragraph commit the compression-operator reading (ADR-058) and the operator-geometry codomain (ADR-059) into the conceptual model, tied to the Hopf convergence tower. Domain-neutrality preserved: use cases enumerated as illustrative (JSON/XML/ ASN.1/S-expressions/proof-normalization/term-rewriting); no downstream consumer crate named. Atlas/exceptional-group code realization explicitly left as application-level / demand-driven Layer-3 per ADR-031, not committed to uor-foundation. All eight validators (V1–V8) pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 21, 2026
  • ADR-057 cross-chapter propagation: concepts, building block view, runtime view, glossary, technical risks Propagates ADR-057's bounded-recursive-structural-typing commitment across the chapters that describe what the substrate offers, how it evaluates, what it builds, and what risks attend it. 08 concepts: - New paragraph after the ADR-056 paragraph commits ConstraintRef::Recurse, shape_iri_registry, register_shape!, partition_coproduct! recurse:T operand grammar, CYCLE_SIZE saturation rule, and the architectural-registry-pattern parallel to ADR-038/049 (observable-IRI) and ADR-007/030 (axis catalog). - Fold-Fusion Principle enumeration extends ADR-035..053 to include ADR-057. - Line 313 BoundShape comparison-semantics rule de-temporalized to match ADR-040 source ("differ from those the catalog already realizes...at the ADR-013/TR-08 amendment boundary"). 05 building block view: uor-foundation interface description adds the shape_iri_registry module (RegisteredShape, lookup_shape, __register_shape) and the register_shape! SDK macro to the foundation-published surface enumeration. 06 runtime view: ψ_1 NerveResolver's evaluation surface extended to include ConstraintRef::Recurse handling — lookup_shape(shape_iri) consultation, descent-budget-bounded unrolling, irreducible-leaf termination — alongside the prior eight resolver-bound ψ-Term dispatch description. 11 technical risks: new TR-21 — shape-IRI registry capacity and verifier-side registry drift. Records link-time symmetry commitment between prism-side and prism-verify-side registries within a fixed wire-format version, registry contribution mechanics (auto-emitted via partition_coproduct! / partition_product! macro expansions; cross-crate registration via standard-library Layer-3 sub-crates), Recurse-target-not-found runtime ShapeViolation surface, and the descent-budget cycle-termination guarantee for mutually-recursive shape graphs. 12 glossary additions: - shape_iri_registry (foundation module) - RegisteredShape (carrier struct) - register_shape! (SDK macro) - Bounded recursive structural typing (coined term) - CYCLE_SIZE entry extended to record the Recurse saturation rule. Domain-neutrality preserved: no downstream consumer crate named; use cases enumerated as illustrative (JSON, XML, ASTs, S-expressions, protocol-message families, filesystem-like hierarchies, categorical constructions). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 18, 2026
  • LexicographicLessEqThreshold + TargetCommitment + ValueThresholdObservable: close ADR-040/048/049 catalog correspondence; refine ADR-035 scope cross-references to ADR-056 across chapters ADR-040: add Bound-shape-to-ObservablePredicate-impl correspondence — every BoundShape catalog primitive (ADR-040) has a foundation-published ObservablePredicate impl (ADR-049), with type:LexicographicLessEqBound realized by LexicographicLessEqThreshold under a new observable:ValueThresholdObservable taxonomy subclass. ADR-048: publish TargetCommitment = SingletonCommitment<LexicographicLessEqThreshold> as the canonical foundation-published search-cost commitment alias. ADR-049: extend foundation-published ObservablePredicate impls from 4 to 5 — add LexicographicLessEqThreshold (struct declaration, reference impl, accept_prob closed form, evaluate semantics under right-aligned big-endian comparison). New observable:ValueThresholdObservable taxonomy subclass parallel to SpectralObservable. Glossary: UOR observable surface 4 -> 5; add LexicographicLessEqThreshold, TargetCommitment, observable:ValueThresholdObservable entries; TypedCommitment entry notes TargetCommitment alias. ADR-013 audit table: ADR-040/048/049 rows reflect the new catalog-correspondence, type alias, and 5th impl. Cross-chapter ADR-056 scope refinement (02, 06, 08, 10, 11, 12): tighten "verb-body" framings of ADR-035's ψ-residuals discipline to "route body's syntactic surface", with compound-verb / axis-impl / resolver bodies explicitly outside scope per ADR-056. Eliminates the prior internal contradiction where chapters described discipline as forbidding emissions in all verb bodies while ADR-056 had refined it to only the prism_model!-declared route closure body. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 17, 2026
  • ADR-056: ψ-residuals discipline scope refinement — applies to route body's syntactic surface only Implementer report: "ADR-035/036 ψ-residuals (wiki constraint, not a foundation-sdk gap). concat/hash/le/lt/ge/gt rejection blocks SHA padding, HMAC, Merkle, tensor saturation. Closure requires wiki amendment." Wiki-internal contradiction surfaced by ADR-055's universal substrate-Term verb body discipline: every axis impl must decompose to substrate Terms, but ADR-035 (broad-scope reading) forbids Concat/Le/Lt/Ge/Gt/AxisInvocation in verb bodies — exactly the primitives SHA padding (Concat + Le/Lt), HMAC (Concat), Merkle (Concat), and tensor saturation (Le/Ge) require. Standard library unimplementable under the broad reading. ADR-056 refines ADR-035's scope. The ψ-residuals discipline applies to the **route body's syntactic surface** — the closure body the author writes directly in the `prism_model!`-declared `route` function. The discipline does NOT apply to: - Compound verb bodies declared via `verb!` per ADR-024 - Axis impl bodies per ADR-055's universal discipline - Resolver bodies per ADR-046 The four categories of "verb body" the wiki recognizes (route body, compound verb body, axis impl body, resolver body) now have explicit scope-boundary placement. The discipline's purpose — keeping admission structurally shaped at the typed-iso surface — is preserved at the route-body layer where it matters; the vocabulary restriction at the substrate layer is lifted. Coordinated updates: - ADR-035 RA7 marked "(*scope refined by ADR-056*)" with the refinement explanation preserving the original rejection rationale per the feedback-implementer-loop discipline. - ADR-046 decision section restructured to recognize all four verb-body categories (route bodies restricted; compound verb bodies + axis impl bodies + resolver bodies unrestricted). Discipline-scope-boundary paragraph in ADR-035 amended to point to ADR-056's refinement. - ADR-013/TR-08 audit-trail table extended with ADR-056 row. - Typed-iso surface consolidation extended with ADR-056. - §8 Closure Across Layers gains a paragraph explaining ADR-056's scope refinement and the canonical compound operations it enables. - §11 TR-14 mitigation posture updated to acknowledge ADR-056's scope refinement: authors restructure search-shaped logic by introducing compound verbs that internally use byte-comparison / byte-concat operations the route's syntactic surface cannot directly emit. - Glossary ψ-residuals discipline entry updated for route-body- syntactic-surface scope; canonical compound operations listed explicitly. Wire format unchanged. ADR-056 is not a substrate amendment — it refines the proc-macro discipline-walk scope; no primitives, Term variants, or wire-format fields change. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 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
  • Post-ADR-050..053 consistency pass: catalog count, Γ form, new risks Five remaining stale references closed after the ADR-050..053 additions: - §8 Concepts F-signature: PrimitiveOp catalog enumerated as 18 variants at the post-ADR-053 snapshot (was 15 pre-ADR-053). The six ring-axis primitives Γ = {Add, Sub, Mul, Div, Mod, Pow}, the four hypercube-axis ops {Xor, And, Or, Bnot}, the unary set, byte-level comparisons, and Concat. - §9 ADR-026 G12 disambiguation: lowercase PrimitiveOp identifier list updated to 18 variants (added div, mod, pow). - §11 TR-12 macro identifier-resolution: same 18-variant update. - §12 Categorical X regime split glossary: Γ corrected from the five-element form {+, −, ×, ÷, ^} to the six-element form {Add, Sub, Mul, Div, Mod, Pow} per ADR-053. Added cross-reference to ADR-050's full-Witt-tower evaluation discipline. - §11 gains two new risk entries: - TR-18 — width-parametric arithmetic cold-path may surprise authors at wide Witt levels. Per-op cost characterization: O(width) for additive ops, O(width^2) for Mul/Div/Mod, O(width^2 · log(exp)) for Pow. Mitigation via algorithmic optimizations within the strategy-selection lane (Karatsuba, Barrett, sliding-window — byte-output-equivalent to reference impl). - TR-19 — Div/Mod zero-divisor runtime path. ShapeViolation carrying https://uor.foundation/op/Div/nonZeroDivisor surfaces at evaluation time, not at proc-macro expansion. Mitigation: authors compose b > 0 precondition through Term::Match or first_admit on input metadata; foundation reference impl checks unconditionally at evaluation time. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • Close remaining wiki gaps surfaced by post-ADR-047..049 review Final completeness pass over the wiki after the ADR-047..049 additions surfaced four classes of remaining items: - Five-parameter shape consistency: ADR-029 prose (the running catamorphism description) and §8 concepts (the closure-across- layers section) updated from "four substrate parameters" to "five substrate parameters" with cross-references to ADR-048. §2 architecture constraints table extended with a TypedCommitment row describing the fifth model-declaration parameter. - ADR-048 wire-format extension paragraph clarified: the CommitmentEvaluated trace event's variant-discriminator byte is foundation-assigned (next free after the existing five variants), not hard-coded; pipeline::run_route extends from five-type- parameter (<H, B, A, M, R>) to six (<H, B, A, M, R, C>). - §11 Technical Risks gains two entries: - TR-16 σ-Projection Hardening Principle non-conformance — structural attack surface a non-conforming Hasher impl exposes; mitigation via foundation CI running axis::cryptanalyze per ADR-049 plus third-party axis crates declaring U1–U6 conformance. - TR-17 deeply-nested AndCommitment compile-time cost — the architectural trade-off between runtime zero-cost and compile- time monomorphization work at large K; mitigation via shallower sub-commitment factoring at architectural boundaries. - §10 Quality Requirements gains QS-06 (zero-cost typed-bandwidth admission) with measurable response criteria: zero allocations attributable to C; bandwidth scaling matching α⁻¹·2^K within ±30% at N=100 and ±10% at N=10⁴, per Hardening Principle U6 (ADR-047). - §12 Glossary gains EmptyCommitment, SingletonCommitment<P>, and AndCommitment<A, B> entries (the three built-in TypedCommitment implementors per ADR-048). All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 14, 2026
  • Sharpen ADR-048/049 with reference-impl skeletons; add CommitmentEvaluated trace event To make ADR-048 and ADR-049 implementation-ready for the foundation team, both ADRs now carry a "Reference implementation surface" subsection with paste-ready Rust skeletons, explicit module paths, and the macro-syntax extension: - ADR-048: Foundation places TypedCommitment + 3 built-in impls in uor_foundation::commitment; the 5th model parameter lands on the pipeline::PrismModel trait with a sealed C: TypedCommitment bound defaulting to EmptyCommitment; pipeline::run_route extends with the &C value-reference parameter and the post-resolver C::evaluate(kappa_label) consultation. The prism_model! macro parses an optional 5th type-position clause in the impl block. - ADR-049: Foundation places the typed observables and ObservablePredicate trait in uor_foundation::observable::predicate; the cryptanalysis battery lives in uor_foundation::axis. Each observable carries a concrete evaluate() body with the p-adic valuation / Walsh–Hadamard parity / ultrametric distance / single-bit-parity computation. CryptanalysisReport carries StructuralReport (§A–§H) + CalibrationReport (§I–§J) with per-test critical thresholds at α = 0.001. - §8 Trace Wire Format: CommitmentEvaluated event variant added per ADR-048 with verifier-check semantics and the default-EmptyCommitment emission rule. The wiki commitments are now spec-complete for the foundation team to implement against. Five upstream items remain blocking prism-btc completion at foundation 0.4.5 (TypedCommitment + 3 impls; 5th PrismModel param; prism_model! macro extension; ObservablePredicate + 4 typed observables; axis::cryptanalyze battery); the wiki now specifies each at trait-signature + module-path + emission-rule detail. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 14, 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
  • Audit-gap-closure pass for ADR-037/038/039: reconcile stale capacity-cap references and surface verdict realization across sections Stale capacity-cap references reconciled to HostBounds-parametric forms per ADR-037: - Section 05 BBV pipeline component: pipeline::ROUTE_INPUT_BUFFER_BYTES / ROUTE_OUTPUT_BUFFER_BYTES / FOLD_UNROLL_THRESHOLD → <B as HostBounds>::* per ADR-037 - Section 08 Closure Across Layers ADR-034 paragraph: FOLD_UNROLL_THRESHOLD reference now HostBounds-parametric - Section 10 QS-01 response measure: ROUTE_INPUT_BUFFER_BYTES / ROUTE_OUTPUT_BUFFER_BYTES references now HostBounds-parametric - Section 11 TR-10 (foundation-fixed buffer ceilings): description + mitigation reframed; ceilings now HostBounds-parametric per ADR-037; applications declare their own HostBounds or use DefaultHostBounds - Section 11 TR-13 (catamorphism evaluation cost): pipeline::FOLD_UNROLL_THRESHOLD reference now HostBounds-parametric - Section 09 ADR-023 Decision + Rejected alternative 4: ROUTE_INPUT_BUFFER_BYTES references reframed as <B as HostBounds>::ROUTE_INPUT_BUFFER_BYTES - Section 09 ADR-028 Decision (4 references) + Rejected alternative 4: ROUTE_OUTPUT_BUFFER_BYTES references reframed as <B as HostBounds>::ROUTE_OUTPUT_BUFFER_BYTES - Section 09 ADR-030 closure check + per-axis output buffering: FOLD_UNROLL_THRESHOLD / AXIS_OUTPUT_BYTES_CEILING references reframed - Glossary entries (AxisExtension, fold_n, FOLD_UNROLL_THRESHOLD, output_bytes, ROUTE_INPUT_BUFFER_BYTES, ROUTE_OUTPUT_BUFFER_BYTES) updated; the prior foundation-fixed entries marked deprecated and pointing to HostBounds equivalents Verdict-realization surface in non-09 sections: - Section 02 HostBounds substitution-axis row: extended with 14 + 8 ADR-037-migrated associated constants enumerated; DefaultHostBounds default-carry framing; type-system tuple-impl-table caps stay foundation-vetted with explicit carve-out - Section 05 BBV bridge component: surface inventory extended with closed Observable taxonomy (incl. observable:AxisProjectionObservable per ADR-038), closed BoundShape catalogue of 6 (with LessEqBound semantic extension), inhabitance verdict envelope types (cert:InhabitanceCertificate, cert:InhabitanceImpossibilityCertificate, proof:InhabitanceImpossibilityWitness, trace:InhabitanceSearchTrace) per ADR-039 - Section 06 Scenario 1 step 10: extended with the ADR-039 verdict realization mapping for inhabitance-style applications (successful Grounded IS cert:InhabitanceCertificate envelope; κ-label structural witness at ψ_9; concrete cert:witness ValueTuple at ψ_1; cert:searchTrace as Grounded::derivation().replay(); Err(PipelineFailure) IS cert:InhabitanceImpossibilityCertificate envelope) 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
  • Audit-gap-closure pass: ADR-007 fourth-parameter framing, ADR-026 G19 ψ-residuals restriction, Section 8 enriched signature + Hashing Substrate Contract, TR-14 + TR-15 ADR-007: third-position bound strengthened from A: AxisTuple to A: AxisTuple + Hasher per ADR-036; fourth substrate parameter R: ResolverTuple defaulting to NullResolverTuple noted as parallel substrate parameter (not a substitution axis architecturally) with per-value content provision (instance-associated, value-reference threading) vs per-domain operation kernels (type-associated, type-parameter threading) ADR-026 G19: ψ-residuals discipline restriction surfaced at the G19 grammar form definition — Term::AxisInvocation is a ψ-residual; verb-body emissions are rejected at proc-macro expansion with a closure-violation error citing the verb's name; the variant remains in the substrate for resolver bodies, conformance-corpus generators, foundation-internal trace replay; authors who naturally needed hash(input) in verb bodies express the equivalent through resolver-bound ψ-Term variants whose resolver impls invoke the canonical hash axis internally Section 8 Foundation as a Signature Category — Signature Endofunctor: enriched-signature description extended with substitution-axis-invocation, field-access projection, bounded-search-with-short-circuit, and the nine ψ-chain operators; PrimitiveOp catalog reference updated to snapshot-specific (foundation 0.3.6 canonical catalog); ψ-residuals discipline scopes the verb-body sub-signature Section 8 Foundation as a Signature Category — Catamorphism: carrier parameterization updated to four parameters (H, B, A: AxisTuple + Hasher, R: ResolverTuple defaulting to NullResolverTuple); model declaration's resolver selection participates in carrier determination Section 8 Hashing Substrate Contract: preamble extended to thread the Hasher trait through ADR-030 (consumed via AxisTuple), ADR-031 (HashAxis subsumes the prior Hasher), and ADR-036 (A: AxisTuple + Hasher bound enables resolver-bound substrate operations to consume canonical hash axis type-associatedly) TR-14 (new): ψ-residuals discipline rejects naturally search-shaped verb bodies at proc-macro expansion — structured-error requirements (rejected variant + offending span + ψ-residual category + architectural reason + recommended restructuring path); the discipline is load-bearing for verifiability commitment per ADR-001 + ADR-019; foundation does not relax for application convenience TR-15 (new): RESOLVER_ABSENT runtime path is the only mechanism reporting resolver-absent at evaluation time — NullResolverTuple Null* impls return ShapeViolation carrying RESOLVER_ABSENT shape IRI + foundation-internal discriminator byte; mitigation posture names SDK proc-macro-time warning analysis (paralleling ψ-residuals walk) emitting at compile time when verb-body ψ-Term emissions require categories the model's R doesn't declare; the runtime mechanism is the load-bearing path, proc-macro warning is a diagnostic convenience 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 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
  • Audit-gap-closure for ADR-035/036: reconcile sections 2/3/5/6/7/8/9/10/12 + c4 + 15288 to ψ-chain Term variants and ResolverTuple substrate parameter - TC-03: ten Term variants → twenty-one (original 9 + AxisInvocation + ProjectField + FirstAdmit + nine ψ-chain) - Section 02 substitution-axes: add ResolverTuple subsection as fourth model-declaration substrate parameter per ADR-036 - Section 03 author-input row: include ResolverTuple selection - Section 05 BBV substrate trait list, prism whitebox interface, vocabulary re-exports, bridge component, pipeline component: add ResolverTuple, eight ψ-chain resolver traits, marker traits, ResolverCategory, MAX_RESOLVER_TUPLE_ARITY, resolver! macro - Section 06 Scenario 1: catamorphism step extended with all twenty-one Term variants including the ψ-chain fold-rules consulting ResolverTuple - Section 07 deployment view author's executable: include axis impls + resolver impls as monomorphized native code - Section 08 PrismModel trait signature: <H, B, A> → <H, B, A, R>; forward call updated to run_route::<H, B, A, R, Self>(input, &axes, &resolvers) - Section 09 ADR-020 Consequences + ADR-022 D4/D5/D6 Consequences: trait signature, model-author impl example, run_route signature, and reconciled rejected-alternative count for D4 - Section 10 QS-01: per-variant fold-rule recital extended with the resolver-bound and resolver-free ψ-chain variants - Section 12 glossary PrismModel entry: signature + forward call updated - Section c4 workspace.dsl: bridge component + vocabulary re-exports include ResolverTuple cluster - Section 15288 technical.adoc + technical-management.adoc: add ResolverTuple as fourth model-declaration substrate parameter alongside the three substitution axes All 8 validators pass; Stage 5 idempotence check clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 10, 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
  • ADR-022 reconciliation + ADR-023: input-binding gap closure ADR-022 + ADR-020 needed reconciliation with the 0fd0c03 implementation surface, plus closure of one architectural gap (M::Input → CompileUnit binding-table mechanism, ADR-023). ADR-022 updates: - D2: arena slice form is canonical (TermArena<CAP> on the trait would require generic_const_exprs); from_slice constructor remains for callers that explicitly want the arena form. - D3: closure-body grammar specified per-form (G1-G11) — replaces prior phrase-level enumeration. Adds Lift/Project (G4/G5, previously omitted), reserves name_index sentinels (0 for `input`, u32::MAX for wildcard / default-propagation). - D4: ConstrainedTypeShape is unparameterized; Input adds IntoBindingValue bound, Output adds GroundedShape bound. - D5: forward body calls run_route which reads arena_slice() (D6) and serializes the input via IntoBindingValue (ADR-023). - D6 (new): FoundationClosed trait surface — one method, fn arena_slice() -> &'static [Term]. ADR-020 updates: Decision text declares the FoundationClosed trait surface and removes "(proposed name)" hedges (both names ratified in source). Section 8 PrismModel Contract trait body matches the new D4 form. ADR-023 (new): Foundation declares IntoBindingValue trait that any ConstrainedTypeShape used as PrismModel::Input MUST implement. pipeline::run_route serializes the input value into a transient BindingEntry for Term::Variable { name_index: 0 }. Closes the gap that blocked correct catamorphism execution for non-empty inputs. Glossary: FoundationClosed entry reflects new method-on-trait surface; new IntoBindingValue entry; G.3 conditional skipped (no existing TermArena entry). Asciidoctor edge cases fixed: bare `_` inside backticks (parsed as italic emphasis, produced malformed XML pandoc choked on, silently dropping ADR-023 + (D2) Rejected); `prism's seal regime` and `forward's body invokes ... lower-level pipeline::run` (close- backtick + apostrophe-s + later open-backtick mis-parsed). Edits above plus the underscore-passthrough wrap (++`_`++) make the docbook well-formed throughout. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 7, 2026
  • Align iso/categorical-prism wording with hylomorphism framing Section 8's Anamorphism subsection establishes the structure is explicitly *not* a categorical iso and the trait does *not* realize the categorical Prism optic, but ~12 sites elsewhere still used the older typed-iso / categorical-iso / categorical-prism wording. Reframed each site to hylomorphism-with-verifiable-round-trip; added a Hylomorphism glossary entry (term was used in 6 sites but undefined). Also fixed a forward-signature typo in section 5.1's PrismModel description (-> Grounded<Output> -> Result<Grounded<Output>, PipelineFailure>) and resolved a direct contradiction in ADR-020's rejected-alternative-2 (claimed PrismModel realizes the categorical Prism optic while the Decision says it does not). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 7, 2026
  • ADR-022: PrismModel implementation surface decisions (resolves 2 contradictions + 3 gaps) User identified 5 issues with ADR-020 / surrounding spec — two contradictions where the foundation source as currently written cannot satisfy ADR-020's commitments, and three gaps where the architectural decision was delegated to the implementation by silence. Each requires explicit architectural resolution before the prism_model! macro + foundation surface can land. ADR-022 codifies five resolutions, each binding on the foundation/prism implementation: D1 - FoundationClosed seal mechanism. The supertrait Sealed lives in #[doc(hidden)] pub mod __sdk_seal {} — the standard ecosystem idiom for cross-crate-extensible-but-controlled traits. The proc-macro names prism::__sdk_seal::Sealed when emitting impls; external crates that name the module are architecturally non-conforming. Closes the contradiction where pub(crate) Sealed would prevent the SDK macro from emitting impls. D2 - TermArena const construction. Foundation adds pub const fn TermArena::from_slice(slice: &'static [Term]) -> Self. Macro emits 'const ROUTE_SLICE: &'static [Term] = &[…]' plus 'const ROUTE: TermArena = TermArena::from_slice(ROUTE_SLICE)'. Existing &mut self push API preserved; from_slice is purely additive. Closes the contradiction where TermArena's public API does not admit const construction. D3 - Route declaration syntax. Closure-bodied 'route' function inside the prism_model! invocation; macro parses Rust expressions into Term trees at expansion time. Closure body never executes as Rust. Foundation-vocabulary closure check emits compile error pointing at offending call site. Resolves the gap where the macro's input grammar would otherwise become de facto architecture. D4 - Substitution-axis selection. Trait parameterized by axes: PrismModel<H: HostTypes, B: HostBounds, A: Hasher>. Author selects axes at the impl site. Trait stays at 3 associated types (Input, Output, Route). Each impl is one member of the H-indexed family of carriers (ADR-019 *Consequences*). Resolves the gap by the cleanest of three alternatives (six-assoc-type form rejected as conflating model declaration with carrier selection). D5 - Catamorphism call-site. Foundation exposes prism::pipeline::run_route<H, B, A, M: PrismModel<H, B, A>> (M::Input) -> Result<Grounded<M::Output>, PipelineFailure> as the higher-level entry point. PrismModel::forward calls run_route. Lower-level pipeline::run remains for callers that construct CompileUnit themselves. Resolves the gap by keeping the macro at the architectural layer rather than coupling it to foundation's CompileUnit internals. Five rejected alternatives recorded (one per resolution). Cross-references applied: - ADR-020 *Consequences* now names the seal idiom by reference, points at the H-indexed-family parameterization, and names the run_route call-site (each cites ADR-022). - Section 8 PrismModel Contract subsection rewritten to show the parameterized trait signature (with the [source,rust] declaration) and the ADR-022 cross-references in each cell of the contract table. - Glossary entries for FoundationClosed and PrismModel updated with the parameterization, the seal idiom, the run_route call-site, and the closure-bodied syntax. Build hiccup en route: asciidoctor parsed __sdk_seal as italic emphasis (double-underscore = unconstrained emphasis even inside inline backticks). Wrapped each occurrence in ++…++ passthrough form. The pandoc step had been silently dropping ADR-022 from the rendered .md because the malformed XML failed mid-conversion. Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds. ADR-022 + 4 cross-references render in 09-Architecture-Decisions.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 7, 2026