Trust & controls
This page states Origin's posture plainly for security and procurement review. Origin is decision-support and evidence infrastructure, it runs a deterministic, configuration-bound reference check over an exact agent configuration and produces a tamper-evident attestation a reviewer can re-verify offline. A runtime gate and controlled proxy are proposed pilot architecture, not deployed general enforcement. It is not legal or compliance certification, and it does not guarantee approval.
The prototype runs; it is not production SaaS. "Tamper-evident" means alteration is detectable by replay and digest checks; "review-ready" means a reviewer can check it, and never that a reviewer has signed off. Specifics below are pilot defaults, finalized per engagement in the Data Processing Agreement (DPA).
How to read the status badges
Don't take our word for it
The deterministic oracle is the only judge, so we gate it like one. One command, make gates-all, runs the TypeScript build, every TypeScript and Python test
suite (including the property-based tests on the oracle itself), the evidence-verify
scripts, and a machine honesty check, with real exit codes. The same surface is enforced
in CI on
every push. That run covers the same suites plus the evidence-verify scripts, a secret scan
(gitleaks), and the honesty-lint, with automated dependency updates via Dependabot. The scoreboard below
is a machine-readable snapshot of the local make gates-all run.
make gates-all. (Live scoreboard loads here.)
Every number in this scoreboard is reproducible under this verifier by
make gates-all on the public repo, never "safe" or "correct." (Physical-AI
training metrics shown elsewhere are measured on a private pipeline and labeled as such.)
Want to check a single credential yourself? Paste it into
/verify, it re-verifies offline, in your browser.
What Origin handles
Scoped to what an engagement needs to enforce policy and produce evidence, not repurposed across customers.
Each run of the loop records a bounded set of events:
Retention
Pilot defaults, finalized in the DPA. Placeholders below are marked and confirmed per engagement.
| Data class | Default retention | Notes |
|---|---|---|
| Audit & evidence package | Retained for the engagement Not finalized |
The hash-chained record of what the agent did and why it was allowed. Retained so evidence stays reviewable; archived or deleted per the DPA at engagement end. |
| Raw tool-call payloads | Minimized Not finalized |
Request/response bodies for side effects. Kept only as long as needed to produce and verify the evidence package; can be redacted or shortened per engagement. |
| Contact & lead data | Until deletion is requested Available now |
Information you submit to book a review. Deletion honored on request; the audit log retains the record of the deletion itself. |
Deletion requests are honored at engagement end. The audit log retains the record of the deletion, not the deleted payload.
Security controls
Need-to-know access scoped per engagement. Administrative access is limited and recorded. Secrets are held server-side and are never exposed to agents.
Traffic is encrypted in transit (HTTPS/TLS). Production credentials for connected tools are resolved server-side, never handed to the agent. At-rest encryption for a given deployment is confirmed in the DPA.
Every proposal, verdict, approval, action, block, and exception is written to an append-only, hash-chained record. Tampering breaks the chain and is detectable through replay and digest checks.
Over-scope calls, low-confidence verdicts, and anomalies are held for a named risk owner rather than executed. The escalation path and named contact for material incidents are agreed per engagement.
Responsibility
Origin provides the enforcement and evidence layer. You stay in control of your agents and the systems they touch.
Origin is not a custodian of your agents, your connected tools, or your production systems. It enforces and records; the customer stays responsible for what they connect.
For procurement
For vendor security and procurement review, we assemble a packet per engagement. Each item is status-labelled below, most are provided by request or confirmed for your specific deployment, and the DPA is finalized when the engagement is signed. We do not claim SOC 2, ISO, or any compliance certification.
Data Processing Agreement, including retention terms. Drafted and signed per engagement.
Infrastructure, hosting, and identity providers under confidentiality & security obligations.
Per-class retention confirmed for your deployment.
A written summary of the controls on this page for your review process.
The escalation path and named contact for material incidents.
Each artifact above is provided on request during a private pilot and finalized in the DPA per engagement, none is a finished certification. Origin does not claim SOC 2, ISO, or any compliance certification.
The bottom line
Origin runs across clouds and model providers, and the evidence package is yours to export and hand to a reviewer. It is decision-support and evidence infrastructure, not a compliance certification, a legal defense, or a guarantee of approval. Tamper-evident means alteration is detectable.