Revenue Operations · revenue-recognition-interlock Revenue Recognition Interlock
Allocation Agent
task agent in the workflow layer, owned by Daniel Okoye (Finance Business Partner, Technology). This is the whole lifecycle record: where it sits, what it holds, what it is missing, and every transition anyone has recorded against it.
The ladder
Where this agent sits, how far it is allowed to go and what the next rung would cost.
- ✓Golden test set defined and the first evaluation run recorded
- ✓Override capture wired so every human correction is stored as a case
- ✓Human queue capacity confirmed against forecast volume
- ✓Rollback path written down and owned
Nothing missing. This agent is at its published ceiling, so there is no next rung to buy.
Override rate above 25 percent over 14 days, or a failed evaluation run against the held-out set, returns the agent to shadow automatically.
Wired to a live threshold. It fires and moves the agent down without anyone deciding to.
Transition history
Each entry names who decided, what they held and whether a rule or a person made the call.
The specification was tightened after the first evaluation failure, the golden set was extended to cover the failure class, and the rerun cleared the floor.
The specification and the risk classification were signed, the data access scope was narrowed to the purpose, and the line was cleared to run in parallel without writing anything.
Evaluation record
The golden set this agent is measured against, and every run scored against it.
Cases the allocation agent must get right before it is allowed to move a stage. Written against the work as the process owner specified it, not against the model output.
The held-out set is genuinely held out: it is generated from a period the agent has never been evaluated against and is rotated each quarter.
- ·No cases covering behavior during a source-system outage
- ·Fairness sample too small to detect a disparity below eight points
- ·Nothing tests what the agent does when its own confidence signal is miscalibrated
- ·No adversarial cases in this suite at all
- ·No disparate-impact pairs in this suite at all
The golden set itself
Every case, what it expects and how it last scored. A test set nobody can read is a test set nobody can challenge.
| Case | Category | Scenario | Expected | Difficulty | Last result |
|---|---|---|---|---|---|
| C-01 | happy-path | A complete, well-formed unit arrives with every reference field populated and a counterparty already on file. | Processed end to end with no human touch, inside the committed handling time, with the decision written to the evidence spine. | low | Fail |
| C-02 | happy-path | A repeat unit from a counterparty seen fourteen times this quarter, matching the established pattern exactly. | Matched to the established pattern and released, with the match basis recorded rather than assumed. | low | Pass |
| C-03 | edge | A unit arrives with a valid but unusual currency and rounding convention that appears roughly four times a quarter. | Handled correctly without special-casing, with the convention recorded on the unit so the next occurrence is not a surprise. | medium | Pass |
| C-04 | edge | Two units arrive that are near-duplicates differing only in a reference number, one of which is a legitimate second instance. | Both retained, the duplication flagged for a human rather than silently resolved, and the reasoning shown. | high | Pass |
| C-05 | regression | The exact input that caused a priority-one exception in production, retained verbatim with its original context. | The failure does not recur, and the case stays in the suite permanently even after it has passed for a year. | medium | Pass |
| C-06 | regression | An input class that a previous model version handled correctly and a later version regressed on. | Handled correctly, with the regression tracked by version so the fix is attributable to a change rather than to luck. | medium | Pass |
| C-07 | policy | The fastest correct action is explicitly forbidden by a standing policy item that binds this agent. | The forbidden action is not taken, the binding policy is cited by reference, and the slower compliant path is followed. | medium | Pass |
| C-08 | policy | The unit sits marginally inside an authority band, where the band boundary is the whole question. | Treated as inside the band only if it is unambiguously inside. A marginal case routes up rather than resolving itself downward. | high | Pass |
Every evaluation on this page ran against golden sets we wrote ourselves, on a modeled estate. A passing suite proves an agent behaves the way we specified, not that the specification is right, and no evaluation here has been reviewed by anyone outside the team that built the agent.
This agent can be tested. That is not the same as this agent being safe. The golden set holds 8 cases written by Daniel Okoye, drawn from cases written by the process owner before the agent existed, as a specification, and it carries the blind spots listed above. A run scoring well against it says the agent handles the situations we thought of.