| CC‑E3.10 | Place BLP below E/E‑LOG and above product tactics. Resolve conflicts by the applicable precedence rules. Invoke the BLP exception procedure when seeking an exception to a preference that would otherwise decide the case (§6 and CC‑E3.11). | Identifies the governing rule and any required exception. |
| CC‑E3.11 | A DRR invoking an exception to an applicable BLP/generality policy identifies that policy and meets its waiver, evidence and conditional debt requirements. Specialization or a fixed procedure alone creates no exception. | Keeps overrides visible without manufacturing them. |
| CC‑E3.12 | Each agentic plan declares an AutonomyProfileId (e.g., L0–L4) with explicit budgets. Add explore_share and the E/E‑LOG EmitterPolicyRef only when the plan uses that live-pool profile under C.24 ATC-4. | Aligns autonomy with assurance. |
| CC‑E3.13 | L1+ executions emit CallGraphs with editioned policy/method ids and budget deltas; L3+ include adaptation status. | Ensures replayability & audit. |
| CC‑E3.14 | Profile changes follow promotion/demotion triggers and publish the profile/policy editions and A.21 decision. E.18 crossing refs and F.9 Bridge refs are present only when their separate predicates obtain. | Keeps autonomy under control. |