Skip to content

History / 11 Technical Risks

Revisions

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

    @afflom afflom committed May 22, 2026
  • ADR-058/059 consistency pass: glossary terms, strategy row, QS-05 T2 cross-ref, TR-22 Closes the cross-chapter gaps an audit surfaced after landing ADR-058/059, so the compression-operator reading and operator-geometry codomain are consistently referenced wherever their coined terms appear (κ-derivation / Atlas / ResGraph / operator-geometry are used across chapters 5, 8, 9, 12). 12 glossary: add entries for κ-derivation, compression-to-canonical-form, closure-lossless taxonomy (T1/T2/T3), operator-geometry coordinates, Atlas of Resonance Classes, ResGraph — coined terms used in multiple chapters that lacked definitions. 11 technical risks: new TR-22 — Atlas / exceptional-structures codomain typing is conceptually committed (ADR-059) but code-realization-deferred to application-level / demand-driven Layer-3 per ADR-031 + ADR-059 rejected-alt-7. Scopes the risk to applications electing the finer operator-geometry-codomain-typed admission vocabulary; records that the framework's core commitments (κ-label byte-coordinate, T1/T2/T3 taxonomy, coarse convergence-tower stratification) are substrate-native and carry no dependency on the Atlas realization. 10 quality requirements: QS-05 (replay equivalence) response measure now reads TC-05 trace-replay equivalence as ADR-058's T2 tier (κ-label-identity), and states substrate-independence is binary (conforming → byte-identical certificate; non-conforming → fail closed), no statistical-regression form. 04 solution strategy: new strategic-decision row committing the κ-derivation-as- compression reading (ADR-058) and the Atlas/E₈ codomain (ADR-059), matching how the Fold-Fusion Principle (ADR-054) conceptual reading is captured in the same table. Audit found no semantic inconsistency — substrate-independence was already binary across the wiki; these are cross-reference / glossary completeness fixes. Domain- neutrality preserved. All eight validators (V1–V8) pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

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

    @afflom afflom committed May 15, 2026
  • Wiki cleanup: restructure substrate-amendment audit trail; tighten three-fusion-layers duplication; cross-ref TR-14/TR-15 to ADR-055 Three high-impact cleanup items from the post-ADR-055 audit: (1) ADR-013/TR-08 substrate-amendment audit-trail restructured. The mega-paragraph at §9 line 190 (1,084 words classifying ADR-038..ADR-055 as substrate amendments or not) becomes a compact reference table with one row per ADR carrying the yes/no/wire-format-only verdict and a one-sentence summary. Cognitive load down ~70%; all architectural content preserved in scannable form. The ADR-037 reconciliation prose stays as introductory context; the table is the audit trail. (2) Three-fusion-layers verbatim duplication tightened. §4 Strategic Decisions row 55 and §8 Closure Across Layers concluding paragraph both carried the same 3-fusion-layers enumeration verbatim (macro-expansion / catamorphism / monomorphization, with identical sub-bullet phrasing). Both passages now cross-reference ADR-054 / ADR-055 in §9 as the canonical locus for the detailed mechanics; each chapter keeps its scope-appropriate framing (strategic commitment in §4; closure-across-layers reading in §8) without re-stating the full layer mechanics. ~800 words saved while preserving the chapter-cohesive architectural framings. (3) TR-14 (ψ-residuals discipline) and TR-15 (RESOLVER_ABSENT) gain post-ADR-055 cross-reference notes. TR-14's mitigation is now connected to the verb-body/resolver-body scope boundary per ADR-046 and the universal substrate-Term verb body discipline per ADR-055/TR-20. TR-15 clarifies that resolver-tuple selection is independent of axis bodies — resolver-absent retains its runtime mechanism while axis-body discipline moved to compile-time enforcement via ADR-055. TR-20 already references ADR-055 from prior commit; the cluster TR-14/TR-15/TR-20 now reads as a coherent post- ADR-055 surface. All 8 validators pass; wiki end-to-end consistent; auto cache-clear from prior commit kept the build pipeline clean throughout. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • ADR-055: universal substrate-Term verb body discipline — fold-fusion guaranteed for every axis impl via type-system enforcement Implementer experience proved the standard-library-only scope of ADR-054's canonical axis impl body discipline (ADR-054 RA2) load-bearing for prism's fold-fusion guarantee. An application-author custom axis with an arbitrary-Rust body produces a Term::AxisInvocation whose body the catamorphism cannot reach; the structural-inference guarantee per ADR-001 + ADR-019 fails at that axis's surface; C2's "one Rust function per forward invocation" claim is provisional, not universal. ADR-055 supersedes ADR-054 RA2 with a universal commitment enforced at compile time: - Foundation declares the sealed `SubstrateTermBody` supertrait on `AxisExtension`. Every axis impl (standard-library AND application- author custom) MUST provide a `body_arena() -> &'static [Term]` accessor returning the Term arena slice the kernel decomposes to. - The catamorphism's `Term::AxisInvocation` fold-rule per ADR-029 recursively folds the axis impl's `body_arena()` slice rather than calling an opaque kernel function. Fold-fusion's structural reach extends to the leaf level across every axis surface for every axis impl. - The `axis!` SDK macro per ADR-030 + ADR-052 extends with a normative `body` clause; the macro emits both `AxisExtension` and `SubstrateTermBody` impls together. Axes lacking a `body` clause fail to satisfy the supertrait bound and fail to compile. - ADR-010's arbitrary-Rust Hasher carve-out is amended: HashAxis impls (per ADR-031's HashAxis-from-prism-crypto framing) are axis impls and follow the universal discipline. Standard-library impls already satisfy this per ADR-054's canonical discipline; application-author custom Hashers provide a `body` clause too. Migration: pre-ADR-055 axes with arbitrary-Rust kernels have two paths per ADR-019's initial-algebra commitment: (1) decompose to substrate Terms via the closure-body grammar; (2) move the off-substrate kernel out of the axis surface to a host-boundary wrapper around `forward(input)`. No third option — operations that cannot be expressed in substrate Terms are not prism operations. Updates across the wiki for consistency: - §4 Strategic Decisions row updated to reflect universal scope and drop the standard-library-only framing. - §8 Closure Across Layers concluding paragraph updated similarly. - Conceptual Model intro C2 mechanism updated; "structurally guaranteed by the type system, not aspirational." - ADR-013/TR-08 substrate-amendment paragraph + typed-iso surface consolidation paragraph extended with ADR-055. - TR-20 rewritten: discipline regression is now a compile-time error, not a runtime / inclusion-criterion concern. Migration risk for pre-ADR-055 axes documented. - ADR-054's Rejected alternative 2 marked `(*superseded by ADR-055*)` with the supersession reasoning preserved per the feedback-implementer-loop discipline. - Glossary: new `SubstrateTermBody` trait entry; `Substrate-Term verb body` entry updated for universal scope. Wire format unchanged. All 8 validators pass on clean rebuild. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • Eradicate \`-escape rendering artifacts: AsciiDoc {empty} boundary attribute + passthrough conversion for angle-bracket spans Root cause: AsciiDoc smart-quote substitution + Pandoc DocBook→markdown backtick-escape interaction. When an AsciiDoc inline code-span `text` is immediately followed by a trigger character (letter, ASCII apostrophe, or ASCII double-quote), Pandoc escapes the opening backtick because the smart-quote substitution makes the code-span boundary ambiguous in markdown. Result: literal `\\`text` artifacts in the rendered wiki — the closing backtick is consumed by the entity, and the opening backtick appears as `\\`` text rather than a styled code span. Two-part fix: (1) Insert AsciiDoc `{empty}` attribute substitution between the closing backtick and the trigger character via a state-machine parser (`/tmp/fix_backtick_boundary.py`). `{empty}` is a zero-width attribute that breaks the AsciiDoc/Pandoc bonding without affecting rendered output. The parser tracks opening/closing backtick pairing using AsciiDoc constrained-span rules (opening flanked by start-of- line, whitespace, or specific opening punctuation; closing flanked by non-whitespace), so it only inserts at true closing positions. Applied 462 fixes across 14 .adoc source files (12 arc42 chapters plus 2 ISO 15288 lifecycle pages). (2) Convert 6 specific AsciiDoc inline code spans containing `<...>` angle brackets to `++...++` passthrough form. AsciiDoc inline code spans wrapping content with HTML-significant characters get the angle brackets escaped through the DocBook→markdown conversion, producing literal `\\<` and `\\>` plus the opening-backtick escape. Converting these to `++...++` passthrough preserves the content verbatim (the rendered output remains code-styled monospace). Fixed spans: ADR-026 G6 (match grammar, 4 spans); glossary's first_admit + fold_n + Term::FirstAdmit grammar forms. Build pipeline preserved; all 8 validators pass on clean rebuild (vendor/arc42-generator/build/ cleared); zero `\\` artifacts remain in any of the 22 rendered wiki pages. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 15, 2026
  • Post-ADR-054 consistency: terminology, strategic-decision row, §8 closure paragraph, fold-rule glossary, TR-20 Five remaining gaps closed after the ADR-054 + ADR-031 amendments: - §4 + §8: "application-neutral-within-domain" replaced with "application-neutral" per ADR-031's amendment (3 locations collapsed to 0 stale occurrences). - §4 Strategic Decisions: new row committing the Fold-Fusion Principle (ADR-054) as the architectural mechanism that realizes zero-cost composition end-to-end across all three layers of closure. Three fusion layers (macro-expansion, catamorphism, monomorphization) plus the standard-library canonical axis impl body discipline (ADR-054 + ADR-031). Cross-referenced to the Conceptual Model intro C2 commitment. - §8 Closure Across Layers: concluding paragraph integrating ADR-054. The three-layer closure plus all substrate-amendment series reduce to fold compositions the catamorphism fuses universally. Fold-fusion is the structural mechanism upholding Conceptual Model C2 ("one Rust function per forward invocation" is structurally enforceable, not aspirational). - §12 Glossary: new "Fold-rule" entry (the per-variant evaluation rule the catamorphism applies; 21 Term variants × 21 fold-rules composing universally per ADR-019's initial-algebra property; fold-rules are the building blocks of fold-fusion). - §11 Technical Risks: new TR-20 — canonical axis impl body discipline regression breaks fold-fusion at the leaf level. A standard-library canonical axis impl that regresses to an arbitrary-Rust body (a hand-written compression function, an inlined-via-FFI native primitive) compiles successfully but invalidates the architectural commitment that the catamorphism reaches through the published canonical surface to the leaf level. Mitigation: foundation's code review + CI conformance suite (byte-equivalence against FIPS-180-4 / FIPS-202 / BLAKE3 spec / secp256k1 SEC 2 §2.4.1 / BLAS integer-precision / FHE correctness predicates) enforces the discipline per ADR-031 + ADR-054. All 8 validators pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

    @afflom afflom committed May 14, 2026
  • 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
  • Audit-gap-closure pass: ADR-007 fourth-parameter framing, ADR-026 G19 ψ-residuals restriction, Section 8 enriched signature + Hashing Substrate Contract, TR-14 + TR-15 ADR-007: third-position bound strengthened from A: AxisTuple to A: AxisTuple + Hasher per ADR-036; fourth substrate parameter R: ResolverTuple defaulting to NullResolverTuple noted as parallel substrate parameter (not a substitution axis architecturally) with per-value content provision (instance-associated, value-reference threading) vs per-domain operation kernels (type-associated, type-parameter threading) ADR-026 G19: ψ-residuals discipline restriction surfaced at the G19 grammar form definition — Term::AxisInvocation is a ψ-residual; verb-body emissions are rejected at proc-macro expansion with a closure-violation error citing the verb's name; the variant remains in the substrate for resolver bodies, conformance-corpus generators, foundation-internal trace replay; authors who naturally needed hash(input) in verb bodies express the equivalent through resolver-bound ψ-Term variants whose resolver impls invoke the canonical hash axis internally Section 8 Foundation as a Signature Category — Signature Endofunctor: enriched-signature description extended with substitution-axis-invocation, field-access projection, bounded-search-with-short-circuit, and the nine ψ-chain operators; PrimitiveOp catalog reference updated to snapshot-specific (foundation 0.3.6 canonical catalog); ψ-residuals discipline scopes the verb-body sub-signature Section 8 Foundation as a Signature Category — Catamorphism: carrier parameterization updated to four parameters (H, B, A: AxisTuple + Hasher, R: ResolverTuple defaulting to NullResolverTuple); model declaration's resolver selection participates in carrier determination Section 8 Hashing Substrate Contract: preamble extended to thread the Hasher trait through ADR-030 (consumed via AxisTuple), ADR-031 (HashAxis subsumes the prior Hasher), and ADR-036 (A: AxisTuple + Hasher bound enables resolver-bound substrate operations to consume canonical hash axis type-associatedly) TR-14 (new): ψ-residuals discipline rejects naturally search-shaped verb bodies at proc-macro expansion — structured-error requirements (rejected variant + offending span + ψ-residual category + architectural reason + recommended restructuring path); the discipline is load-bearing for verifiability commitment per ADR-001 + ADR-019; foundation does not relax for application convenience TR-15 (new): RESOLVER_ABSENT runtime path is the only mechanism reporting resolver-absent at evaluation time — NullResolverTuple Null* impls return ShapeViolation carrying RESOLVER_ABSENT shape IRI + foundation-internal discriminator byte; mitigation posture names SDK proc-macro-time warning analysis (paralleling ψ-residuals walk) emitting at compile time when verb-body ψ-Term emissions require categories the model's R doesn't declare; the runtime mechanism is the load-bearing path, proc-macro warning is a diagnostic convenience All 8 validators pass; Stage 5 idempotent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

    @afflom afflom committed May 9, 2026
  • ADR-030 + ADR-031 + Scientific Methods and Results partition (issue #7) ADR-030 — `axis!` SDK macro: universal substrate-extension declaration mechanism. Generalizes Hasher to one axis among many; introduces AxisExtension, AxisTuple, MAX_AXIS_TUPLE_ARITY, AXIS_OUTPUT_BYTES_CEILING. Term::HasherProjection becomes Term::AxisInvocation (Term enum stays at ten variants). Catamorphism's per-variant fold-rule dispatches through A::dispatch(axis_index, kernel_id, &evaluated_inputs). ADR-031 — `prism` is the standard library: a façade over `uor-foundation` plus standard-library Layer-3 sub-crates (prism-numerics, prism-crypto, prism-tensor, prism-fhe) published from the Prism repository. Inclusion criteria, layered consumption pattern, content-addressing invariance, conformance vetting. Repository allocation made explicit: architecture in UOR-Framework, standard library in Prism. Drops prior "blessed" framing. Cross-references: ADR-007 third-position generalization to A: AxisTuple; ADR-013 Consequences extension; ADR-024 axis-declaration mechanism alongside verb-declaration; ADR-026 G19 generalization to axis-trait method calls; ADR-029 fold-rule + Substitution-axis-realized verbs paragraph rewritten for AxisTuple. Section 4 strategic decision row + composition paragraph; Section 8 Closure Across Layers paragraph. Glossary: 11 new/updated entries (axis!, AxisExtension, AxisTuple, AXIS_ADDRESS, AXIS_OUTPUT_BYTES_CEILING, MAX_AXIS_TUPLE_ARITY, Standard-library Layer-3 sub-crate, prism-numerics, prism-crypto, prism-tensor, prism-fhe, Term::AxisInvocation rename). Scientific Methods and Results — new non-normative academic-documentation partition (Director of Research stream per issue #7). Adds src/scientific/Scientific-Methods-and-Results.adoc with the landing-page content; scripts/render-scientific.sh (Stage 3d, mirrors render-15288.sh with reconciliation-gap discipline); Stage 3d wiring in build.sh + Stage 4g in stage-to-wiki-root.sh + render_scientific in validate.sh; sidebar entry in src/wiki/Sidebar.adoc; partition specification in wiki-definition.md (Non-normative content partitions section, source-tree, build-stages, correctness-contract Property 7); SOP in README.md (Robin issues -> wiki maintainer authors AsciiDoc -> build.sh -> commit). Pin refresh: tools/versions.txt java line refreshed from openjdk 21.0.11 to openjdk 21.0.10 (the JDK 21.x actually installed on the build host). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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

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

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

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

    @afflom afflom committed May 4, 2026