GraphOS compiles a domain model from your intent and your data, then answers with a decision Thread: evidence on every edge, contracts that say what is missing, and a machine-checkable proof a third party can verify without trusting you — or us.
Demo mode: use the API key from your operator, or a session account if the deployment enables sessions. No data leaves this machine in demo mode.
By continuing you accept that this is a pilot build: no SLA, no legal advice, and every decision should be reviewed by a qualified human.
Ingest evidence, compile the model, solve the decision. Everything in between is inspectable.
Every edge carries a belief id, a source tier and a locator. Unsourced “facts” are downgraded to hypotheses instead of being asserted.
Intent plus sample records become an Ontology, rules, evidence contracts and a validation suite — versioned, diffable and approved by a human.
Each Thread ships with a DPF document. An independent, stdlib-only checker verifies pins, edge identity, evidence and findings.
python -m graphos.proof dpf.json — no GraphOS import, no network.The evidence pack is the artifact a reviewer reads: status, coverage, findings, evidence, missing evidence, unknowns, and the proof. If a rule cannot run, it is listed as unknown — not hidden.
Start with one domain and one reviewer. Success is measured by an external reviewer accepting the evidence pack, not by a demo.
4 weeks, one domain, one evidence pack reviewed, weekly working session.
Up to 5 domains, API + Studio, proof export, email support.
Self-hosted, SSO, audit retention, custom sources and review workflows.