Repository navigation
Lifecycle Technical Management Processes
This chapter specifies Prism’s instance of the Technical Management processes from ISO/IEC/IEEE 15288:2023 Clause 6.3. The eight processes in this group concern how a project plans, controls, and assures the production of a system: project planning and assessment, decisions, risks, configuration, information, measurement, and quality assurance.
Note
Normative source: ISO/IEC/IEEE 15288:2023, Systems and software engineering — System life cycle processes, Third edition (2023-05). Published jointly by ISO, IEC, and IEEE; supersedes ISO/IEC/IEEE 15288:2015. ICS 35.080. Free preview at iso.org/obp. This chapter covers Clause 6.3 of the standard.
The processes in this group fall in two categories with respect to Prism: those whose subject is the producing organization’s project management (not specified by the wiki) and those whose subject is the system’s own architectural records (specified by the wiki, and named here with their architectural artifact). This chapter records both kinds explicitly.
Not applicable to Prism.
The 15288 Project planning process produces and coordinates effective and workable plans. The wiki specifies what Prism is, not how the Foundation plans the project that produces Prism. Schedules, resource allocations, milestone definitions, and effort estimates are organizational concerns external to the system’s specification: the wiki is a desired-state document, not a roadmap or schedule.
Not applicable to Prism.
The 15288 Project assessment and control process determines the status of the project relative to its plans and directs project execution. As with Project planning, this is an organizational concern external to the wiki’s scope.
Prism’s instance: Architecture Decision Records in section 9 (chapter 9, Architecture Decisions).
The 15288 Decision management process provides a structured, analytical framework for objectively identifying, characterizing, and evaluating a set of alternatives for a decision. Prism’s load-bearing architectural decisions are recorded as numbered ADRs in section 9. Each ADR carries a context statement, the alternatives considered, the decision taken, and the consequences. The decisions are normative: an implementation that does not honor a decision in the manner the corresponding ADR specifies is not conformant.
ADRs are append-only and amendable. When a decision is revisited, the revisited ADR records the supersession and points to the new ADR; the old ADR remains in the wiki as a historical record. This append-only discipline mirrors the codebase’s git history; it preserves the audit trail of decisions in the same artifact that documents the current state.
Prism’s instance: Technical Risks register in section 11 (Technical Risks).
The 15288 Risk management process identifies, analyzes, treats, and monitors risks continually. Prism’s identified technical risks are recorded as numbered TR entries in section 11. Each TR entry carries the risk’s description, the architectural impact, and the mitigation or acceptance posture the architecture takes.
Risk management in Prism is an architectural discipline rather than an operational one: risks are addressed by architectural choices (constraints, ADRs) rather than by ongoing project-level surveillance. TR-04 (distribution channel selection) and TR-05 (hasher selection mismatch), for example, are accepted-and-mitigated by architectural choice (ADR-004 declares the channel out of scope; constraint TC-05 requires the hasher identifier to be conveyed out-of-band). TR-01 (generic_const_exprs incompleteness) is mitigated by the shape proc-macros emitting only const-expression patterns the toolchain handles correctly, with the conformance suite exercising those emissions on every commit. The codebase’s CI absorbs the ongoing-surveillance components of risk management.
Prism’s instance: the three crates' versioning, the wiki’s pinned authorities, and the wiki’s validator scripts.
The 15288 Configuration management process manages and controls system elements and configurations over the life cycle. Prism’s configuration items are:
-
The three crates (
uor-foundation,prism,prism-verify), versioned via Cargo’s semver discipline and published tocrates.io. -
The wiki’s pinned external authorities: the arc42-generator submodule pin, the structurizr.war SHA-256 checksum, the cmark-gfm tag literal, the Ruby gem versions in
Gemfile.lock, and the three transcribed-standard pin files (tools/iso-19450-opl.ebnf,tools/iso-19450-opd-coherence.txt,tools/iso-15288-processes.txt). -
The application author’s selections of
HostTypes,HostBounds, theAxisTuple(the substitution axes; section 2 — the third position originallyHasherper ADR-007, generalized per ADR-030 to a tuple of axis trait selections bound by+ Hasherper ADR-036 with the prism-crypto-declaredHashAxisper ADR-031 as the canonical first member), and optionally theResolverTuple(the fourth model-declaration substrate parameter per ADR-036 defaulting toNullResolverTuple, carrying application-provided per-value content for resolver-bound ψ-Term variants per ADR-035 when the model’s verb bodies emit any). These are application-level configuration, not Prism-level.
Updating any pin is a deliberate maintainer act performed by direct push, with the regenerated wiki output co-committed so the wiki’s rebuild from sources remains deterministic. The wiki’s validator scripts (under scripts/ in the wiki repository) enforce the configuration: they confirm the architecture chapters' structural alignment with arc42, the conceptual model’s syntactic conformance to OPM, and the lifecycle chapters' coverage of the 15288 process catalog.
Prism’s instance: the wiki’s normative specification and the codebase’s in-source documentation.
The 15288 Information management process generates, obtains, confirms, transforms, retains, retrieves, disseminates, and disposes of information to designated stakeholders. Prism’s information artifacts are the wiki (this site, including all twelve arc42 chapters, the conceptual model, and the four lifecycle chapters) and the codebases' rustdoc plus Lean docstrings. The wiki is the normative information artifact: where wiki prose and codebase comments diverge, the wiki prevails by ADR-001.
Information dissemination is via GitHub’s rendering of the wiki and the published crate documentation on docs.rs. No information passes through an author-operated channel at runtime or verification time; the wiki and the published documentation are the only information artifacts the application author or user needs to consult, and both are reachable through GitHub’s and crates.io's public interfaces.
Prism’s instance: the conformance suite, the doctest harness, and the Lean theorem set.
The 15288 Measurement process collects, analyzes, and reports objective data and information to support effective management and demonstrate the quality of the products, services, and processes. Prism’s measurement artifacts are:
-
cargo testagainst the workspace’s doctest and integration suites. Each architectural claim made by rustdoc has an executable doctest that confirms the claim. -
lake buildagainst the UOR Lean 4 library. Each mathematical claim made by the wiki has a corresponding theorem; the Lean build’s success is the measurement that the claims hold. -
cargo run --bin uor-conformanceagainst the conformance suite. Each end-to-end behavioral claim (pipeline replay equivalence, certificate idempotence, hasher contract conformance) is exercised by a conformance test.
The three measurement artifacts are run by the codebase’s CI on every commit. Where the wiki references a specific doctest, theorem, or conformance entry as evidence for a claim, the reference uses the artifact’s source-side identifier (constraint CV-02); a reviewer reads the wiki and the codebase together to confirm the artifact exists and says what the wiki claims it says.
Prism’s instance: the wiki’s validator scripts plus the codebase’s CI gates.
The 15288 Quality assurance process provides confidence that quality requirements will be fulfilled. Prism’s quality assurance is the union of:
-
The wiki’s validator scripts (under
scripts/in the wiki repository), which enforce: the architecture chapters' structural alignment with arc42; the architecture chapters' renderability through arc42’s build pipeline; the C4 diagrams' Structurizr DSL validity; the wiki pages' CommonMark/GFM well-formedness; the rendering through GitHub-markup; the conceptual model’s OPL syntax against the pinned ISO 19450 EBNF; the conceptual model’s OPD/OPL bimodal coherence; and this lifecycle chapter set’s structural coverage of the ISO 15288 process catalog. -
The codebase’s CI gates:
cargo build,cargo test,cargo clippy,cargo fmt,lake build, the conformance suite, the Lean axioms-list check, the no-sorrycheck.
Quality assurance is mechanical: the validator scripts and CI gates either pass or fail, with no human-judgment middle ground. A wiki state or codebase state that does not pass the gates is not a conformant state; the repair is to fix the underlying violation and re-run.
Generated from sources at UOR-Framework.wiki. Do not edit pages directly via the GitHub web UI — edits are overwritten by the next build. See README for the authoring workflow.