The authorization layer for automated systems
The signed record of who accepted the risk, what the system may do, and until when.
The agent removed
40,000 posts.
Who said it could?
This sample demonstrates where an evaluation attachment would appear in the record. No evaluation was performed for this illustration. It contains no evaluator, findings, test results, or assurance opinion and is not part of the signed public demonstration record.
Make the boundaries of automation explicit. See what has been authorized, which conditions apply, and where permission ends.
Keep institutional decisions connected to their sources, interpretations, and owners. Produce the record when someone asks.
Find your systems and their authorization records. See which records need attention and which are approaching expiry.
Explore with us ↗Bring scope, conditions, exclusions, and the named risk acceptor together in a signed, versioned record.
Inspect a signed demonstration record ↗Inspect the source and attributed interpretation behind a condition, alongside its policy reference and evidence requirements.
Explore with us ↗Produce an audit memo and Cedar policy set from the same record. Check the signed record independently.
Inspect a signed demonstration record ↗Optional runtime enforcement. Check proposed actions against the recorded authorization before they proceed. Production executor integration is required.
Co-founder & CEO
Twenty years across seven federal agencies, where no system goes live until a named official accepts its risk in writing. licet brings that discipline to every automated system. American Service Fellow in the Mid-Career MPA program at Harvard Kennedy School. MA in Strategic Studies, Air War College.
David’s story at Harvard Kennedy School ↗Co-founder
Swiss lawyer and former compliance lead for a Swiss cantonal government. MC/MPA candidate at Harvard Kennedy School, selected as Switzerland’s representative on a Harvard sovereign AI project.
Preserve the institution’s decision in a form that product, policy, legal, and independent reviewers can examine.
Read the signed demonstration record ↗An authorization record documents institutional permission.
Keep the risk acceptance and concurrences attached to the version that was approved.
Preserve the sources, interpretations, limits, and evidence requirements behind the decision.
Demonstration signatures establish no real-world identity or approval. Operational assurance is not assessed; legal compliance is not determined. This is a fixed snapshot, not a current authorization check.