Skip to content

History / 05 Building Block View

Revisions

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

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

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

    @afflom afflom committed May 12, 2026
  • Audit-gap-closure pass for ADR-037/038/039: reconcile stale capacity-cap references and surface verdict realization across sections Stale capacity-cap references reconciled to HostBounds-parametric forms per ADR-037: - Section 05 BBV pipeline component: pipeline::ROUTE_INPUT_BUFFER_BYTES / ROUTE_OUTPUT_BUFFER_BYTES / FOLD_UNROLL_THRESHOLD → <B as HostBounds>::* per ADR-037 - Section 08 Closure Across Layers ADR-034 paragraph: FOLD_UNROLL_THRESHOLD reference now HostBounds-parametric - Section 10 QS-01 response measure: ROUTE_INPUT_BUFFER_BYTES / ROUTE_OUTPUT_BUFFER_BYTES references now HostBounds-parametric - Section 11 TR-10 (foundation-fixed buffer ceilings): description + mitigation reframed; ceilings now HostBounds-parametric per ADR-037; applications declare their own HostBounds or use DefaultHostBounds - Section 11 TR-13 (catamorphism evaluation cost): pipeline::FOLD_UNROLL_THRESHOLD reference now HostBounds-parametric - Section 09 ADR-023 Decision + Rejected alternative 4: ROUTE_INPUT_BUFFER_BYTES references reframed as <B as HostBounds>::ROUTE_INPUT_BUFFER_BYTES - Section 09 ADR-028 Decision (4 references) + Rejected alternative 4: ROUTE_OUTPUT_BUFFER_BYTES references reframed as <B as HostBounds>::ROUTE_OUTPUT_BUFFER_BYTES - Section 09 ADR-030 closure check + per-axis output buffering: FOLD_UNROLL_THRESHOLD / AXIS_OUTPUT_BYTES_CEILING references reframed - Glossary entries (AxisExtension, fold_n, FOLD_UNROLL_THRESHOLD, output_bytes, ROUTE_INPUT_BUFFER_BYTES, ROUTE_OUTPUT_BUFFER_BYTES) updated; the prior foundation-fixed entries marked deprecated and pointing to HostBounds equivalents Verdict-realization surface in non-09 sections: - Section 02 HostBounds substitution-axis row: extended with 14 + 8 ADR-037-migrated associated constants enumerated; DefaultHostBounds default-carry framing; type-system tuple-impl-table caps stay foundation-vetted with explicit carve-out - Section 05 BBV bridge component: surface inventory extended with closed Observable taxonomy (incl. observable:AxisProjectionObservable per ADR-038), closed BoundShape catalogue of 6 (with LessEqBound semantic extension), inhabitance verdict envelope types (cert:InhabitanceCertificate, cert:InhabitanceImpossibilityCertificate, proof:InhabitanceImpossibilityWitness, trace:InhabitanceSearchTrace) per ADR-039 - Section 06 Scenario 1 step 10: extended with the ADR-039 verdict realization mapping for inhabitance-style applications (successful Grounded IS cert:InhabitanceCertificate envelope; κ-label structural witness at ψ_9; concrete cert:witness ValueTuple at ψ_1; cert:searchTrace as Grounded::derivation().replay(); Err(PipelineFailure) IS cert:InhabitanceImpossibilityCertificate envelope) All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

    @afflom afflom committed May 11, 2026
  • Audit-gap-closure for ADR-035/036: reconcile sections 2/3/5/6/7/8/9/10/12 + c4 + 15288 to ψ-chain Term variants and ResolverTuple substrate parameter - TC-03: ten Term variants → twenty-one (original 9 + AxisInvocation + ProjectField + FirstAdmit + nine ψ-chain) - Section 02 substitution-axes: add ResolverTuple subsection as fourth model-declaration substrate parameter per ADR-036 - Section 03 author-input row: include ResolverTuple selection - Section 05 BBV substrate trait list, prism whitebox interface, vocabulary re-exports, bridge component, pipeline component: add ResolverTuple, eight ψ-chain resolver traits, marker traits, ResolverCategory, MAX_RESOLVER_TUPLE_ARITY, resolver! macro - Section 06 Scenario 1: catamorphism step extended with all twenty-one Term variants including the ψ-chain fold-rules consulting ResolverTuple - Section 07 deployment view author's executable: include axis impls + resolver impls as monomorphized native code - Section 08 PrismModel trait signature: <H, B, A> → <H, B, A, R>; forward call updated to run_route::<H, B, A, R, Self>(input, &axes, &resolvers) - Section 09 ADR-020 Consequences + ADR-022 D4/D5/D6 Consequences: trait signature, model-author impl example, run_route signature, and reconciled rejected-alternative count for D4 - Section 10 QS-01: per-variant fold-rule recital extended with the resolver-bound and resolver-free ψ-chain variants - Section 12 glossary PrismModel entry: signature + forward call updated - Section c4 workspace.dsl: bridge component + vocabulary re-exports include ResolverTuple cluster - Section 15288 technical.adoc + technical-management.adoc: add ResolverTuple as fourth model-declaration substrate parameter alongside the three substitution axes All 8 validators pass; Stage 5 idempotence check clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

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

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

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

    @afflom afflom committed May 7, 2026
  • Surface PrismModel + categorical structures (ADR-019, ADR-020) Two related additions that name the structures already present in the architecture and surface the developer's contract for declaring an application as a typed iso between input features and output labels. ADR-019 — Foundation is a closed signature endofunctor; `Term` is its initial algebra; `pipeline::run` is the catamorphism. The wiki has stated TC-01 (zero-cost runtime) and ADR-013 (closure under uor-foundation's vocabulary) as separate properties. They are not separate; they are two halves of one categorical theorem: closure makes F's signature complete; completeness lets the catamorphism be discharged at the application's compile time (TC-04, UORassembly); zero-cost follows. Stating the theorem in its native vocabulary lets later commitments compose against initiality + uniqueness + completeness rather than re-establishing them. The vocabulary uor-foundation gains is editorial: signature endofunctor, F-algebra, initial algebra, catamorphism, anamorphism, fixed point. None names a new runtime concern; each names a structure already present. Naturally extends ADR-007's three-position substrate-vs-implementor pattern: foundation defines the signature endofunctor and initial algebra; prism declares the bound (the F-algebra contract any Route satisfies); the application author selects the F-algebra by writing the model. ADR-020 — `PrismModel` is the application author's contract for declaring a typed iso between input features and output labels. Without a trait, the categorical structure exists but is not actionable: developers assemble ConstrainedTypeShape impls, pick substitution-axis selections, and write hand-rolled Rust to compose them, with no type system enforcing that the composition is the unique homomorphism the architecture demands. Real-world Prism applications observed in the field exhibit exactly this failure mode (the operations are foundation-vocabulary; the composition is hand-rolled outside the type system). `PrismModel` carries Input, Output, Route associated types and forward(input) -> Grounded<Output>. Route's bound is closure under foundation vocabulary, checked at the application's compile time (TC-04, ADR-006). forward is the catamorphism prism derives from Route via initiality of Term (ADR-019); the application author does not write forward's body. The framing the developer reads is Real-Time Inference; the framing the architecture supports underneath is the categorical iso. Both framings are the same statement. Naming considered: Prism (collides with crate name + optic concept), Model (ML connotation: parameterized weights, training), Inference (names the runtime behavior, not the declaration), Route (names a Route component, not the whole iso). Settled on PrismModel as the conjunction with no overload. Edits: - src/arc42/adoc/08_concepts.adoc: two new top-level sections — "Foundation as a Signature Category" (signature endofunctor, initial algebra, catamorphism, anamorphism, fixed points, the closure+TC-01 unification) and "PrismModel" (contract, compilation as monomorphism, Real-Time Inference framing, replay side). - src/arc42/adoc/05_building_block_view.adoc: new PrismModel row in the prism container's Level 3 component table; prism black-box description's author-interface row updated to lead with the PrismModel trait; layered-structure paragraph updated to describe PrismModel sitting at the top of the runtime stack. - src/arc42/adoc/09_architecture_decisions.adoc: appended ADR-019 (signature category) and ADR-020 (PrismModel) after ADR-018, each with three rejected alternatives. - src/arc42/adoc/12_glossary.adoc: 8 new entries — Anamorphism, Catamorphism, F-algebra, Fixed point, Initial algebra, PrismModel, Real-Time Inference, Signature endofunctor — placed alphabetically. Verification: ./scripts/build.sh complete, all 8 validators PASS, Stage 5 idempotence holds, ./tests/run-all.sh PASS (59 tests). No incidental SVG churn (the timestamp-stripping work makes C4 SVGs deterministic across builds). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
  • Adopt HostBounds capacity completeness (ADR-018) ADR-018 declares that every capacity bound flowing along the principal data path is carried by HostBounds, with foundation-global capacity constants and closed foundation-controlled enums explicitly rejected. This commit applies the architectural change across the wiki sources. Eliminated as foundation-global constants: FINGERPRINT_MIN_BYTES -> HostBounds-borne byte-width range (lower) FINGERPRINT_MAX_BYTES -> HostBounds-borne byte-width range (upper) TRACE_MAX_EVENTS -> HostBounds-borne trace event-count ceiling Retained as foundation-fixed: TRACE_REPLAY_FORMAT_VERSION -- protocol identifier, not a capacity. Cross-implementation interoperability requires a single shared format ID. Edits: - 02_architecture_constraints.adoc: HostBounds row in the substitution axes table now enumerates the capacities it carries (fingerprint output width range, trace event-count ceiling, algebraic-level bit-width ceiling, plus extension); names DefaultHostBounds. - 05_building_block_view.adoc: prism-verify Re-exports row, the enforcement::calibrations and enforcement::transcendentals sub- components, the bridge::trace::Trace and bridge::cert::ContentFinger- print rows, and the high-level enforcement-component description all reframed to refer to HostBounds-carried capacities (with ADR-018 cross-references). transcendentals now mentions only the wire-format version constant. - 06_runtime_view.adoc: Scenario 2 verification time bound now reads 'bounded by the trace event-count ceiling carried by the application's selected HostBounds'. - 08_concepts.adoc: Trace events length bound, DatumAdmitted variant width check, and Hashing Substrate Contract output width row all refer to HostBounds-carried ranges. - 09_architecture_decisions.adoc: ADR-007 context expanded with the list of capacities HostBounds carries; ADR-009 rejected alternative reworded; ADR-010 Decision reworded; NEW ADR-018 (HostBounds capacity completeness) appended after ADR-017 with three rejected alternatives (foundation-global constants, closed foundation- controlled enums, fourth substitution axis). - 10_quality_requirements.adoc: QS-03 response measure refers to HostBounds-carried trace event-count ceiling. - 12_glossary.adoc: removed glossary entries for FINGERPRINT_MIN_BYTES, FINGERPRINT_MAX_BYTES, TRACE_MAX_EVENTS; updated ContentFingerprint and HostBounds entries. - src/c4/workspace.dsl: prism-verify reExportsComp description updated to mention 'the HostBounds trait surface (whose associated constants carry every capacity bound) and the wire-format version constant TRACE_REPLAY_FORMAT_VERSION' instead of the deprecated FINGERPRINT_* and TRACE_* constants. The L3 prism-verify component SVG is the only C4 SVG affected by this change (the other 10 are byte-identical to e7508e8 because the timestamp-stripping work makes them deterministic). Verification: ./scripts/build.sh complete (V1-V8 all PASS, Stage 5 idempotence holds). The 2 remaining FINGERPRINT_MAX_BYTES occurrences in 09-Architecture-Decisions.md are ADR-018's intentional contrast of the canonical pattern '[u8; H::FINGERPRINT_MAX_BYTES]' against the non-conforming '[u8; FINGERPRINT_MAX_BYTES]'. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

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

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

    @afflom afflom committed May 4, 2026