Skip to content

History

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
    d08a8c1
  • 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
    032c9ce
  • Add Stage 4b page-size guard so oversized pages fail the build, not the live wiki The 512 KiB truncation that dropped ADR-047..060 from the rendered Architecture Decisions page was silent: V1..V8 run in Stage 2 (before staging) and none checks rendered page byte size, so an oversized page reached the published wiki undetected. Stage 4b now scans every staged wiki page after staging and: - FAILS the build (exit 1) if any page >= 524288 bytes (512 KiB), the point past which GitHub truncates rich markdown rendering; - emits a WARNING if any page >= 471040 bytes (460 KiB), ~50 KiB before the cliff, so growth is flagged before it breaks; - reports the largest page every run. This makes the failure mode surface at build time for every page, not just chapter 9. On first run it already flagged 12-Glossary.md at 491,935 bytes (~480 KiB) — in the warning band, ~32 KiB below the limit — which would have been the next page to silently truncate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 22, 2026
    db099f0
  • Split Architecture Decisions page at ADR-038 (GitHub 512 KiB render limit) The Architecture Decisions chapter grew to ~695 KiB, exceeding GitHub's ~512 KiB per-page rich-markdown rendering limit: the live wiki truncated mid-ADR-46 (ADR-047 began at byte ~512,380, right at the boundary), so ADR-047 through ADR-060 did not render. Fix: stage-to-wiki-root.sh now splits the staged page at the first `## ADR-038 ` heading — the start of the "substrate-amendment audit trail (ADR-038 through ADR-NNN)" cohort. Page 1 (09-Architecture-Decisions.md, ~396 KiB) keeps the chapter intro, the audit-trail table, and ADR-001..037; page 2 (09-Architecture-Decisions-Continued.md, ~300 KiB) carries ADR-038 onward. Both pages are well under 512 KiB, so every ADR renders. New ADRs append to page 2; ADR-001..037 is stable, so the split point and page-1 size do not drift. The split is deterministic (first ADR-038 heading line), so Stage 5 idempotence holds; it runs after image-reference rewriting so page 2 inherits the already-rewritten tail. Cross-navigation links added in both directions; the Sidebar gains a nested "ADR-038 onward" entry under chapter 9. The source stays one .adoc (09_architecture_decisions.adoc), so V1 arc42 structural alignment is unaffected. All eight validators (V1-V8) pass; idempotence check clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 22, 2026
    31d217b
  • 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
    31cfedc
  • 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
    37cd0ee
  • 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
    b0c8df6
  • 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
    847aab5
  • 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
    5b1d388
  • 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
    4d8af3a
  • 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
    9767a9a
  • 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
    d20ed74
  • 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
    7cffe95
  • 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
    41d29b0
  • 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
    5131462
  • build pipeline: clear transient caches at every invocation Stale outputs in vendor/arc42-generator/build/ (gradle/docker incremental cache for the V2 stage) and build/ (top-level stage outputs consumed by V4/V5) have historically masked source-AsciiDoc changes that the incremental-build cache didn't recognize as inputs (boundary attribute insertions, passthrough conversions, narrative-only additions to OPM SDs). Result: rendered .md files did not reflect committed source changes until a maintainer manually cleared the build directories — a foot-gun the build pipeline now removes structurally. Three coordinated changes: - build.sh: new Stage 0 (`clear transient build caches`) nukes build/ and vendor/arc42-generator/build/ before pre-flight runs. Idempotent; both directories are regenerated by every successful build. - validate.sh: same cache clear at the top of the script so standalone validator runs (without going through build.sh) also start clean. V2/V4/V5 can never validate against stale outputs from a prior run. - v2-arc42-build.sh: additional defense in depth — clears vendor/arc42-generator/build/ before staging local sources + docker invocation. Triggers a clean gradle/docker rebuild on every V2 invocation regardless of which top-level entry point launched it. All 8 validators pass on clean rebuild. The architectural guarantee: every validation run reflects the current source tree, full stop. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
    d954ef3
  • 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
    8393f98
  • 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
    c9cdf49
  • 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
    aed8099
  • 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
    1185f75
  • 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
    6af5c12
  • Add ISO standard links + source info to OPM and Lifecycle chapters (issue #8) Per issue #8 (RobinWikoff), pages referencing ISO standards previously named the standard without a clickable link or full edition/source metadata. Added: Conceptual-Model page (OPM, ISO 19450): - Linked ISO/PAS 19450:2015 to iso.org/standard/62274.html and ISO 19450:2024 (Second edition) to iso.org/standard/83454.html. - Added ICS codes (25.040.40, 35.240.50) and an explicit pointer to the wiki's pinned EBNF transcription at tools/iso-19450-opl.ebnf. - Cited supplementary sources: Dori 2002 (CAiSE) and Dori 2016 (Springer) — the canonical OPL production rules pre-dating the ISO standard and the published textbook treatment. - Linked the iso.org/obp free preview for Clauses 1–3. - Noted the standard's patent acknowledgment per ISO/PAS 19450:2015 Foreword. Lifecycle pages (ISO/IEC/IEEE 15288), four chapters covering Clauses 6.1, 6.2, 6.3, 6.4: - Added a `[NOTE]` block at the top of each chapter linking ISO/IEC/IEEE 15288:2023 to iso.org/standard/81702.html, naming the full title, edition, ICS code (35.080), supersession relationship, and joint publication by ISO, IEC, and IEEE. - Linked the iso.org/obp free preview. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 14, 2026
    afc4874
  • Conceptual Model: ISO 19450 framing + cost-model establishment + per-OPD narratives The conceptual model chapter previously rendered as six bare OPD-plus-OPL pairs with a one-line preamble. Two structural problems: (1) no normative context tied each OPD back to ISO 19450's vocabulary or the arc42 chapters that elaborate it; (2) the OPM model derived from prism's architecture, when the conceptual model must instead establish the cost-model that architecture and implementation uphold. Both addressed: - src/opm/intro.md establishes the normative ISO 19450 framing (ISO/PAS 19450:2015 + 2024 second edition; §6 OPD; §7 OPL; §8 generic OPM ontology; bimodal-equivalence principle V6/V7 enforce) AND names four cost-model commitments (C1–C4) the conceptual model establishes for prism: - C1: Operational cost = declared bandwidth at equality (Hardening Principle U6 per ADR-047; Lean tight-bound theorem). - C2: Zero runtime movement per inference (per-invocation cost is O(1) + K·t_eval; no allocation, no dyn, no runtime-unknown loop bounds; #![no_std] posture). - C3: Structural inference, not search (ψ-residuals discipline per ADR-035 + scope clarification per ADR-046; host-boundary retry is external to the catamorphism's per-invocation contract). - C4: σ-projection axis qualification is conceptual (U1–U6 axioms per ADR-047; empirical witness through axis::cryptanalyze per ADR-049; foundation CI enforces). - src/opm/<SD>/narrative.md for each of the six OPDs (SD, SD1-Prism-Structure, SD2-Principal-Data-Path, SD3-Verification, SD4-UORassembly-Enforcement, SD5-Distribute-and-Run) carries: - OPD kind per ISO 19450 §6.5 (System Diagram / in-zoom). - Architectural commitment with explicit ADR cross-references. - Which of C1–C4 the OPD upholds and how. - ISO 19450 vocabulary used (consists of, exhibits, requires, yields, invokes, handles, affects), each cited to §7.3.X. - Arc42 cross-reference to the chapter elaborating the OPD. - scripts/render-opm-index.sh extended to inject the optional top-level src/opm/intro.md after the page heading and the optional per-SD src/opm/<SD>/narrative.md after each OPD's heading. Backward-compatible: SDs without narrative.md render as before (no narrative block). OPL syntax and OPD-OPL coherence validators (V6/V7) are unaffected — they operate on opl.txt and opd.svg only. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 14, 2026
    9c0b1f1
  • 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
    6fe9c1b
  • 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
    de839d4
  • 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
    622b133
  • ADR-037: clarify HostBounds capacity-cap totals (22 migrated + 4 pre-existing = 26) The prior phrasing said "22 new associated constants" without disambiguating the 22 newly-migrated caps (14 free-standing data-shape caps + 8 ψ-stage resolver output ceilings) from the 4 pre-existing HostBounds fields per ADR-018 (FINGERPRINT_MIN_BYTES, FINGERPRINT_MAX_BYTES, TRACE_MAX_EVENTS, WITT_LEVEL_MAX_BITS). Read naively, implementations could miscount the surface or assume the pre-existing fields were superseded. Clarified phrasing makes both groups explicit and notes the 26-constant total. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

    @afflom afflom committed May 12, 2026
    e3ac73d