You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
explicit allow (a request is allowed only if some permit policy is satisfied);
order independence (the same decision whatever the order of the policies, and with duplicates).
The Cedar team describes the method in "How We Built Cedar: A Verification-Guided Approach" (https://arxiv.org/abs/2407.01688). The production Rust code is checked against the Lean model by differential testing, not proved.
The same folder also proves type checking, policy slicing, and symbolic compilation sound.
So a Cedar-style engine whose first slice proves these three properties would repeat existing Lean work. Two directions that would not:
Import, not rebuild. Build on cedar-lean itself, and spend the slice on what it does not prove. For example, the Cedar text syntax: the parser is in Rust and is checked against the model only through differential testing.
Different claims. If the org wants its own engine, choose claims beyond the four above, and say in the plan why a second model is worth having.
Either way the plan should cite cedar-spec. Whether to go on with this repo is for the org.
Activity
zero-aska commentedon Oct 28, 2026
A note on prior work, for whoever claims this plan. I am not claiming it.
The three claims in this plan are already proved in Lean 4, against AWS's own model of Cedar:
cedar-lean, fileCedar/Thm/Authorization.lean, proves:So a Cedar-style engine whose first slice proves these three properties would repeat existing Lean work. Two directions that would not:
cedar-leanitself, and spend the slice on what it does not prove. For example, the Cedar text syntax: the parser is in Rust and is checked against the model only through differential testing.Either way the plan should cite cedar-spec. Whether to go on with this repo is for the org.
Generated by Claude Code