FreshContext for AI governance
Leave evidence for why context was trusted, questioned, refreshed or excluded.
Governance usually examines models, permissions and actions. FreshContext adds a judgment point one layer earlier: the context admitted before the model or agent acts.
- candidate
- context + source + time
- decision
- reasoned verdict
- attestation
- signed record where used
- verification
- independent check
The governance gap
The context handoff is often invisible.
A system may log what the model produced or what tool it called without preserving a clear record of why the input context was considered fit to rely on.
Source
Where did the context come from, and what source class was assumed?
Time
When was it published or observed, when was it retrieved, and how quickly does this source decay?
Confidence
How strong is the timestamp or evidence basis, and were any failure states present?
Decision
Why was this context used, questioned, refreshed, watched or excluded?
Attestation
A verdict can be checked without trusting FreshContext.
New ledger-backed verdict records are signed with Ed25519. The public key document and offline verifiers let a third party check the signature independently.
Published key
The active and retired public verification keys are available from the FreshContext well-known key document.
Ledger lookup
/v1/verify can resolve a verdict identifier against the stored record and report the verification method used.
Offline verification
Node and Python verifiers ship with the published package so the signature can be checked without an account, API key or callback to FreshContext.
Boundary
Governance primitive, not governance replacement.
FreshContext provides context-evaluation and attestation primitives. It does not itself replace legal, compliance, model-risk, security, or organizational governance processes.
| FreshContext can provide | FreshContext does not claim |
|---|---|
| Freshness, source, confidence and utility signals | That freshness alone proves factual truth |
| Readable context decisions with reasons | That the caller must enforce the recommendation |
| Signed verdict records where ledger-backed attestation is used | Legal or regulatory compliance certification |
| Independent signature verification | Replacement of model governance, security or organizational controls |
Commercial path
Review the context boundary in one workflow first.
A bounded integration review can identify where context enters, which evidence should travel with it, and whether signed decision records add value to the current governance process.