Technology

Engineered for trust

The honest page. No magic claims — the actual architecture, and why each piece exists.

Event-sourced, single source of truth

Every action in Syzero is an event in an append-only, ordered log. The world can be replayed from any point; nothing is hidden, nothing is lost. The 3D client is a projection of this log — if it isn't in the log, it doesn't appear in the world.

Hard tenant isolation

Every business has its own database and data directory. There is exactly one code path to reach a tenant's store, and stores never merge. Cross-business work travels as tickets — memos, never shared filing cabinets. Shared services (finance, legal, audit) are themselves isolated child tenants of HQ.

Human-gated by construction

Money-out is structurally unrepresentable without an approved operator decision — enforced in the database schema, not by policy text. External actions require an approval with a full payload preview, and first-of-its-kind actions must pass a rehearsal in a sandbox before the real thing is even proposed.

Deterministic where it matters

Routing, deduplication, claims, gates, and guardrails never touch a language model — they are deterministic and explainable. Cognition runs on a tiered model policy with per-business daily budgets; when budgets run out, the world goes simple before it goes mute.

Agents that compound

Every agent recalls before it works, cites what it uses, and distills a reusable skill from every accepted deliverable. Skills are counted by reuse; weekly consolidation merges what overlaps and prunes what never earned reuse. Performance records weight future routing — a robot's reputation is a measurable thing.

Anti-looping, by law

A goal is claimed atomically and can never be worked twice. One review, at most one rework round, and a watchdog that refuses any task that has already failed twice — citing the prior outcome and escalating to the operator instead of running another lap.

Verified continuously

170 automated tests plus a live verification harness that boots the runtime, requests a business, approves it at the inbox, watches the full construction event trail, and exercises connectors, knowledge recall, and the kill switch — on every change.

The digital twin

The Unity client renders the campus from runtime state and events only. Buildings, robots, walkway crossings, construction, boards, and the finance hall all bind to real data. The renderer visualizes reality — it never invents it.