• What is live · Updated 20 August 2026

The honest status page.

Most companies show you the roadmap and call it the product. This page shows the line between what is live today and what is still being built. It is linked from everywhere on purpose.

01 The unrounded facts

Where things actually stand.

5
verticals mapped: DTC live, restaurants in demo, three more in pack spec.
Apr 2026
running daily in production since.
7
deterministic rules, plus one synthesis pass per cycle.
11
named agents, all on one shared engine.
The engine, described plainly

Today Cintrel runs on a deterministic engine of seven rules plus one language-model synthesis pass per cycle, anchored by a persistent memory layer. The engine tick and the morning brief each run once a day on a fixed schedule: a tighter cadence is a hosting-tier change, not a code change. The eleven named agents below are how that capability is organized in the v1 spec, not eleven autonomous bots. They all run through that one shared engine; the one still in pack spec says so. The chips below are the honest current state.

02 The eleven, each with its real state

No vapor, agent by agent.

Runs on the engine Pack spec · designed, not built
The Watchman
Deploy health and uptime on the surfaces that sell. Hourly.
Runs on the engine
The Auditor
Staleness gates: refuses to brief on data it cannot trust. Every six hours.
Runs on the engine
The Memory
Persistent context across brand, thresholds, and past calls. Ingest, classify, embed, search.
Runs on the engine
The Author
Assembles and sends the daily brief: the decision, the evidence, the draft.
Runs on the engine
The Tracker
Marketing efficiency and attribution drift, with window alignment checks.
Runs on the engine
The Counsel
Compliance and policy watch before anything ships. Twice monthly.
Runs on the engine
The Forecaster
Daily inventory and stockout signals into the engine. Demand forecasting is not built.
Runs on the engine
The Service Mind
Support themes and response patterns from the help desk.
Runs on the engine
The Concierge
VIP risk signals with account context. Dealer briefings are not built.
Runs on the engine
The Critic
Checks the engine's own calls against what happened. Outcome capture is live; automatic grading is not.
Runs on the engine
The Studio
Creative variants and the production pipeline.
Pack spec
03 One engine, vertical packs

The same patterns, wearing each industry's nouns.

A vertical is a noun map, a rulebook pack, and a pilot corpus. The engine, the rank function, the evidence rule and the refusal discipline ship unchanged. That is the point of them.

Built Pack spec · designed, not built
DTC e-commerce
Carrier invoice audit, chargeback and claim windows as statement clocks, ad-platform spend reconciliation, stock cover to the next PO.
Live
Restaurants
Vendor recovery, the statute pack, a franchise agreement read as private law, and people cards behind hard fences.
Demo built
Medical and dental groups
Payer remittances recomputed against the fee schedule, credentialing expiry against the booked schedule, prior-auth windows as deadline clocks.
Pack spec
Trades and field services
Certified-payroll rules per project jurisdiction, equipment certifications against dispatched jobs, retainage aging, change-order windows.
Pack spec
Auto service groups
Warranty claim windows per manufacturer agreement, parts core-charge recovery, technician certifications against booked bays.
Pack spec
04 Why the packs transfer

One pattern, many industries.

three-way match
restaurant vendor bill · parcel carrier bill · payer EOB · warranty claim
private-law pack
franchise agreement · dealer agreement · payer contract
statute pack
wage and scheduling law · certified payroll · licensure boards
expiry vs posted work
food-handler card · technician cert · clinician credentialing
window clocks
statement close · chargeback window · prior-auth expiry · dispute deadline
05 Architecture, honestly

One engine underneath.

Every vertical runs the same codebase, the same schema, and the same caps. What changes is the rule pack and the noun map. A new industry is a configuration problem, not a rewrite, which is why the discipline in the engine matters more than any single rule.

The engine proposes. It does not execute. Every suggestion carries its evidence, confidence is capped in the schema, and a run with no resolvable evidence is refused rather than filled in. The detail on security, data handling, and continuity is on the trust page.

Pack specs above are designed, not built, and say so. If anything on this page ever reads as more certain than it should, that is a bug. Tell us and we will fix the wording.

06 Private beta

Honest enough to bet on.

If radical honesty about what is and is not built is the kind of partner you want, let us show you the rest on your own stack.

Book a demo How it works →