Decision
The approved request and the human or policy decision bound to it.
GRIFF Execution Trust
Content-addressed execution for work you can verify.
Bind the decision, artifact, policy, environment, and output into one reviewable execution record. Verification and evidence are available today. Runtime enforcement remains deployment-specific.
Execution identity
sha256:decision + artifact + policy + environment + output
Inputs identifiedVerifiable
Authority boundVerifiable
Policy versionedVerifiable
Environment fingerprintedVerifiable
Outputs sealedVerifiable
Five-part custody
Know exactly what produced the result.
A conventional activity log says something ran. Execution Trust makes the material inputs and outputs addressable so reviewers can detect drift, substitutions, and missing proof.
Artifact
The exact code, prompt bundle, document, or payload used by the run.
Policy
The exact policy version evaluated before execution.
Environment
Runtime, dependencies, deployment boundary, and tool identity.
Output
The exact produced result and its evidence package.
One contract · every boundary
Evidence travels. Authority stays where you put it.
SaaS Hosted
Managed verification and evidence custody in the GRIFFai control plane.
Hybrid
Keep sensitive data or execution local while synchronizing bounded proof.
Local
Verify receipts on the operator machine without requiring a cloud execution path.
Self-hosted
Run the control plane, policy boundary, and evidence store inside your infrastructure.
Spot execution drift
Compare the expected identity with the observed receipt before accepting an outcome.
Open the evidence dossier
Move from summary to hashes, actors, timestamps, policy versions, and linked artifacts.
Add enforcement deliberately
Attach runtime admission controls only where the deployment has a verified enforcement adapter.