Skip to content

History / Lifecycle Technical Processes

Revisions

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

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

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

    @afflom afflom committed May 10, 2026
  • 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
  • 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
  • Phase 4 reconciliation: OPM + ISO 15288 sources, V6/V7/V8 all PASS Lands the three transcribed-standard pin files, all six OPM Conceptual Model OPDs, and all four ISO/IEC/IEEE 15288 lifecycle process-group chapters. The wiki state now matches its declared state in wiki-definition.md: every validator runs (no skip-gap), Stages 3b/3c produce committable output, and Stage 5 idempotence holds. Pin files (tools/): - iso-19450-opl.ebnf — OPL formal syntax in ISO/IEC 14977 EBNF. Workspace-authored transcription of ISO/PAS 19450:2015 Annex A. Each production carries an inline source-attribution comment citing the standard plus seven public corroborating sources (Dori 2002, Dori 2016, OPCAT 3.0 manual, Svensson 2004 thesis, OPCloud linkTypeSelection.ts, Wikipedia, ISO 19450 free preview). Coverage: object/process/state declarations, the four fundamental structural relations, transformation links, enabling links, in-out link pairs, tagged structural links, invocation. Deferred to a later cycle: state-specified link variants, control-link modifiers, in-zoom/unfolding, multiplicity, path labels. - iso-19450-opd-coherence.txt — Maps the three entity-introducing productions to their name-bearing rules (object-declaration → object-name, process-declaration → process-name, state-declaration → state-name). Why these three: per ISO 19450 Clauses 7-9, only these introduce entities into the model; the other 13 sentence kinds reference pre-introduced things. - iso-15288-processes.txt — 30-process catalog across the four process groups (2 + 6 + 8 + 14). Verbatim from ISO/IEC/IEEE 15288:2023 Clause 6 section titles. ISO 15288 lifecycle (src/15288/): Per-process-group AsciiDoc chapters declaring Prism's instance of each of the 30 processes. For each process, the chapter records either (a) the artifact in Prism's architecture that satisfies the process (cross-referencing arc42 sections, ADRs, constraints, or codebase verification artifacts) or (b) "Not applicable to Prism" with the architectural reason for inapplicability. V8 verifies that every process named in the pin file appears as a `===` heading in the corresponding `<group>.adoc` file. OPM Conceptual Model (src/opm/): Six OPDs presenting Prism's static and dynamic conceptual structure: - SD : Top-level system context (chapter 3) - SD1-Prism-Structure : Three containers (chapter 5) - SD2-Principal-Data-Path : Pipeline stages (chapter 6 scenario 1) - SD3-Verification : Replay surface (chapter 6 scenario 2) - SD4-UORassembly-Enforcement : Compile-time bilateral check (scenario 3) - SD5-Distribute-and-Run : Author-to-user handoff (scenario 4) Each OPD comprises an opl.txt (canonical OPL declaration set, V6's input) and an opd.svg (rendering, V7's secondary input). V7 verifies the entity name set declared by opl.txt equals the <text> content set in opd.svg. OPL files for SD, SD1, SD2, SD3 are workspace-authored to match the architecture chapters; OPL for SD4 and SD5 is workspace-authored from chapter 6 scenarios 3 and 4. All six SVGs are generated by tools/opl-to-svg.rb (a developer aid; see below). OPL → SVG generator (tools/opl-to-svg.rb): A one-time / occasional bootstrap helper that produces a deterministic OPM-style SVG from an OPL file. NOT part of the build pipeline — opd.svg is a source artifact, not a build output. The generator classifies each entity as object (rectangle) or process (ellipse) by examining its declaration's essence and its appearances in procedural-link sentences; environmental things render with dashed borders. Layout is a 4-column grid; each entity receives one <text> element whose content matches the OPL declaration verbatim, so V7's coherence check holds by construction on first generation. The author may hand-tune the SVG layout subsequently; V7 catches any edit that drops or alters an entity-name <text>. Sidebar.adoc: Reorganized into three sections matching the three coordinated standards: - Architecture (arc42 + C4): 12 chapters, unchanged - Conceptual Model (OPM ISO 19450): Conceptual-Model - Lifecycle (ISO/IEC/IEEE 15288): four lifecycle pages Validator status (./scripts/validate.sh): V1 — arc42 structural alignment PASS V2 — arc42 build pipeline PASS V3 — Structurizr DSL PASS V4 — CommonMark / GFM PASS (21 files, +6 vs prev) V5 — GitHub-markup rendering PASS (21 files) V6 — OPL syntax PASS (6 OPL files) V7 — OPD/OPL bimodal coherence PASS (6 OPDs) V8 — ISO 15288 process superset PASS (4/4 groups, 30 processes) Build (./scripts/build.sh): Stages 1-5 complete. Stage 5 idempotence holds. Tests (./tests/run-all.sh): test-v6-translator.rb PASS (44 unit tests) test-v7-extractor.rb PASS (11 unit tests) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @afflom afflom committed May 5, 2026