Source + force
Citation, revision, effective dates, jurisdiction, and binding/contractual/normative/committed force.
Source ownerBlueprint · careervector.blueprint-graph/v5
Graph explorer
Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.
Nested layer 2 · governance · control · evidence · operations
Operating obligation record fields
The record preserves the whole justification and proof chain without confusing an obligation ID with one of the nine semantic hub IDs.
- Source + force to Applicability + scope: assess
- Applicability + scope to Idea interpretation: interpret
- Idea interpretation to Required Behaviour: require
- Required Behaviour to Implementation / Infra: realize
- Implementation / Infra to Suite / Test / evidence: verify
- Suite / Test / evidence to Anomaly · Event · Journal: detect or prove
- Anomaly · Event · Journal to Owner + review: account
- Owner + review to Source + force: reassess
Applicability + scope
Decision, authority, products, modules, actors, data classes, interfaces, and rationale.
Decision authorityIdea interpretation
Approved product/system meaning linked into the Idea hub.
Product ownerRequired Behaviour
Atomic statement, acceptance criteria, prohibited outcomes, and state.
Product and QAImplementation / Infra
Enforceable control, failure behaviour, recovery, and named command path.
Owning productSuite / Test / evidence
Verification links and runtime evidence prove the current claim.
QA and owning productAnomaly · Event · Journal
Violation, incident, explanation, compensation, and recovery remain traceable.
Ops and productOwner + review
Approver, escalation, cadence, and source or product change close the loop.
Accountable owner01 · obligation · target Source + force Citation, revision, effective dates, jurisdiction, and binding/contractual/normative/committed force.
Source owner02 · boundary · target Applicability + scope Decision, authority, products, modules, actors, data classes, interfaces, and rationale.
Decision authority03 · perspective · target Idea interpretation Approved product/system meaning linked into the Idea hub.
Product owner04 · process · target Required Behaviour Atomic statement, acceptance criteria, prohibited outcomes, and state.
Product and QA05 · service · target Implementation / Infra Enforceable control, failure behaviour, recovery, and named command path.
Owning product06 · store · target Suite / Test / evidence Verification links and runtime evidence prove the current claim.
QA and owning product07 · process · target Anomaly · Event · Journal Violation, incident, explanation, compensation, and recovery remain traceable.
Ops and product08 · actor · target Owner + review Approver, escalation, cadence, and source or product change close the loop.
Accountable owner
Flows
- Source + force → Applicability + scope assess
- Applicability + scope → Idea interpretation interpret
- Idea interpretation → Required Behaviour require
- Required Behaviour → Implementation / Infra realize
- Implementation / Infra → Suite / Test / evidence verify
- Suite / Test / evidence → Anomaly · Event · Journal detect or prove
- Anomaly · Event · Journal → Owner + review account
- Owner + review → Source + force reassess
Canonical architecture note
Open note ↗Operating Obligation Record
Machine authority
architecture/operating-obligations.ts defines the Zod and JSON-compatible TypeScript contract.
This note explains its semantics; it does not duplicate the field schema.
Record sections
| Section | Required meaning |
|---|---|
| Source | Verifiable title and citation; jurisdiction/revision/effective dates where relevant |
| Force | Binding, contractual, normative, or explicitly committed |
| Applicability | applicable, not-applicable, or open, plus products, modules, actors, data, interfaces, rationale, authority, and decision |
| Interpretation | Approved Idea references and the product/system meaning of the source |
| Requirements | Atomic statements, state, Behaviour references, acceptance criteria, and prohibited outcomes |
| Controls | Implementation/Infra references, named commands, failure behaviour, and recovery |
| Assurance | Suites, Tests, runtime evidence, Anomalies, Events, Journals, and verification method |
| Accountability | Owner, approver, escalation, and review cadence |
State rules
as-builtmeans current implementation and verification evidence exist.targetmeans an approved decision and acceptance criteria exist.mixedmust be decomposed into separately state-labelled requirements or controls.opennames the unresolved decision and the authority that must resolve it.applicableandnot-applicablerequire a durable decision reference;opendoes not masquerade as either conclusion.
Nine-hub mapping
References use the existing prefixes only: idea:, implementation:, journal:, behaviour:,
suite:, test:, anomaly:, infra:, and event:. obligation: identifies the boundary
record itself; it is deliberately not accepted as a semantic-hub reference.
Current seed
The register contains one honest seed: CareerVector's explicit zero-user-cost commitment. It is target-state because the complete Behaviour, control, and assurance chain is not yet linked. The seed proves the schema without pretending that a legal review or implementation gate already exists.
Change discipline
Changing a source, applicability conclusion, requirement, or prohibited outcome is an architectural decision. Updating evidence links after implementation is traceability maintenance. Both are reviewed, but only the former changes product meaning.