Skip to content

build-set describes a set as one system from its system record (DR-54) - #25

Closed
afflom wants to merge 1 commit into
mainfrom
claude/system-diagram
Closed

afflom wants to merge 1 commit into
mainfrom
claude/system-diagram

Conversation

@afflom

@afflom afflom commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Until now a prompt set described only its decisions, each with its own OPM view. This PR adds an optional system record to a set. When it is present, build-set describes the whole system and puts it on top of the decisions.

  • Architecture (ISO/IEC/IEEE 42010): the beneficiary as a stakeholder, the attribute the system changes as a concern, a system viewpoint and view, and components for the system, the beneficiary, its inputs and its results.
  • Design (ISO 19450 OPM):
    • The system diagram: the main process, the beneficiary as agent and its attribute's two states, the instruments, the inputs it consumes and the results it makes.
    • Its zoom: the main process into one process per part, and each part into the Decide process of every app that part holds.
  • Compliance: one obligation for each standard the system names.
  • Refusals:
    • an app that is in no part, or in two parts;
    • a part that holds no app and doesn't say what it owes;
    • a missing role;
    • an unknown shared component.
  • Test: DR-54 (builder/test.mjs DR-54, 46 assertions). DR-17 and DR-22 are unchanged, and cargo test passes 76 tests.

afflom/me uses this to model the Prism as a digital twin of its person that is also their agent. It vendors this builder and verifies its 69 modules in the locked SDK.


Generated by Claude Code

A set described only its decisions, each with its own OPM view. An optional
`system` record now puts the system on top of the architecture description
(ISO/IEC/IEEE 42010): its beneficiary as a stakeholder, the attribute it changes
as a concern, a system viewpoint and view, and components for the system, the
beneficiary, its inputs and results. Design gets the OPM system diagram (ISO
19450): the main process, the beneficiary as agent and its attribute's two
states, instruments, inputs consumed and results made, and its zoom: the main
process into one process per part, each part into the Decide process of every
app it holds. Every app is a part's exactly once; a part no app realizes states
what it owes. Each standard the system names gets a compliance obligation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3QU8Mz6i7JNPDbNRBd

afflom commented Nov 15, 2026

Copy link
Copy Markdown
Owner Author

I'm closing this PR. audit-prism (#22) correctly refuses it, because it adds 185 lines of non-Prism JavaScript, and the ratchet only allows that count to shrink. The system diagram now lives where the rule says it should: afflom/me authors it in LexLean as an app/src/PrismSystem.lex.tex module that prismpm check accepts. The builder stays unchanged.


Generated by Claude Code

@afflom afflom closed this Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants