Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:25:20 UTC

E.3:11 - SoTA-Echoing — resolve rule conflicts and bind oversight to the action

Practice question and choice. How can an agentic action use applicable governance rules and a budget profile without acquiring an undeclared priority or extra authority? The selected answer combines §4.2’s partial order and unresolved-action hold with §6’s editioned profile, concrete ceilings, checks and permission window. The simpler default uses one fixed conflict-combining rule and a stable table of profiles. That default is cheaper where every relevant rule fits its declared semantics and the table fully specifies the action; the added governance work is justified when obligations conflict or a profile’s conditions change.

Under Cedar’s authorization algorithm, an applicable forbid overrides permits, otherwise an applicable permit allows the request, and the default is denial. Adopt explicit request scope and a declared combination rule where that permission policy is intended. Reject treating it as a universal ordering of obligations: a requirement to publish and a prohibition of publication can remain normatively inconsistent even when access is denied. Cedar does not claim to repair that inconsistency. Its policy-error handling also does not replace A.21’s treatment of required check results. The source defines an authorization language, not FPF rule-change authority.

For oversight, §6 draws on NIST AI RMF 1.0 §6, pp.33–34. Its profiles depend on the use, requirements, risk tolerance and resources; they can distinguish current and target conditions. Adapt that contextual treatment to §6’s budgets, signers, checks and effective window. The source does not prescribe ABL’s L0–L4 labels, numeric defaults or FPF permission semantics. A project’s defaults need a basis appropriate to its use; an ordinal-looking label alone supplies none. This comparison uses the published 1.0 method.

At the same action and input scope, the two cases expose the chosen trade-off:

CaseSimpler defaultSelected move and cost
G1 requires noon publication and G2 forbids it; same source level and class, no priority.A forbid-overrides permission rule denies publication. It is a complete access decision if that combination is already authorized, but leaves the competing obligation to be resolved.§4.2 returns the unresolved obligation pair and holds its action. The extra cost is obtaining an authorized priority or scope amendment; the gain is a visible unresolved duty instead of an invented governance winner.
A plan keeps the label L2 while its requested ceiling changes from twenty to thirty minutes.A stable profile table works if it already resolves the correct edition, checks and window. Looking only at an unchanged label cannot decide the new request.§6 binds the new ceiling and permission before minute twenty-five. Maintaining those conditions costs more than checking a label; an existing table or policy system can carry them without another store. No E.18 or F.9 event is inferred from the budget chang