Mission-Bound Authorization

An eight-part proposal that takes Mission-Bound Authorization from architectural argument to concrete protocol and composition surfaces across OAuth and AAuth. Part 1 frames the problem. Part 2 specifies the Intent step. Parts 3-5 specify Mission Governance on the OAuth substrate, the AAuth substrate, and the cross-substrate MAS topology. Part 6 specifies substrate-independent Runtime Enforcement. Part 7 applies the stack to MCP. Part 8 specifies substrate-neutral Conformance.