Skip to content

History / 12 Glossary

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
  • Post-ADR-060 consistency sweep: residual byte-width-cap references Closes the current-fact references to removed constants an audit surfaced after landing ADR-060: - 12 glossary `Grounded::output_bytes` entry asserted the value-payload slot is bounded by the removed `ROUTE_OUTPUT_BUFFER_BYTES`; rewritten to the source-polymorphic TermValue carrier (Inline/Borrowed/Stream, no fixed slot). - 09 substrate-amendment audit-trail heading "(ADR-038 through ADR-055)" was stale (table runs through ADR-060); corrected. - 09 ADR-013 substrate-amendment narrative (line 186) and ADR-030 capacity-bound reconciliation asserted the writer-style resolver signature / AXIS_OUTPUT_BYTES cap as current fact; annotated with the ADR-060 amendment. - 09 ADR-050 arithmetic-width references cited the removed TERM_VALUE_MAX_BYTES as the effective width ceiling; reframed to the WittLevel ceiling (WITT_LEVEL_MAX_BITS / carrier_inline_bytes) per ADR-060. - 09 ADR-051 audit-trail row annotated with the source-polymorphic carrier amendment. Remaining byte-width-cap / DefaultHostBounds occurrences are confined to the historical bodies of ADR-018/028/036/037 (each carrying an ADR-060 supersession banner) and ADR-060's own diagnosis/rejected-alternatives — preserved per the historical-record convention. No current-architecture chapter (2/4/5/6/8/10/11) or the OPM Conceptual Model references a removed constant as current fact. 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-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
  • 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
  • ADR-057: bounded recursive structural typing via ConstraintRef::Recurse + foundation shape-IRI registry Adds the foundation-declared ConstraintRef::Recurse { shape_iri, descent_bound } variant (and the LeafConstraintRef::Recurse parallel) for bounded recursive structural typing at the constraint-geometry level, completing the parallel to Term::Recurse at the Term level. Foundation publishes the shape_iri_registry module + register_shape! SDK macro for link-time shape-IRI registration; ψ_1 NerveResolver unrolls Recurse references against the registry up to the descent budget; const-time validation defers Recurse to runtime; partition_coproduct! / partition_product! macros admit recurse(<bound>):<T> operand markers; shapes carrying Recurse constraints saturate CYCLE_SIZE at u64::MAX. Wire format gains a Recurse variant tag carrying (shape_iri, descent_bound); wire-format version bumps. Unblocks bounded recursive structural typing for JSON, XML, code-module ASTs, S-expressions, ASN.1 / Protocol-Buffer message families, filesystem-like hierarchies, and categorical constructions (rose trees, bounded forests, etc.) without per-application const-eval-cycle-break invention. Architecture remains domain-neutral: the use-case scope enumerates illustrative domains; no downstream application crate is named in the substrate description. ADR-013 audit-trail table: new ADR-057 row marked wire-format-amending. ADR-040 future-BoundShape paragraph: replace "hypothetical MultiPrecisionFieldLessEqBound" speculative naming with policy phrasing — any totally-ordered value type with comparison semantics distinct from those the catalog realizes lands as its own distinct BoundShape primitive at the ADR-013/TR-08 amendment boundary. ADR-037 / MAX_RESOLVER_TUPLE_ARITY (3 sites): replace "currently 8, growing with future ADR-013/TR-08 substrate amendments" with structurally-bound phrasing — 8 per ADR-035's eight resolver-bound ψ-stages, tracking any ADR-013/TR-08 amendment that revises card(ResolverCategory). Variadic-generics carve-out: explicitly language-conditioned (Rust's current absence of variadic generics); migration follows the ADR-013/TR-08 rule if variadic generics stabilize. Glossary: ConstraintRef entry adds Recurse variant + foundation shape-IRI registry resolution semantics; LexicographicLessEqThreshold entry's "256^|target|" math notation broke a table cell — rewritten as "256^len(target)" with passthrough markup. 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
  • Post-ADR-055 consistency: close 5 audit-surfaced gaps that contradicted or omitted universal fold-fusion Broader architectural audit after ADR-055 surfaced 5 places where the wiki text contradicted ADR-055's universal scope or omitted its type-system enforcement. Closed each: (1) ADR-031 'Canonical axis impl body discipline' subsection: removed the directly-contradicting clause "Application-author custom axis impls retain the arbitrary-Rust body permission per ADR-010; the discipline applies to standard-library canonical impls only" — replaced with ADR-055's universal scope and SubstrateTermBody supertrait enforcement. Retitled subsection to acknowledge both ADR-054 + ADR-055. (2) §6 Runtime View Scenario 1 Term::AxisInvocation fold-rule description: was "dispatches through AxisTuple selection to the right axis impl's kernel" — updated to "routes through AxisTuple selection to the right axis impl; per ADR-055's universal substrate-Term verb body discipline, the fold-rule recursively folds the axis impl's SubstrateTermBody::body_arena() static Term slice rather than calling an opaque kernel function." (3) §10 QS-06 Source citation: extended to include ADR-054 + ADR-055. The zero-cost typed-bandwidth admission's structural-enforceability claim now anchors on ADR-055's type-system enforcement explicitly. (4) SD2 Principal Data Path narrative C2 commitment: updated to reflect ADR-055's universal scope. The C2 "one Rust function per forward invocation" claim is now type-system-enforced; axis impls without a substrate-Term `body` clause fail to compile. (5) §12 Glossary `axis!` + `AxisExtension` entries: extended trait- contract description to include `SubstrateTermBody` sealed supertrait bound. The closure-check at axis! invocation now verifies substrate-Term decomposability alongside the prior "sealed, deterministic, no_std-clean, output-bounded" properties. Standard-library sub-crate entry: cross-reference updated from "(ADR-054)" to "(ADR-054 + ADR-055's universal scope)". Wire format unchanged. All 8 validators pass on clean rebuild (build/validate.sh + v2-arc42-build.sh now auto-clear caches per the prior commit). Wiki end-to-end consistent with ADR-055. 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
  • ADR-054: Fold-Fusion Principle + ADR-031 amendments + Conceptual Model C2 mechanism ADR-054 names fold fusion as the architectural mechanism that realizes C2 (zero runtime movement per inference per the Conceptual Model's cost commitments). Every prism transformation — verb-body, prism_model route, resolver body, standard-library canonical axis-impl body — is a folding operation, and the catamorphism's initial-algebra universal property (ADR-019) fuses composed folds into one Rust routine per substitution-axis selection. Three fusion layers stack: (1) Macro-expansion fusion — verb-call sites lower to Term subtrees at proc-macro expansion (ADR-024); the verb-call walker is absent at run time. (2) Catamorphism fusion — per-variant fold-rules (ADR-029) compose universally per the initial-algebra property; there is no choice about how to fuse them. (3) Monomorphization fusion — per-substitution-axis-selection Rust routine has no dynamic dispatch and no allocation (TC-01); LLVM inlining collapses per-variant dispatch with fold-rule bodies into straight-line code. Standard-library canonical axis impl body discipline: every published canonical impl carries a substrate-Term verb body, so the catamorphism's structural reach has no opaque axis-kernel boundary inside the published canonical surface. Application-author custom axis impls retain ADR-010's arbitrary-Rust permission. Substrate-Term realization examples cover the operation-space dichotomy: prism-numerics (algebraic/laws-structured — modexp_p, polyeval, gcd, ext_euclidean, field_<op><P>, fma, newton_step, horner) and prism-crypto (cryptographic/iteration-structured — SHA-2, SHA-3, BLAKE3 compression rounds as substrate-Term W32/W64 ops + rotate). Both reduce to fold compositions under the principle. ADR-031 amendments per the implementer patch: - "Application-neutral within domain" → "Application-neutral" with substrate-faithful framing (conventional groupings are presentation conventions, not architectural partitions). - Roster reframed as operational organization, not architectural commitment: reorganizing the roster is admissible operational policy so long as the disciplines (ADR-024 closure, ADR-017 content-addressing, ADR-031 conformance, ADR-054 body discipline) are preserved. - New "Conventional shape and axis naming" section: BigInt<MaxBits>, FixedPoint<I,F>, Tensor<Element,Shape>, Digest<N>, etc. are conventional aliases for substrate-level ConstrainedTypeShape constructions. - New "Canonical axis impl body discipline" section per ADR-054. - Deduped resolver-baselines paragraph; second occurrence updated to drop "application-neutral-within-domain" → "application-neutral". ADR-013 substrate-amendment paragraph + typed-iso consolidation extended with ADR-054 (not a substrate amendment — names a property the architecture already realizes; only substrate-adjacent change is the canonical axis impl body discipline on ADR-031's inclusion criteria). Conceptual Model intro's C2 commitment now points to the Fold-Fusion Principle as its structural mechanism, and SD2 Principal Data Path narrative carries the same cross-reference. Glossary entries added: Fold-Fusion Principle, Substrate-Term verb body. Folding-transformation entry updated to cross-reference ADR-054. Standard-library sub-crate entry updated to reflect the roster's operational (not architectural) framing. 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
  • ADR-050..053: width-parametric arithmetic + wide literal carrier + axis-generic SDK emission + Div/Mod/Pow catalog extension Four ADRs plus two inline amendments commit substrate arithmetic at the full Witt tower, widen the literal carrier to match, and admit parametric impl types in the SDK's axis-extension emission. Per the implementer document (prism repo implementing uor-foundation/SDK). - ADR-050 (width-parametric arithmetic fold-rules) — the ring-axis and hypercube-axis arithmetic PrimitiveOps (Neg/Bnot/Succ/Pred/ Add/Sub/Mul/Xor/And/Or, plus Div/Mod/Pow per ADR-053) evaluate at the full Witt tower with width = max(operand widths) for binary ops. The pre-ADR fold-rules silently truncated to u64, a Correction-4-class soundness gap. Operands wider than result_width are now rejected as ShapeViolation::CardinalityViolation; comparison primitives Le/Lt/Ge/Gt and Concat retain byte-level semantics. - ADR-051 (wide-value Term::Literal carrier) — Term::Literal widens from `value: u64` to `value: TermValue` (byte sequence sized to level.witt_length() / 8). Wide constants become single records instead of Concat-of-narrow chains. SDK helper literal_u64(value, level) preserves the narrow-construction surface. - ADR-052 (axis! macro generic-form emission) — the companion axis_extension_impl_for_<name>! macro accepts :ty (not just :ident), admitting parametric impl types like BigIntModularNumeric<BYTES> without hand-written AxisExtension boilerplate. Existing call sites continue to work; SDK seal discipline per ADR-022 D1 preserved. - ADR-053 (Div/Mod/Pow PrimitiveOp catalog extension) — catalog extends from 15 to 18 variants. Each is a folding-transformation per ADR-053's coined principle (one fold = one Term variant, not multiple Term variants the catamorphism walks). Div/Mod are Euclidean (b=0 → ShapeViolation with the nonZeroDivisor IRI); Pow is square-and-multiply modular exponentiation. Identity individuals DV_1..DV_4 + PW_1..PW_3 added to the Lean corpus commitment. GeometricCharacter gains Quotient/Remainder/ IteratedScaling. Inline amendments: - ADR-026 line ~670: Γ = {Add, Sub, Mul, Div, Mod, Pow} (six ring- axis primitives on Z/(2^n)Z) — corrected from the prior five- element form. Hypercube-axis ops {Xor, And, Or, Bnot} remain separate per the MetricAxis enum. - ADR-031 numerics sub-crate roster: substrate-native ring arithmetic is closed under PrimitiveOp::{Add,Sub,Mul,Div,Mod,Pow}; substrate-native hypercube arithmetic under {Xor,And,Or,Bnot}. BigIntAxis/FixedPointAxis/RingAxis dissolve into the substrate PrimitiveOp catalog at the appropriate Witt-level. FieldAxis retained for prime parametricity (PrimeFieldNumeric<P> instances). prism-numerics' role shifts to publishing shapes plus compound arithmetic verbs (modexp_p, polyeval, gcd, ext_euclidean, horner, newton_step, fma, field_<add|sub|mul|inv><P>). ADR-013 substrate-amendment paragraph + typed-iso surface consolidation paragraph updated. Glossary entries added for Folding-transformation (ADR-053's coined principle), literal_u64 (ADR-051's SDK helper), Term::Literal (wide-value carrier). PrimitiveOp glossary entry updated to 18-variant catalog at the post-ADR-053 snapshot. Gauge-tower Γ entry corrected to the six-element form. 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
  • ADR-047..049: generalize implementer-shipped zero-cost patterns + close upstream items Three coupled architectural commitments close the load-bearing implementer-surfaced gaps from a downstream implementation that shipped a typed-bandwidth admission surface, a UOR observable surface, and an empirical cryptanalysis battery — patterns the architecture must support in a generalized way so any implementor achieves zero-cost operations from the wiki alone. - ADR-047 (σ-Projection Hardening Principle) — commits six structural axioms (U1 marginal-uniformity, U2 joint-independence, U3 admission- orthogonality, U4 avalanche, U5 autocorrelation-flatness, U6 bandwidth-additivity) qualifying Hasher impls as UOR-hardened canonical hash axes per ADR-030. Property axiom on existing substrate constructs; no wire-format change. - ADR-048 (TypedCommitment + 5th substrate parameter) — commits the zero-cost typed-bandwidth admission surface: foundation-declared TypedCommitment: Copy trait with three built-in impls (EmptyCommitment, SingletonCommitment<P>, AndCommitment<A,B>); fifth model-declaration parameter C: TypedCommitment on PrismModel defaulting to EmptyCommitment; the catamorphism's ψ_9 dispatch consults C::evaluate(kappa_label) before sealing the success envelope. Substrate amendment under ADR-013/TR-08; trace gains CommitmentEvaluated event variant; wire-format version bumps. Pulls admission fully inside the catamorphism per the implementer's "residual upstream move" identification. - ADR-049 (UOR observable surface + cryptanalysis battery) — commits four foundation-declared typed observable primitives (Stratum<P>, WalshHadamardParity, UltrametricCloseTo<P>, AffineParity) under ADR-038's closed Observable taxonomy plus a new SpectralObservable subclass; commits axis::cryptanalyze::<H: Hasher>(samples) -> CryptanalysisReport as the substrate-level test primitive witnessing the Hardening Principle's U1-U6 axioms empirically. Substrate amendment under ADR-013/TR-08; new Observable subclasses bump the wire-format version. ADR-013 substrate-amendment paragraph and ADR-020 typed-iso surface consolidation updated with cross-references. Five glossary entries added (σ-Projection Hardening Principle, TypedCommitment, Typed- bandwidth admission, UOR observable surface, UOR Cryptanalysis Battery). All 8 validators pass. The wiki remains strictly domain-neutral: no downstream-implementer crate is named anywhere in src/ or rendered output. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 14, 2026
  • ADR-043..046: close implementer-surfaced gaps in resolver-body discipline + product-field metadata + Grounded::tag affordance Four new ADRs complete the wiki's coverage of architectural surfaces the prism-btc implementation depends on: - ADR-043 (Iterative-Resolution Discipline) — canonicalizes the resolver-internal computational pattern for resolver-bound ψ-stages: FreeRank protocol; bounded-domain enumeration over ConstrainedTypeShape::CYCLE_SIZE; convergence vs exhaustion termination; impossibility-witness emission per ADR-039; host- boundary retry. Not a substrate amendment — canonicalizes existing substrate constructs. - ADR-044 (PartitionProductFields trait) — amends ADR-033's partition_product! emission shape to a split-const form on a foundation-declared trait: FIELDS: &'static [(u32, u32)] + FIELD_NAMES: &'static [&'static str]. Macro-emitted impls and hand-written impls share the same metadata surface. - ADR-045 (Grounded::tag::<NewTag>()) — adds the zero-cost re-tagging consuming method to Grounded<T, Tag>. Preserves the seal regime; applications surface domain-distinct Grounded types without newtype boilerplate. - ADR-046 (Resolver-body discipline scope) — records the boundary between ADR-035's verb-body ψ-residuals discipline and ADR-043's resolver-body iterative-resolution discipline. Structural, not stylistic. Cross-references added to ADR-013 substrate-amendment paragraph and ADR-035 ψ-residuals discipline. Glossary entries added for the new concepts; FreeRank entry cross-references ADR-043. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 13, 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 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