Data Boundaries and Ownership¶

This page documents ownership boundaries for domain data and recommended integration behavior.

Ownership Model¶

flowchart TD
    Core[core shared concerns]
    Portfolio[portfolio_mgmt owns program/project context]
    SysDef[sysdef_mgmt owns system-element hierarchy]
    SysArch[sysarch_mgmt owns architecture structures]
    Req[requirements_mgmt owns requirements and trace links]
    VnV[verification_validation_mgmt owns verification evidence]
    Safety[safety_assurance owns hazards and assurance arguments]
    Baseline[baseline_mgmt owns controlled release/baseline state]

    Portfolio --> Req
    SysDef --> Req
    Req --> VnV
    Req --> Safety
    VnV --> Baseline
    Safety --> Baseline
    Core --> Portfolio
    Core --> SysDef
    Core --> SysArch
    Core --> Req
    Core --> VnV
    Core --> Safety
    Core --> Baseline

Boundary Rules¶

• Each domain owns its write models and workflow transitions.
• Cross-domain reads are acceptable when they support traceability views.
• Cross-domain writes should be explicit and reviewable.
• Shared policy logic belongs in core.