Trust
Most AI platforms ask you to trust a policy document. NOW OS is built so the trust properties are structural — enforced by the architecture, checked by machines, and re-verified while you watch.
The six structural guarantees
Every consequential thing an agent discovers or recommends is filed as a proposal to your Strategic Advisory Board. A named human approves, denies, or defers — NOW OS cannot promote its own output into your operation. This isn't a setting; there is no other code path.
Governance decisions and execution events land in a hash-chained audit log. When anyone views it, the chain is recomputed live — a broken link is visible immediately. The "verified" badge is earned on each page load, never cached.
Work touching FERPA, HIPAA, PCI, export-control, and similar regimes carries control floors the scoring cannot cross — it can never be silently over-automated, no matter how favorable the score. Non-compliant work is refused at ingest, fail-closed.
Every fact entering the live knowledge graph is validated against schema and contract before it is written, queued for a named reviewer, and re-validated on promotion. There is no side door, and destructive operations carry pre-state snapshots.
Role walls, ownership checks, and persona boundaries are covered by regression suites and adversarial review passes — the product's own release gates fail if a wall regresses. What a requestor can see is decided server-side, fail-closed.
When an answer draws on reference or shared knowledge, the borrowed source is labeled in the response and in the sealed audit payload — you always know which facts are yours and which are contextual.
At production
A production tenant runs with enterprise single sign-on (Microsoft Entra ID), secrets held in Azure Key Vault (fail-closed — no baked credentials), tenant isolation at the runtime, and live-system connectors that ingest your data under your governance. Evaluation instances are the same runtime with the production machinery dormant — cutover swaps identity, secrets, and data sources; the platform doesn’t change.
Sealed intellectual property: the per-dimension scoring weights, readiness formulas, and policy-floor values are never disclosed — the platform always explains what each dimension means and why an action landed where it did. Aspects of NOW OS are the subject of pending U.S. provisional patent applications.
Common questions
No. The conversational surfaces exist, but the core is a computed model of your organization's work — decomposed to atomic actions, scored against a published rule, and operated with human gates. Retrieval is one layer of it; the work model is the product.
It scores every action and recommends a mode: some work automates, some gets augmented or assisted, and some stays Human-Only by design — accountable approvals can't be automated away, and restricted work carries enforced floors. The output is a governed division of labor, not a headcount plan.
Nothing, to evaluate — the demo instance runs on simulated data. A pilot needs your policy corpus and organizational data for one process; the work model is discovered from your real documents, not hand-authored from templates.
Leading frontier models (Anthropic's Claude family) for reasoning, orchestrated over your knowledge graph with tool use, plus a library of 49+ deterministic quantitative capabilities. Model reasoning is grounded in retrieved facts with provenance, and audit-grade outputs are bit-reproducible.
Not until they're earned. Everything runs today on a high-fidelity reference dataset; at cutover your live data recalibrates the models, and stronger claims are earned through non-circular backtests under your board's sign-off. We say "built" and "validated" precisely, and never swap one for the other.
You do. NOW OS recommends; your Strategic Advisory Board approves, denies, or defers; the ledger records. Every decision is replayable.
Our commitments
We never build the map from a person’s keystrokes, camera, microphone or mood. We never use it to rate or blame an individual. We never let a machine grant itself more autonomy than a named person approved. Every figure the platform shows traces back to its source.
These are not policies we ask you to trust. They are how the system is built.
Map your work
What you type about your process is not kept unless you tick the box asking us to keep a copy of your map. Without the tick, your description is used to build the map and is gone when each request finishes — the page doesn’t even send it with your email.
Files you attach are never kept. They are read once to understand your process, and only a short summary of them is used after that. That summary is shown back to you.
When you leave your email, we keep it with the industry, role and laws or policies you told us about (if you did), and the size of your map. If you ask us to talk, we keep what you write to us too.
If mapping is paused on our side, the page offers to send you your map when it’s back. We keep your email, and your description and answers only if you tick the box, so we can build your map and send it to you. Files you attach are still never kept.
We count how the page is used, anonymously: which steps people reach (for example, “a map was built” or “the example was opened”). Those counts carry no name, no address, no identifier and nothing you typed. The only thing the page remembers in your own browser is whether you’ve seen its introduction.
A briefing covers the architecture, the governance model, and the audit trail live on the running system.