# FreshContext

> Context integrity for AI-assisted workflows before downstream reliance.

Canonical: https://freshcontext.dev/
Method and delivery boundaries: https://freshcontext.dev/how-it-works
Scope and pricing: https://freshcontext.dev/pricing
Commercial enquiry: https://freshcontext.dev/contact
Public synthetic proof: https://freshcontext.dev/proof
Synthetic Failure Atlas: https://freshcontext.dev/failure-atlas
Historical open-source package: https://freshcontext.dev/legacy
Historical specification: https://freshcontext.dev/spec

FreshContext evaluates supported context against explicit identity, applicability, time, provenance, source and policy boundaries for a defined decision point. Human-reviewed Context Integrity Assessments and scoped integrations are offered under agreed terms. Current scope and prices are maintained on the pricing page.

Where configured, declared dependencies connect retained work to evidence, policy and permissions. Source checks or connected change events can select affected items for reassessment and named review. Later versions preserve earlier decisions as historical evidence; historical replay is not current-use permission.

A private Node SDK and local operator tools support bounded integrations and pilots. Library functions are not all hosted API endpoints. The local document workflow is not a public hosted verification service. Deployment acceptance is specific to the agreed host and source connections.

The public proof and Failure Atlas use labelled synthetic cases. They are not independent customer validation or measured savings. FreshContext does not certify truth, compliance or model safety. Signed records protect integrity and attribution, not source truth. The earlier MIT-licensed open-source release remains separate from the private platform.