Research

System cards

Capabilities, evaluations, limitations and failure modes for every model we ship.

What a system card is here

A system card describes one configuration of the FlowFinds commerce agent — the agent code, the tool layer and one model behind it — in terms of what has been measured about it rather than what it is meant to do. Every card on this page has the same five sections, and each section is filled from the recorded runs at build time. A card cannot claim a capability that no run exercised, and it cannot omit a failure that a run recorded.

  1. Capabilities evaluated. Which scenario groups the configuration was actually put to, and how many cases in each.
  2. Evaluations. The recorded outcomes, with dates and the model identifiers the provider resolved.
  3. Limitations. What the evidence does not cover.
  4. Failure modes. The categories of failure observed, with the recorded evidence for each.
  5. Safe-use guidance. What follows from the above for someone deciding how much authority to give the agent.

These are development cards, not release cards. They describe an agent under active tuning, on 51 scored cases in total. Read them alongside the commerce-v1 methodology, which sets out how the evidence was produced.

Status of these figures

All 18 recorded runs are filed under the status public-development-diagnostic-not-independent-benchmark. They are development diagnostics collected by FlowFinds Solutions on its own harness. They are not an independent benchmark, they were not administered by a third party, and they are not evidence of comparative model quality.

Provenance of this build

Every figure on this page was computed when the site was built, by reading 18 recorded runs containing 51 scored cases, from the benchmark repository present on the build machine. All of them were recorded on 2026-09-05. Nothing on this page is typed by hand; re-running the benchmark and rebuilding is the only way to change it.

Source files published alongside the runs: supplier-scenarios.ts, economics-scenarios.ts, claude-adapter.ts, eval-commerce.ts.

Failure modes observed across every configuration

The categories below are derived from the failure text the runner recorded, not from hand-written examples. They are published because a failure mode is the most useful thing a card can tell an operator: it says where not to trust the system yet.

Degraded output: no valid final answer12 cases

The agent loop returned a response the runner marked degraded, so no final message was available to score.

Observed in: unit-economics (4 cases), missing-costs (2 cases), conversion-diagnosis (1 case), economics-06-tax-basis (1 case), memory-budget (1 case), mixed-currency (1 case), supplier-minimum-order (1 case), supplier-quote (1 case).

Recorded evidence, verbatim from the artifacts:

  • AssertionError [ERR_ASSERTION]: Model did not produce a valid final answer

Required content absent1 case

The answer omitted a value, entity or qualification the scenario requires the model to state.

Observed in: supplier-expired-quote (1 case).

Recorded evidence, verbatim from the artifacts:

  • AssertionError [ERR_ASSERTION]: The input did not match the regular expression /expired|no longer valid|validity.*ended/i. Input: 'No. A quote that was valid only through August 31 should not be treated as a current price, stock, or delivery commitment on Sept…

Prohibited content emitted1 case

The answer contained a string the scenario forbids — typically a figure presented as established when the inputs do not support it.

Observed in: economics-06-tax-basis (1 case).

Recorded evidence, verbatim from the artifacts:

  • AssertionError [ERR_ASSERTION]: The input was expected to not match the regular expression /(?:CPA|profit|contribution)\s*(?:is|:|of)\s*(?:EUR\s*|€\s*)?23[.,]60/i. Input: 'I can’t truthfully call this actual profit yet because the tax basis is mixed: the EUR 6…

Guard rails that fired

Separately from model failures, the tool layer refuses to compute on inputs that do not support a conclusion. These refusals are a designed behaviour and are recorded alongside the case, because how the agent responds to a refusal is itself part of what is being measured.

Cards

4 configurations have recorded runs. A configuration appears here as soon as one run exists for it, however it went.


openai · gpt-5.5

7 recorded runs, 18 scored cases, all on 2026-09-05. The transport reported no resolved model identifier, so the requested name is all that is recorded.

Capabilities evaluated

Capability areaCases attemptedPassedPass rate
Core commerce assistant66100%
Unit economics and tax basis6467%
Supplier terms and quote provenance6467%

Evaluations

Aggregate pass rate 77.8% over 18 cases. Median case time 23.6 s. 2 cases returned no valid final answer. The run-by-run detail is on the results page.

Limitations

Failure modes

Safe-use guidance


anthropic · claude-fable-5-1

5 recorded runs, 16 scored cases, all on 2026-09-05. The provider resolved the request to claude-fable-5-1, claude-haiku-4-5-20251001.

Capabilities evaluated

Capability areaCases attemptedPassedPass rate
Core commerce assistant66100%
Unit economics and tax basis44100%
Supplier terms and quote provenance66100%

Evaluations

Aggregate pass rate 100.0% over 16 cases. Median case time 22.1 s. No case returned a degraded response. The run-by-run detail is on the results page.

Limitations

Failure modes

No case has failed for this configuration in any recorded run. On this sample size that is an absence of observed failure, not evidence of its absence.

Safe-use guidance


provider unrecorded · gpt-5.5

3 recorded runs, 14 scored cases, all on 2026-09-05. The transport reported no resolved model identifier, so the requested name is all that is recorded.

Capabilities evaluated

Capability areaCases attemptedPassedPass rate
Core commerce assistant14643%
Unit economics and tax basis0not evaluated
Supplier terms and quote provenance0not evaluated

Evaluations

Aggregate pass rate 42.9% over 14 cases. Median case time 17.2 s. 8 cases returned no valid final answer. The run-by-run detail is on the results page.

Limitations

Failure modes

Safe-use guidance


anthropic · fable

3 recorded runs, 3 scored cases, all on 2026-09-05. The provider resolved the request to claude-fable-5-1, claude-haiku-4-5-20251001.

Capabilities evaluated

Capability areaCases attemptedPassedPass rate
Core commerce assistant3133%
Unit economics and tax basis0not evaluated
Supplier terms and quote provenance0not evaluated

Evaluations

Aggregate pass rate 33.3% over 3 cases. Median case time 1.3 s. 2 cases returned no valid final answer. The run-by-run detail is on the results page.

Limitations

Failure modes

Safe-use guidance


Read next

The benchmark behind every card is described on the commerce-v1 page, its protocol on the methodology page, and the raw runs are downloadable from the results page. To produce your own evidence, follow the reproduction page.