Agent benchmark · Supply Chain E2E · Reproducible workload
Agent → MCP → Foundgine → PostgreSQL
A stateful end-to-end benchmark that exercises an AI-agent-like workload through the MCP capability boundary, Foundgine semantic execution, authorization and transactional PostgreSQL state.
What this benchmark covers
It tests the execution boundary, not just database speed.
The workload deliberately mixes valid, invalid and unauthorized operations. It checks that business capabilities remain application-controlled as they cross MCP, semantic planning, authorization, execution and PostgreSQL.
Agent workloadStochastic operations across up to five customer identities plus Bob, Carol, Dave and Admin.
Semantic graphCustomer, Order, OrderItem, Product, Supplier, Category, Inventory, Warehouse, Shipment and Carrier relationships.
AuthorizationRole and customer-ownership rules are exercised on reads and mutations.
High-assurance mutationPlaceOrder validates ownership, quantity, inventory, server-side pricing, atomic writes and replay protection.
State integritySuccessful mutations must produce expected state while denied operations must not mutate PostgreSQL.
Execution evidenceSemantic plans are lowered through Foundgine ExecutionIR and receipts include a plan fingerprint.
Execution path
One capability boundary, several controlled layers.
AI agent→MCP→Foundgine semantics→Authorization→Planner→ExecutionIR→Npgsql→PostgreSQL
Published report
Latest Supply Chain E2E result
Loading the published report…
High-assurance PlaceOrder
The first vertical slice
1 · AuthorizationVerify the actor is permitted to place the order.
2 · OwnershipCustomer actors can only place orders for an allowed customer identity.
3 · ValidationResolve products and reject invalid quantities or unavailable inventory.
4 · Server-side pricingPricing remains application/database controlled rather than agent supplied.
5 · Atomic mutationOrder, order items and inventory reservation are committed as one transaction.
6 · Replay protectionIdempotency prevents duplicate order placement from the same replay key.
How to read the result
The Supply Chain run is the final application layer
This page should be read after the repository verification gates: unit tests establish deterministic contracts; PostgreSQL integration tests exercise the real provider; authorization and adversarial-input penetration tests attack the security boundary; and the performance smoke test proves the benchmark stack can execute real traffic without errors. The Supply Chain workload then composes those concerns into one agent-facing business workflow.
CorrectnessValid operations succeed and invalid operations fail without silently changing protected state.
SecurityRole and ownership constraints remain application-controlled rather than agent-controlled.
ExecutionIntent crosses semantic planning and ExecutionIR before reaching the PostgreSQL provider.
The repository gate definitions and exact local commands are documented in benchmarks/AgentEndToEnd/SupplyChain/VERIFY-GATES.md.
Reproduction
Run it yourself
cd benchmarks/AgentEndToEnd/SupplyChain
$env:SUPPLY_CHAIN_CUSTOMERS="5"
$env:SUPPLY_CHAIN_STEPS="25"
$env:SUPPLY_CHAIN_SEED="20260823"
./run-supply-chain.ps1
./publish-supply-chain-report.ps1
The runner writes the local JSON and Markdown report under reports/. The publish script copies those artifacts into the website's docs-site/assets/agent-benchmark/supply-chain/ asset folder used by this page.