# Evolution 85 — Vertical Workforce Catalog

**FIRME AI CORPORATION · CAIN-42 · Evolution 85** — branch `evolution-85`, baseline Evolution 84 (`2c419a042`). Development result. Not deployed. Not released. Built by the three-person team.

## Why these three first

Chosen from the operator playbook's first streams, where an engine, a fixed-price offer and a delivery tool already
exist: fabrication audit (stream 1), MCP and agent security review (stream 2), signed evidence pack (stream 4). Each
is low-risk (read-only analysis of material the customer supplies), needs no regulated data, and produces a result a
buyer can check.

## Built and measured

| Vertical | Domain | Tool | Items | TP / FP / FN / TN | Precision | Recall | Delivery without → with approval | Receipts |
|---|---|---|---|---|---|---|---|---|
| `evidence_pack` | compliance and auditing | `scripts/evolution84/verify_action_receipt.py` | 12 | 6 / 0 / 0 / 6 | 1.0 | 1.0 | HOLD_FOR_APPROVAL → COMPLETED | 2 |
| `fabrication_audit` | AI and software engineering | `cainwitness.engine.scan_source` | 20 | 7 / 0 / 3 / 10 | 1.0 | 0.7 | HOLD_FOR_APPROVAL → COMPLETED | 2 |
| `mcp_tool_review` | cybersecurity | `mcp-security-scanner engine.scan_tool_definition` | 20 | 8 / 1 / 2 / 9 | 0.8889 | 0.8 | HOLD_FOR_APPROVAL → COMPLETED | 2 |

Every prototype: one mission template (intake → specialist analysis → verifier re-execution in a separate process →
governed record → delivery held for a human → approved delivery → evidence export), a three-identity team, an
authorization policy with a human approval gate on delivery, E84 receipts that verify offline, and a measurable
outcome.

The engines are heuristic pattern checkers. The labelled items were written for this evolution, half of them chosen
to be hard; the misses are in the per-item rows. These figures are not real-world precision, and the verifier
re-runs the same engine, so it catches a tampered result, not an engine that is wrong. No professional or regulated
competence is claimed.

| Vertical | Knowledge source | Specialist roles | Data class | Human approval | Failure modes seen | Customer outcome |
|---|---|---|---|---|---|---|
| `fabrication_audit` | source files supplied by the customer | commander, audit-specialist, audit-verifier | customer-confidential, read-only | required to deliver the report | deterministic fakes with no random call are missed | every supplied module graded, with the modules that return invented results listed |
| `mcp_tool_review` | the tools/list response of the server under review | commander, mcp-specialist, mcp-verifier | customer-confidential, read-only | required to deliver the report | paraphrased instructions are missed; a quoted attack string is flagged | every tool definition a server exposes reviewed, with the ones unsafe to connect listed |
| `evidence_pack` | receipts and pinned keys | commander, evidence-specialist, evidence-verifier | customer-confidential, read-only | required to deliver the report | none on this set | a set of agent action receipts re-verified offline, with every altered receipt identified |

## Planned, not built (requirements, not claims)

| Domain | Data needed before a prototype | Status |
|---|---|---|
| Scientific research | literature corpus, experiment logs | DESIGN ONLY |
| Mathematics and quantitative reasoning | proof and solver tools | DESIGN ONLY |
| Finance and accounting operations | ledgers; regulated | DESIGN ONLY |
| Legal research and document operations | case and statute data; regulated | DESIGN ONLY |
| Healthcare administration and clinical support | clinical data; regulated, human oversight mandatory | DESIGN ONLY |
| Manufacturing and industrial operations | plant data | DESIGN ONLY |
| Robotics and physical AI | hardware; simulated only today | DESIGN ONLY |
| Logistics and supply chains | shipment data | DESIGN ONLY |
| Agriculture | sensor and yield data | DESIGN ONLY |
| Energy and utilities | grid data; safety-critical | DESIGN ONLY |
| Education | curricula | DESIGN ONLY |
| Marketing and sales | CRM data | DESIGN ONLY |
| Business operations | ERP data | DESIGN ONLY |
| Government and public administration | public records; regulated | DESIGN ONLY |
| Insurance | claims data; regulated | DESIGN ONLY |
| Real estate | listing and title data | DESIGN ONLY |
| Enterprise research and knowledge management | document stores | DESIGN ONLY |

A new vertical needs: a deterministic or model-backed tool adapter, a labelled evaluation set that the team did not
tune on, a policy with its approval gates, and a mission template. It does not need a change to the governed core.
