An architecture description must record the rules, guidance and standards that limit or shape activities, including the conditions under which a constraint changes. It must show how rules apply to activities and how policy, doctrine, security marking and release criteria are represented as guidance or stronger rule types. The data should support transaction definitions, access rules, step sequencing and option analysis in PPBE, JCIDS, DAS, systems engineering, operations planning and capability portfolio management.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.