The Engine
What runs behind your team’s rules, every hour of every day.

The rules are the output. This is the work that produces them and keeps them current: the calls, the extraction, the approvals, and the eval that scores every draft. Live sample workspace for a pursuit team; every name, deal, and number is fictitious.

live
Interviews
1 running
Iris
on a call · 2:41
Extraction
drafting 3 rules
Approvals
2 waiting
Connector
serving
Eval
scoring
Expertsweekly calls Extractionrules · attribution Debriefswon · lost Skillsv14 · 27 rules Your AICopilot · connector calibration: what the team actually sent flows back and re-scores the rules
118
drafts served, 90 days
27
rules live · v14
96% fresh
+65
Metis delta, running eval
generic 31 → 87
41
expert calls captured this quarter
1 live now
Northwind pursuit team · Finalist Q&A skill file · v14
--:--:--
0
drafts served through the connector, 90 days
+1 every few seconds right now
27
rules live across 6 skill files
+4 this quarter
96%
library freshness
2 rules due in 9 days
+0
Metis delta, running eval score
generic vs Metis-powered, same prompt

Activity streaming

Metis delta eval on the last draft

+0points, generic vs Metis-powered
CFO pricing email · "Draft the reply."
Generic modelMetis-powered

Scored by an automated eval against the skill file: which rules applied, which flags raised, which numbers re-run, whether every claim carries an owner. The same eval runs on every draft, so the delta is tracked over time, not demonstrated once.

Ingesting interview, K. Rosner

Pricing pushback replies · 27 min · human-led

Iris async capture

D. Okafor · calling in after the finalist

Approval queue 1 pending

waiting for D. Okafor to approve
Finalist Q&A · proposed rule 14+ When the buyer’s CFO sits on the committee, lead every pricing answer with 3-year total cost, never the year-1 rate. Source: D. Okafor, on Northwind.
Why a file alone can't do this

A file is a snapshot. The engine is the weekly calls that fill it, the approvals that keep it honest, and the calibration that checks it against what your team actually sent. The work is continuous, and it is what keeps the file from becoming a document nobody trusts.

Why your experts will actually use it

They do not write things down. They react, and they talk. Iris takes the 30-minute call, asks the follow-up, drafts the rule, and nothing goes live until the person whose name is on it taps approve.

Why the delta is measured, not claimed

Every draft your AI produces is scored against the skill file, generic and Metis-powered side by side. The number at the top is that score, tracked over time. It is the one number, agreed up front, made visible.