RuleSpoolTwo requests, one remembered approval
Choose “A saved approval meets a deny” in the explorer. The agent layer asks for shell actions generally and denies the git push * pattern later. The saved layer contains an allow for all shell resources. The two request strings are git push origin main and git status --short.
For push, the configured agent-plus-session result is deny. The evaluator stops before consulting saved approvals for the request. The saved tape is visibly skipped. For status, configured rules ask; the saved approval is considered and the supplied pre-hook result becomes allow.
Do not flatten the layers into one list
Putting every remembered approval at the bottom of one universal last-match array would make that broad allow appear to override push. It would be the wrong model for this source snapshot. RuleSpool first evaluates the configured rules for every requested resource and checks whether any of those final results deny.
The word “final” matters here. An earlier agent deny can itself lose to a later configured session rule. The checkpoint examines the winner after those configured layers, not the presence of any deny ticket anywhere.
Unknown is different from empty
If you imported only an agent export, the site has not seen the session or durable approval state. Those layers initially read unknown. A supplied empty array means you have explicitly modeled no rules in that layer. Neither representation proves the state of a running server; they make your input assumptions visible.
Use Snapshot coverage to mark the draft layer supplied, then add the actual patterns you intend to analyze. Clearing the supplied checkbox removes its draft rules and restores the unknown label. Review changes records the coverage change even when the visible effect stays the same.
What happens after the preview
The native flow can invoke permission-evaluation hooks after the configured and saved stages. Managed policies and runtime context are outside this browser computation. A remembered permit also does not prove that a login, file write or web request succeeded.
See official approvals and the pinned configured/saved flow.