Skip to content

History

Revisions

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

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

    @afflom afflom committed May 12, 2026
    75411cf
  • Tighten + clean up: resolve ψ-residuals contradictions, split mega-paragraphs, align glossary ψ-residuals contradiction resolution: - Section 06 Scenario 1 step 9 + Properties bullet 4: drop "Routes whose closure body contains hash(input) invocations emit Term::AxisInvocation"; replace with canonical-hash-axis type-associated framing + ψ-residuals discipline note (resolver impls invoke canonical hash internally; verb bodies do not) - ADR-029 Consequences: rewrite from "model whose route uses hash(input) emits Term::AxisInvocation" to "verb body emits ψ-residual-free Term variants; resolver-bound ψ-Term fold-rules consult R" - ADR-029 Substitution-axis-realized verbs: reframe as substrate context (not verb-body context); explicitly note Term::AxisInvocation is forbidden in verb bodies per ψ-residuals discipline but remains substrate-present for resolver bodies + conformance corpus + trace replay - ADR-029 Catamorphism parameterization in (H, B, A) → (H, B, A, R): four substrate parameters; resolver-bound ψ-Term fold-rules consult R at evaluation time - ADR-030 Term enum's commitment: existing Hasher migration through Term::AxisInvocation removed; canonical hash axis is consumed at certificate-emission stage + internally by resolvers, not by verb bodies; hash(...) identifier remains reserved but verb-body emission is rejected by the ψ-residuals walk Mega-paragraph splits: - ADR-013 Consequences: split one ~10-sentence paragraph into six thematic paragraphs (TR-08 maintenance coupling / three-layer-closure framing / ADR-030+031 universal-extension scope / substrate amendments to date / ADR-035 commitment / ADR-036 supporting surface) - ADR-020 Consequences: split one ~8-sentence paragraph into four thematic paragraphs (compile-time trait commitments / four-parameter PrismModel signature + run_route call-site / Output declaration + value-payload carrier / typed-iso surface summary) Glossary alignment: - Hasher entry: drop "Existing wiki text and ADRs predating ADR-030 use 'Hasher' in the original sense" disclaimer; add ADR-036 + Hasher bound mechanism showing how resolver-bound substrate operations consume canonical hash axis type-associatedly via <A as Hasher>::initial() 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
    67d0ddd
  • Audit-gap-closure pass: ADR-007 fourth-parameter framing, ADR-026 G19 ψ-residuals restriction, Section 8 enriched signature + Hashing Substrate Contract, TR-14 + TR-15 ADR-007: third-position bound strengthened from A: AxisTuple to A: AxisTuple + Hasher per ADR-036; fourth substrate parameter R: ResolverTuple defaulting to NullResolverTuple noted as parallel substrate parameter (not a substitution axis architecturally) with per-value content provision (instance-associated, value-reference threading) vs per-domain operation kernels (type-associated, type-parameter threading) ADR-026 G19: ψ-residuals discipline restriction surfaced at the G19 grammar form definition — Term::AxisInvocation is a ψ-residual; verb-body emissions are rejected at proc-macro expansion with a closure-violation error citing the verb's name; the variant remains in the substrate for resolver bodies, conformance-corpus generators, foundation-internal trace replay; authors who naturally needed hash(input) in verb bodies express the equivalent through resolver-bound ψ-Term variants whose resolver impls invoke the canonical hash axis internally Section 8 Foundation as a Signature Category — Signature Endofunctor: enriched-signature description extended with substitution-axis-invocation, field-access projection, bounded-search-with-short-circuit, and the nine ψ-chain operators; PrimitiveOp catalog reference updated to snapshot-specific (foundation 0.3.6 canonical catalog); ψ-residuals discipline scopes the verb-body sub-signature Section 8 Foundation as a Signature Category — Catamorphism: carrier parameterization updated to four parameters (H, B, A: AxisTuple + Hasher, R: ResolverTuple defaulting to NullResolverTuple); model declaration's resolver selection participates in carrier determination Section 8 Hashing Substrate Contract: preamble extended to thread the Hasher trait through ADR-030 (consumed via AxisTuple), ADR-031 (HashAxis subsumes the prior Hasher), and ADR-036 (A: AxisTuple + Hasher bound enables resolver-bound substrate operations to consume canonical hash axis type-associatedly) TR-14 (new): ψ-residuals discipline rejects naturally search-shaped verb bodies at proc-macro expansion — structured-error requirements (rejected variant + offending span + ψ-residual category + architectural reason + recommended restructuring path); the discipline is load-bearing for verifiability commitment per ADR-001 + ADR-019; foundation does not relax for application convenience TR-15 (new): RESOLVER_ABSENT runtime path is the only mechanism reporting resolver-absent at evaluation time — NullResolverTuple Null* impls return ShapeViolation carrying RESOLVER_ABSENT shape IRI + foundation-internal discriminator byte; mitigation posture names SDK proc-macro-time warning analysis (paralleling ψ-residuals walk) emitting at compile time when verb-body ψ-Term emissions require categories the model's R doesn't declare; the runtime mechanism is the load-bearing path, proc-macro warning is a diagnostic convenience All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 11, 2026
    1b982ea
  • 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
    b2cecf6
  • 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
    b0d98ec
  • 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
    6f3c553
  • Cleanup: remove stray prism-btc / Bitcoin-mining domain examples; keep wiki domain-neutral The wiki accumulated domain-specific examples (prism-btc, Bitcoin proof-of-work, nonce_fiber_traversal, sha256d, MerkleRoot, etc.) as illustrative cases for ADRs that introduced architectural mechanisms. Per the framework's universal-model-compiler scope (ADR-031: prism-btc is one third-party Layer-3 implementation among many; the architecture commits to no specific domain over alternatives), the wiki should be domain-neutral. This commit replaces all such examples with generic framings. ADR-009 (consumer-class IL parameterization): - "Bitcoin Proof-of-Work consumer" -> "content-addressing consumer" - "Financial-substrate / Bitcoin proof-of-work consumers" row -> "Cryptographic-search consumers / High-cardinality bounded first-admission search applications" - "Bitcoin-substrate consumer's V&V plan" -> "cryptographic-search consumer's V&V plan" ADR-022: - D2 closure-body example: sha256d(serialize_header(input.template_prefix, input.nonce)) -> hash(concat(input.left, input.right)); MyHasher -> MyAxisTuple - D3 "prism-btc-shaped failure mode" -> generic "the failure mode the closure-bodied form is meant to avoid" - D4 axis-selection example: (Sha256dHasher,) -> (MyHashAxisImpl,) with hash-axis-as-content-addressing context ADR-024: - Layer-3 verb examples: Sha256Compression, MerkleRootDerivation, Sha256dProjection, HeaderSerialization, NonceFiberTraversal -> "each Layer-3 crate declares verbs whose names and semantics are domain-specific to that crate's substrate" - verb! example: pub fn sha256_compression(...) -> pub fn my_named_verb(...) - Rejected alternative 2: "Bitcoin-substrate implementation's verbs are not appropriate for an FHE-substrate implementation" -> generic Layer-3-vs-Layer-3 framing ADR-026: - "FHE-substrate consumer ... Bitcoin-substrate consumer (W32 fiber, SHA-256d hasher)" -> "FHE-substrate ... cryptographic-search (W32 with content-addressing axis) ... tensor-compute" examples ADR-031: - "Bitcoin, Ethereum, ZK applications" reuse example -> "content- addressing, signature-verification, ZK proof systems" reuse example - "prism-btc crate's Bitcoin-specific verbs" -> generic "third-party crate's application-domain-specific verbs" - "prism-btc depends on prism (consuming HashAxis::sha256 for SHA-256d composition; the prior Sha256dHasher impl migrates to a verb...)" -> generic protocol-specific Layer-3 application crate framing - Bitcoin-substrate / Bitcoin verbs framing in *Context* paragraph -> cryptographic-substrate framing - Consequences "Bitcoin pi-projection / SHA-256d-MAC" example -> "content-addressing search / keyed-MAC computation" ADR-032 Consequences: - prism-btc's nonce_fiber_traversal verb body declares first_admit(W32, |nonce| ...) -> "A model that declares first_admit(W32, |idx| ...) over a 32-bit search domain" ADR-033 Context + Consequences: - prism-btc's nonce_fiber_traversal field example -> generic "representative example: a verb that performs bounded first-admission search over a 32-bit candidate domain" - partition_product!(Prefix76, Target32) -> partition_product!(PrefixShape, ThresholdShape) - input.prefix / input.target / |nonce| -> input.left / input.threshold / |candidate| - "lines 102-104 of crates/prism-btc/src/verbs.rs at HEAD b233785" -> removed (specific cross-repo line reference) - prism-btc's MiningInput -> "Layer-3 crate's Input shape" - "the entire mining inference flows through pipeline::run_route" -> "the entire bounded-search inference flows through pipeline::run_route" - prism-btc's traverse_sequential / traverse_parallel retire -> "Layer-3 implementations that previously carried out-of-band traversal helpers can retire those helpers" ADR-034 Context + Decision + Consequences + Rejected alternatives: - "the prism-btc Bitcoin mining case at WittLevel::W32 requires ~6 hours wall-clock per call" -> "a WittLevel::W32 search domain at 2^32 = 4294967296 candidates would require iterating the full domain ... taking many hours of wall-clock" - prism-btc's ops/traversal::traverse_sequential to retire -> "Layer-3 implementations' bounded-search runtime helpers to retire" - partition_product!(MiningInputShape, prefix: Prefix76, target: Target32) -> partition_product!(MyInputShape, prefix: PrefixShape, threshold: ThresholdShape) (in field-access example) - "for example, nonce in the prism-btc Bitcoin mining verb" -> generic "candidate, key, index" identifier examples - TermValue capacity example "(the prism-btc Bitcoin mining case)" -> "a WittLevel::W32 search domain" - Consequences verb-body example: first_admit(W32, |nonce| hash(concat(input.prefix, nonce)) <= input.target) over MiningInputShape -> first_admit(W32, |candidate| hash(concat(input.left, candidate)) <= input.threshold) over MyInputShape - "Bitcoin mining predicate that calls HashAxis::sha256" -> "content-addressing search predicate" - Rejected alternative 2: "prism-btc's traverse_sequential cannot retire" -> "Layer-3 implementations' bounded-search runtime helpers cannot retire" Final scan: no remaining prism-btc, prism_btc, Bitcoin, sha256d, Sha256d, nonce_fiber, NonceFiber, MerkleRoot, HeaderSerial, Sha256Compression, MiningInput, template_prefix, traverse_sequential, or traverse_parallel references in src/, wiki-definition.md, or README.md. SHA-256 mentions remain only where legitimate (prism-crypto HashAxis families per ADR-031; Hasher contract examples in ADR-008 + section 8 + section 11; structurizr.war SHA-256 build pipeline checksum in 15288 technical-management). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 10, 2026
    3a65899
  • 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
    c2913bf
  • Audit-gap-closure for ADR-034: reconcile ADR-026, ADR-030, ADR-032, ADR-033 Following ADR-034 (Term::FirstAdmit + Term::Recurse iteration-counter binding), several earlier ADRs retained text written against the prior state — first_admit lowering through Term::Recurse, "ten/eleven variants" counts, and three-way responsibility framing where the implementation runtime was load-bearing for structural correctness. This audit pass closes the remaining inconsistencies. ADR-026 reframings: - Operator description for first_admit: lowering target Term::Application chain → Term::FirstAdmit per ADR-034; result shape now coproduct-shaped with structural short-circuit on first admission. - Three-way responsibility paragraph: foundation's catamorphism evaluates Term::FirstAdmit end-to-end per ADR-029's fold-rule; the implementation- runtime override is for strategy (sequential, parallel, GPU-accelerated), not load-bearing for structural correctness. fold_n's split similarly reframed — foundation evaluates Term::Recurse with iteration-counter binding per ADR-034. - iterate_until derivability mention: now lowers through Term::FirstAdmit with predicate body composing the termination condition over the iteration-counter binding FIRST_ADMIT_IDX_NAME_INDEX. - Rejected alternative 3 (first_admit substrate-layer): reasoning updated for ADR-034's reconciliation. The operator stays prism-level; structural correctness is now foundation-level via the dedicated Term::FirstAdmit variant. ADR-030 reframings: - Identifier-resolution order in *Closure check at prism_model! invocation*: aligned with ADR-026 G12's canonical 5-step ordering (added lift/project reserved identifiers; switched to snapshot-specific PrimitiveOp catalog reference; noted binary-operator forms recognized at expression syntax level). - Consequences: extended forward-reference from ADR-033 (eleventh) to also note ADR-034's twelfth variant. ADR-032 reframings: - Context paragraph: noted that the original Term::Recurse lowering target shifts to Term::FirstAdmit per ADR-034, while the cardinality-introspection mechanism this ADR introduces remains the source of the literal ADR-034's lowering reads as domain_size_index. - Consequences: foundation's catamorphism iterates idx ascending across [0, CYCLE_SIZE) per the Term::FirstAdmit fold-rule with structural short- circuit (per ADR-034), not unconditionally per the prior Term::Recurse- based reading. ADR-033 reframings: - Consequences: "eleven-variant Term enum" extended with forward-reference to ADR-034's twelfth variant FirstAdmit; catamorphism uniqueness property preserved across all twelve variants. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

    @afflom afflom committed May 9, 2026
    5211eb5
  • 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
    3a62f34
  • Close audit gaps after ADR-024..029: Term variant count, BBV, runtime view, constraints, risks, glossary, C4, 15288, QS-01 Audit found nine categories of inconsistencies and gaps remaining after the three-layer closure ADRs landed. Each is fixed: 1. Term variant count (9 → 10): three sites that said "nine variants" or enumerated 9 names without HasherProjection updated to ten with ADR-029 cross-reference (08_concepts §Initial Algebra and PrismModel Contract Route description; ADR-020 Decision). 2. Section 5 (BBV): pipeline component now describes pipeline::run_route call, IntoBindingValue serialization, ROUTE_INPUT_BUFFER_BYTES / ROUTE_OUTPUT_BUFFER_BYTES / FOLD_UNROLL_THRESHOLD ceilings, and ADR-029's per-variant catamorphism evaluation populating the Grounded value payload via output_bytes(). Operation declaration component names verb!/use_verbs! macros and the seven prism operators. Vocabulary re-exports lists IntoBindingValue, GroundedShape, output_shape!, and the 10-variant Term enum. Shape macros entry adds output_shape! and clarifies which traits each shape macro emits. 3. Section 6 (runtime view, Scenario 1): step 7 expanded with per-variant fold-rules from ADR-029 — Literal, Variable (with IntoBindingValue lookup), Application, Lift/Project, Match, Recurse, Unfold, Try, HasherProjection (substitution-axis-realized verb). Step 9 notes that the application reads output via output_bytes(). Hasher invocation property amended to distinguish certificate- emission (exactly once) from HasherProjection invocations (per route-author request). 4. Section 2 (constraints): TC-02 names GroundedShape, FoundationClosed, IntoBindingValue, and the __sdk_seal::Sealed idiom as the SDK-macro sealing extension. TC-03 cites ADR-029 for the catamorphism's per-variant fold-rules. TC-04 names ADR-024's three-layer closure check as part of bilateral enforcement. 5. Section 11 (technical risks): added TR-10 (foundation-fixed buffer ceilings reject oversized inputs/outputs at runtime), TR-11 (verb- graph cycle detection produces complex error spans for deeply- linked verbs), TR-12 (prism_model! identifier-resolution shadowing between PrimitiveOp names and verb names), TR-13 (catamorphism evaluation stack depth on small-stack targets). 6. Section 10 QS-01 (zero-cost runtime): response measure now includes the catamorphism's fold-rule cost, IntoBindingValue serialization cost, and output-buffer accumulation cost as monomorphized parts of the executable's runtime. 7. Glossary: added GroundedShape (the trait that gates Grounded<T> carriership, sealed via __sdk_seal pattern, generalized through output_shape! per ADR-027); added ROUTE_INPUT_BUFFER_BYTES (the foundation-fixed input-serialization ceiling per ADR-023); added prism_model! (the SDK proc-macro entry point listing all reserved macro-vocabulary identifiers). 8. C4 workspace.dsl: added outputShapeMacro component to uor-foundation (parallel to product/coproduct/cartesian shape macros, emits ConstrainedTypeShape + Sealed + GroundedShape + IntoBindingValue per ADR-027). Updated operationDeclarationComp description to name the seven prism operators and the prism_model!/verb!/use_verbs! macros. 9. 15288 technical.adoc: load-bearing ADRs list now includes ADR-024 (three-layer closure spine). Design definition's cross-cutting concepts list adds ADR-024 (three-layer closure), ADR-025 (substrate operator set), ADR-026 (prism operator set), ADR-029 (catamorphism evaluation), and ADR-027+ADR-028 (typed-iso surface value-payload carriership). Verification section names ADR-029's per-variant fold-rules and the catalog/transition-table conformance test vectors as V activities. V2 docker pipeline is currently blocked by Cloudflare rate-limiting on Maven Central from the docker container's IP (retry-after: 219-283s on each request, with each retry refreshing the limit). The other seven validators (V1, V3, V6, V7, V8) all pass; V4/V5 skip-upstream on V2's failure. The rendered .md files at the wiki root remain at the state from commit 8d6e471 and will regenerate on the next successful V2 run; this commit only updates source AsciiDoc and C4 DSL. Regenerated C4 SVGs are included from V3's successful run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

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

    @afflom afflom committed May 7, 2026
    e997713
  • Codify V&V framework alignment under hylomorphism framing (ADR-021) Resolves the four open V&V decisions from the V&V framework recommendation against the categorical structure ADR-019/020 established. Each decision sharpens under the hylomorphism + catamorphism + anamorphism + trace-as-witness framing rather than needing a separate V&V apparatus. ADR-021 codifies four decisions: D1 - Context of Use: 'UOR Framework as a production substrate for compiled prism applications, with the catamorphism + anamorphism pair providing internal round-trip verification.' The published UOR Foundation mathematics is the validation referent (D2), not a separate CoU. D2 - External referent: stratified validation. The published UOR Foundation mathematics is the external referent (governs spec faithfulness; verified by Oberkampf-Roy code verification + the Lean 4 corpus's zero-sorry proofs). The trace is the *internal* referent (governs implementation reproducibility; the round- trip property is normative, not a test fixture). D3 - Independence: structural and built-in. prism is the V agent (catamorphism); prism-verify is the IV&V agent (anamorphism); the trace is the artifact crossing the V/IV&V boundary. Independence-by-construction since the anamorphism's contract precludes re-running the catamorphism (TC-05). External IV&V remains additional, not substitute. D4 - Integrity Level: per-consumer-class. PRISM-substrate floor is IL 3, justified by TC-01 + the seal-regime + content-addressing embedding property (section 8) lowering the dynamic-validation burden. Consumer-class bands documented (entertainment IL 1, financial IL 3, cryptographic IL 3-4, safety-of-life IL 4). IL 3 deliverable set enumerated; IL 4 adds independent assurance review + GSN v3 formal arguments + hazard analysis. Four rejected alternatives recorded: - Sole CoU = published mathematics (architecture is realized in the substrate; that's what conformance is checked against). - Single-referent validation with round-trip as a test fixture (round-trip is normative under ADR-019 + TC-05). - External IV&V as the sole independence mechanism (cata/ana split is structurally the V/IV&V split). - Single global IL (consumer-class span requires parameterization). Cross-referenced from chapter 7 lifecycle Verification + Validation sections: Verification: prism is the V agent; the catamorphism direction; Lean is the formal artifact for the external referent. Validation: prism-verify is the IV&V agent; the anamorphism direction; the trace is the witness crossing the V/IV&V boundary; the round-trip property is an IEEE 1012 V&V activity (not a behavior-test fixture); IL band per consumer class. The architecture formalization grep targets in the V&V framework recommendation (uor-architecture-formalization.md) reference a file not in the workspace; those edits are out of scope for this commit. Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 7, 2026
    8d7e87d
  • Suppress relationship labels: Structurizr's auto-sized boxes overflow into adjacent boxes' content User report: 'overflow is so bad that it's running into other boxes' content.' Diagnostic confirmed all 59 residual overflows were on relationship-label rects (boxes <200 px wide); element descriptions fit cleanly inside the wider boxes the prior commit (3d51d4e) sized via explicit width/height on the styles block. Structurizr's CLI SVG export sizes the bounding box for a relationship label using a font metric narrower than the rendered Tahoma actually consumes. Even single-word labels at 14 px overflowed by 15-22% (e.g., 'mint primitives' needed 105 px in a 91 px box; 're-exports' needed 70 px in a 64 px box). At those margins, on compact diagrams the spillover crosses into adjacent node boxes — what the user reported. Tried (none of them solved overflow): - 24px → 18px → 14px relationship fontSize. - Setting explicit width 300 → 400 on the relationship style. - Shortening labels to single-word forms ('imports', 'invokes', 'compiles', 're-exports', 'mint primitives'). Even these overflowed. Resolution: drop relationship labels entirely via 'description false' on the relationship style. Arrows still convey direction; chapter prose carries the semantics of every relationship (the L1 system- context, L2 container, L3 component, deployment, and dynamic- scenario chapters all describe their relationships in text). The diagrams become topology-and-direction views rather than carrying in-figure label semantics. Verification: Diagnostic overflow count: 0 (was 59) ./scripts/build.sh: complete; all 8 validators PASS Stage 5 idempotence: holds Arrow path count preserved (e.g., c4-l2-prism-containers.svg has 44 path elements; arrows still draw between elements) Trade-off: dynamic-view step labels (Scenario 1-4 in chapter 6) are also dropped. Chapter 6 prose lists each step explicitly so the sequence semantics survive; the dynamic-view diagrams now show the participants and arrows without per-step verbal annotations. If restoring step labels for dynamic views specifically is wanted, the path is to tag dynamic-view relationships with a custom tag and add a sibling 'relationship X { description true }' style that overrides the global suppression. Left for the user to decide — the visible-overflow problem is the immediate ask. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 7, 2026
    a403c4e
  • Reduce font sizes + shorten labels to fit Structurizr's auto-sized rects User report: 'all of the diagrams are rendering correctly now, but their text is overflowing.' Three coupled root causes: (1) Structurizr's default relationship-label font is 24px. At 24px, even short two-word labels like 'compiles' (~106px wide) overflow Structurizr's auto-sized box (~95px wide). (2) Container/component descriptions render at 24px and edge past the 450px container box (e.g., 'the cross-crate construction surface.' needs ~488px). (3) Dynamic-view step labels carried both my own 'N. ' prefix and Structurizr's auto-numbering 'N: ' prefix, producing '1: 1. invokes Grounding;' — twice the necessary length. Fix: - Add explicit fontSize overrides to the styles block: element 'Element' → 28px (default for unnamed) element 'Person' → 28px element 'Software System' → 28px element 'Container' → 26px element 'Component' → 24px relationship 'Relationship' → 14px, width 300 - Drop my own 'N. ' prefix from every dynamic-view step label (Structurizr auto-numbers; the duplicate created '1: 1. text'). - Shorten remaining relationship labels to single-/two-word forms fitting in Structurizr's narrow auto-sized boxes: 'calls mint primitives' → 'mint primitives' 'imports + provides shapes' → 'imports + provides' 'returns sealed outputs + traces' → 'returns sealed outputs' 'submits verifier source' → 'submits source' 'returns Certified or ReplayError' → 'returns Certified' L3-internal 'Invokes crate-internal constructors of' → 'invokes' L3-internal 'Builds on substitution-axis traits from' → 'uses' L3-internal 'References PrimitiveOp discriminants from' → 'references' 'constructs sealed types via' → 'constructs via' 'references vocabulary via' → 'references' The chapter prose carries the semantic detail of each relationship; the diagram labels are now identifier-grade. Some residual overflow may remain on the longest single-word labels (e.g., 're-exports' in a 64px box at 14px estimates 70px, ~10% over). This is Structurizr's rect-sizing algorithm using a narrower font metric than the rendered Tahoma actually consumes; my analysis multiplier 0.50 may overestimate, so visible overflow is likely smaller than the diagnostic counts. Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
    3d51d4e
  • Tighten ADR-019 + ADR-020: enriched signature, hylomorphism, H-indexed carrier, named Route surface Applies the 21 surgical edits in wiki-edits-adr019-adr020.md (file shared in conversation), grouped into five blocks. All edits target the canonical AsciiDoc sources under src/arc42/adoc/; the rendered .md files regenerate via build.sh. Two architectural-choice flags ratified before the edits landed: Edit 3.3 — forward's return type. Option 1 (Result) selected: forward(input: Input) -> Result<Grounded<Output>, PipelineFailure> Aligns with pipeline::run's actual signature. Edit 4.4 — Route's level. Option 1 (associated type) selected: Route is a type-level associated type carrying a marker-trait bound (proposed name: FoundationClosed). Integrates with Rust's trait-resolution machinery (UORassembly, TC-04, ADR-006); the value-level alternative is documented as feasible but rejected here. Block 1 — sharpen the F-structure claim (6 edits): Term has 9 variants (Literal, Variable, Application, Lift, Project, Match, Recurse, Unfold, Try). The pure-F-algebra reading was clean for 4 of them; the remaining 5 require an enriched signature (binding for Variable, sum decomposition for Match, well-founded recursion for Recurse, coalgebraic carrier for Unfold, failure-promote for Try). Section 8 + ADR-019 Decision restate F as an enriched signature; the typed pipeline endofunctor is distinguished from F (the wiki was using 'endofunctor' for both); ADR-019's Rejected alternative 2 reframed accordingly. Edit 1.5 was folded into Edit 1.4 (same paragraph). Block 4 — Route discipline (5 edits): ADR-020 said Route is 'a chain of Term::Application compositions over PrimitiveOp discriminants' — covered only one of nine Term variants and didn't name the macro that emits the route or the marker trait the closure bound rides on. New treatment: Route is a type-level witness emitted by a proc-macro (proposed name: prism_model!) alongside a value-level TermArena slice; the closure bound is a marker trait (proposed name: FoundationClosed) the macro emits an impl of iff every node is foundation-vocabulary. Type-level/value-level split is the canonical Rust idiom for compile-time-checked structured data. Section 8 PrismModel Contract row, ADR-020 Decision, glossary FoundationClosed entry all updated. Block 3 — catamorphism codomain + optic terminology (7 edits): Two coupled corrections: pipeline::run produces Result<Grounded<T>, PipelineFailure>, not 'Grounded paired with Trace' (the trace is recoverable via derivation().replay() — on the anamorphism side, not the catamorphism's codomain); and PrismModel does not realize a categorical Prism optic — the structure is a hylomorphism with verifiable round-trip (catamorphism + anamorphism through a residue). 'iso' wording remains as informal shorthand explicitly flagged. Glossary entries for Catamorphism, Anamorphism, and Fixed point updated; ADR-020 Decision and Consequences updated. Block 2 — H-indexed family (2 edits): The carrier pipeline::run evaluates against is parameterized by the three substitution axes; initiality and uniqueness hold within each fixed selection, and across selections the carriers differ as an indexed family. ADR-018's capacity completeness is the categorical statement that the indexing is total over HostBounds. Added to ADR-019 Consequences and section 8 Catamorphism subsection. Block 5 — monomorphism embedding side-condition (1 edit): Section 8 said unique-induced maps are mono 'in any category where the carrier is an embedding' without justification. Two mechanisms together establish the embedding: the seal regime gates construction (only the catamorphism produces sealed values, TC-02, ADR-011) and content-addressing makes the catamorphism injective (Grounded<T> carries unit_address + content_fingerprint derived from the originating CompileUnit; distinct Term trees produce values that differ at one of those identity fields, modulo cryptographic-strength collision assumptions on Hasher). Edits split by file: 08_concepts.adoc: 8 edits (1.1, 1.2, 1.3, 2.2, 3.1, 3.2, 4.1, 5.1) 09_architecture_decisions.adoc: 9 edits (1.4, 1.5, 1.6, 2.1, 3.3, 3.4, 4.2, 4.3, 4.4) 12_glossary.adoc: 4 edits (3.5, 3.6, 3.7, 4.5) Three forward-referenced identifiers in the wiki text remain proposed names pending implementation: prism_model! — the route-emitting proc-macro FoundationClosed — the closure-under-foundation marker trait TermArena — the value-level term-arena slice (this one actually exists in foundation/src/enforcement.rs) Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds; ./tests/run-all.sh PASS (59 tests). No SVG churn (no workspace.dsl edits this round). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
    afbdd84
  • Split deployment views: one deployment node per view (autoLayout works) User report: 'the content is just a jumble in the center of the frame, all piled in the middle without organization and unreadable.' Root cause analysis (cumulative-transform layout audit on c4-deployment-application.svg): Outer deployment-node 1 (Application User's Execution Environment) absolute position: (-50, -50), size 707x479 Outer deployment-node 2 (Application Author's Compilation Env) absolute position: (-50, -50), size 776x479 Both top-level deployment nodes anchored at the same point. They were not stacked, not side-by-side — they were drawn on top of each other, with their inner container instances and infrastructure nodes interleaving. autoLayout (whether bare or with explicit tb/lr parameters) does not position multiple top-level deployment nodes within a single Structurizr deployment view; the JointJS-based web UI Structurizr-CLI renders through doesn't compose them. Fix: split each multi-node deployment view into one view per deployment node. autoLayout works correctly when there is exactly one top-level deployment node per view; the inner topology (container instances, infrastructure nodes, intra-node relationships) is laid out properly. Old views (2): c4-deployment-application = authorCompilation + userExecution c4-deployment-verifier = userExecution + userVerification New views (3): c4-deployment-author-compilation c4-deployment-user-execution c4-deployment-user-verification The author→user→verifier flow between environments is conveyed by the dynamic Distribute and Run view (chapter 6, scenario 4) and the prose in chapter 7. The deployment views themselves now focus on what they're best at: the internal topology of one environment. Edits: - src/c4/workspace.dsl: replaced the two old deployment views with three new single-node views, each with bare 'autoLayout'. - src/arc42/adoc/07_deployment_view.adoc: updated the image references from 2 SVGs to 3, with a short connecting paragraph pointing to the dynamic view for inter-environment flow. Layout audit on c4-deployment-author-compilation.svg (new): Outer node at (259, 143), size 2130x1179 Inner elements at (1099, 193), (1656, 262), (1099, 543), (1889, 649), (1669, 699), (309, 718), (1099, 893) All inner elements within the outer node's bbox (259, 143) → (2389, 1322); positions distinct, no overlap. Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds. Stage 4 staged 18 SVGs (was 17 — net +1 because 3 deployment views replace 2; old SVGs deleted). The other C4 SVGs in the diff are timestamp-deterministic from the prior cleanup but rebuild via the autoLayout-revert change in 4d26aeb, so their byte content shifted slightly under non-customized autoLayout — they're rendered with Structurizr's default rank/node spacing now (which produces marginally different positions than the explicit tb/lr 200-250 params). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
    6e6e731
  • Tighten C4 diagrams: short relationship labels + strip metadata footer User report: 'jumbles of boxes and text, large wasted white space, strange dimensions.' Two compounding issues: 1. Relationship labels were authored as multi-paragraph prose (e.g., 'Declares bounds against; consumes type-declaration vocabulary, mint primitives, and wire-format type definitions from'). Structurizr wrapped each long label across many lines and placed them on every relationship arrow. On deployment views with 3 container instances per environment, the same long label repeated for each instance, producing wall-of-text labels that visually dominated the topology — the 'jumble of boxes and text.' 2. Even after the previous viewBox-cropping commit (427f848), the structurizr-injected diagram-title (font-size 36px) and description (font-size 24px) sat at the bottom of the canvas regardless of content extent. The cropper correctly included them in the bbox, but they sat ~400px below the actual diagram, producing the wasted whitespace gap visible in the deployment views (which were 825x2021 — 1:2.5 aspect ratio). Fix: (1) Shorten every relationship label in src/c4/workspace.dsl to <40 chars, following C4 convention (short labels; chapter prose carries the detail). Container-level relationships, deployment- internal relationships, dynamic-view step labels, and component- level relationships all reframed: 'Declares bounds against; consumes type-declaration vocabulary, mint primitives, and wire-format type definitions from' → 'depends on' 'Calls mint primitives at the Datum/Triad/Derivation/ FreeRank admission stages of pipeline::run' → 'calls mint primitives' 'Linked statically against; invokes pipeline::run' → 'linked' 'Imports prism; provides ConstrainedTypeShape declarations, Grounding impls, ...' → 'imports + provides shapes, Grounding, axes, input' 'Compiles against uor-foundation' → 'compiles' ... (~30 labels reframed) (2) Extend v3-structurizr.sh's Phase 2.5 metadata stripper to remove the diagram-title (font-size 36px) and description (font-size 24px) wrapper blocks alongside the existing timestamp removal. All three live in the same recognisable shape: <g id='j_NN' transform='translate(...)'> <g id='v-NN'> <text font-size='(24|36)px' ...><tspan>...</tspan></text> </g> </g> Diagram nodes use different font sizes (33.6px for deployment- node titles, 16.8px for technology labels, 14px for relationship labels), so the (24|36)px filter targets metadata only. The chapter prose in 03_context_and_scope.adoc, 06_runtime_view.adoc, and 07_deployment_view.adoc carries title and description, so embedding them in the SVG was duplicate content. Canvas extents before this commit / after: c4-deployment-application 825x2021 → 825x527 c4-deployment-verifier 776x2021 → 776x527 c4-dynamic-distribute-and-run 1169x2133 → 525x1693 c4-dynamic-principal-data-path 2136x2359 → 1115x1861 c4-dynamic-trace-replay 1482x2329 → 598x1890 c4-dynamic-uorassembly-enf. 2005x2630 → 1340x1890 c4-l1-system-context 3247x1639 → 3068x1040 c4-l2-prism-containers 2814x4484 → 2561x3758 c4-l3-foundation-components 4848x3873 → 4668x3548 c4-l3-sdk-components 3686x2681 → 3499x2327 c4-l3-verify-components 2708x1286 → 2528x1106 Deployment views: 75% height reduction (1:2.5 aspect ratio gone). Dynamic views: ~50% width reduction (the long step-text was the dominant horizontal extent). All views drop ~10-20% in each dimension purely from removing the metadata gap and tightening the labels. Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds. Spot-checked deployment-application.svg's visible text — 64 tspans preserve every node title, technology label, container-instance name, infrastructure-node description, and (now-tight) relationship label. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
    4d26aeb
  • Crop C4 SVG viewBoxes to content extent (fix corner-of-frame rendering) The deployment views rendered as 'jumbled boxes and text in the corner of their frames': the deployment-node and infrastructure-node boxes were drawn correctly, but they sat in the top-left of a 2000x2000 SVG canvas with the bottom-right ~70% empty. The wiki page rendered the SVG at full canvas size, so the actual diagram appeared as a small island in a sea of whitespace. Root cause: the Structurizr SVG exporter emits a fixed canvas size per view (2000x2000 for the deployment views, 5020x4045 for L3 foundation, etc.) regardless of how much room the autoLayout actually consumed. The earlier autoLayout tightening (commit bd1ec6b set 'autoLayout tb 220 150' on deployments) produced compact layouts that no longer filled the canvases Structurizr chose, leaving the corner gap. Fix: post-process every C4 SVG to crop its viewBox to the actual content bounding box plus 24px padding. New library scripts/lib/svg_crop.rb walks the SVG tree, accumulates affine transforms (translate, scale, matrix), computes the bounding box of every visible primitive (rect, ellipse, circle, polygon, polyline, text), and rewrites the SVG's viewBox + width + height attributes. Skips <path> (Structurizr edges, subsumed by the node bboxes the edges connect) and elements with display:none / visibility:hidden / fill-opacity:0 (the hidden-placeholder text Structurizr emits for deployment-node descriptions). Wired into v3-structurizr.sh's existing Phase 2.5 post-processing alongside the timestamp-stripping step. Canvas extents before / after: c4-deployment-application 2000x2000 -> 825x2021 c4-deployment-verifier 2000x2000 -> 776x2021 c4-dynamic-distribute-and-run 1800x2305 -> 1169x2133 c4-dynamic-principal-data-path 3139x2530 -> 2136x2359 c4-dynamic-trace-replay 2333x2501 -> 1482x2329 c4-dynamic-uorassembly-enf. 2664x2801 -> 2005x2630 c4-l1-system-context 3420x1810 -> 3247x1639 c4-l2-prism-containers 2986x4656 -> 2814x4484 c4-l3-foundation-components 5020x4045 -> 4848x3873 c4-l3-sdk-components 3858x2853 -> 3686x2681 c4-l3-verify-components 2880x1458 -> 2708x1286 Width reductions range from 5% (l1, l2, l3) to 60% (deployments) — the deployments were the worst-affected because their compact autoLayout left the most empty canvas. All views still preserve content + footer; the crop adds 24px padding around the content bbox for breathing room. Verification: ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds; viewBox is now content-fitted on every C4 SVG. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
    427f848
  • Make deployment-view nodes visible: dark stroke + off-white fill The two C4 deployment-view diagrams rendered as effectively blank pages on the wiki: deployment-node rectangles had pure-white fill (#ffffff from our style override) and the Structurizr-default stroke (#e6e6e6, a near-invisible light gray). Against the wiki's white page background the deployment-node boundaries vanished — text and inner elements were drawn but the topology's outer containers had no visible edge. Fix: extend the Deployment Node and Infrastructure Node styles in src/c4/workspace.dsl with explicit stroke + strokeWidth, and bump Deployment Node's fill off pure white: element "Deployment Node" { background #fafafa color #000000 stroke #1f2933 strokeWidth 4 } element "Infrastructure Node" { background #dddddd color #000000 stroke #1f2933 strokeWidth 2 } The deployment-node boundary is now a 4px dark slate stroke against a subtle off-white fill — clearly visible at the wiki's rendering scale while keeping the contained infrastructure-node and container- instance boxes the visual focus. Infrastructure Node gets a matching 2px stroke for visual coherence (its #dddddd fill was already visible against white but the boundary was indistinct). Verification: - ./scripts/build.sh complete; all 8 validators PASS; Stage 5 idempotence holds. - Stroke audit on c4-deployment-application.svg: outer-rect strokes are now #1f2933 (was #e6e6e6); no white-on-white surfaces remain. - Only the two deployment SVGs diff (the Deployment Node and Infrastructure Node tags only appear in the deployment views; L1/L2/L3 and dynamic views are byte-identical to 16a8723). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 6, 2026
    9b4e32c