Why believe any particular statement here?
Every statement made here sits at exactly one level of backing and names the records beneath it. The spread is the honest shape of the work: eleven things it can show, three it can point at, three it puts forward as its own reading, and eight it has to say it cannot answer.
The eight it cannot answer are not tucked into an appendix. They appear on the pages themselves, because what the evidence could not settle is part of what it reports.
This page Procurement's own sources, denominators, coding rules, claims and limits. The shared evidence dimensions are defined on the Observatory methodology
What is being observed: doing the work, or setting how the work is done?
Two related layers run through every finding in this Observatory. Keeping them apart is what stops a count of one being read as a count of the other.
Participation in the work. What a tool or a person actually does in a procurement area: performing work, shaping the information or options that reach the next step, applying a rule, executing an action. This layer describes activity. A great deal of it can change without any capability changing hands.
Configuration and formal outcome. Who sets how each part of the decision works, and who makes its result official: setting the objective, determining eligibility, configuring the rules, configuring the alternatives, evaluating or selecting, authorizing, executing, recording, and making the outcome official where the separate binding analysis establishes it. This layer describes control over the decision rather than participation in it.
The 49-position analysis concerns the second layer. It records who configures each observed decision capability across the ten procurement areas. It is not a measure of every task a tool performs, it is not a prevalence, a share or an adoption rate, and it says nothing about areas outside the ten examined.
The two layers can move independently, and that is the point of separating them. A provider can perform most of the work in an area while the firm still configures how it runs, and a provider can configure how an area runs without performing any of the work in it.
What does each statement rest on?
Each one carries how far it is backed, the strongest thing arguing against it, and what it may not be used to conclude.
In every one of the ten areas the corpus names, four things can be named separately and are not the same thing: the party that composes the object, the party that validates it, the act that binds it, and the party whose system holds the authoritative instance.
The records this rests on
- cross-arena/ten-arena/ten-arena-control-atlas-v1.csv - composer, validator, binder_the_act_that_binds and authoritative_record_holder are each populated in 10 of 10 rows
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-control-atlas-v1.csv - composer, validator, binder_the_act_that_binds and authoritative_record_holder are each populated in 10 of 10 rows
The strongest thing against it None. This is a statement about the instrument's coverage, not about the world.
What this does not tell you That the four positions matter equally, that they are equally stable, or that any of them is worth more than another.
Agentic capability is evidenced composing, preparing, recommending, routing and extracting on consequential procurement objects in every area where any agentic capability was inspected at all.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-04
- arenas/*/qualification/qualification-participants-*.jsonl - participation_mode advisory 23, operational-preparation 18 of 78 capability rows
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-04
- arenas/*/qualification/qualification-participants-*.jsonl - participation_mode advisory 23, operational-preparation 18 of 78 Population A register rows
The strongest thing against it Goods receipt and acceptance CL-03: one dated announcement names fourteen supply-chain AI agents and NOT ONE is evidenced acting on a goods receipt, an acceptance state, an inspection disposition, a return, a three-way-match receipt state or a service entry sheet. Composition is not universal. supplier-onboarding codes D08 explicitly absent on the same point.
What this does not tell you How much composition happens, by how many capabilities, at how many buyers. There is no denominator.
No inspected artifact evidences an agentic capability performing the binding act on a consequential procurement object, in ten areas and three probes.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-01
- cross-arena/ten-arena/binding-frontier-v1.csv - machine_performs_binding_act is 'no' in 7 areas, 'YES' in 2 (both configured-deterministic-rule), 'CONTESTED' in 1
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-01
- cross-arena/ten-arena/binding-frontier-v1.csv - machine_performs_binding_act is 'no' in 7 arenas, 'YES' in 2 (both configured-deterministic-rule), 'CONTESTED' in 1
The strongest thing against it Invoice to payment C-003 - SAP Joule releasing an invoice from a payment block and cancelling a posted document. An agentic capability, coded execution, qualified at both registers, acting on CONSEQUENTIAL records in scope for the area. It survives this claim on two qualifications the area supplied itself: both objects are reversible-by-the-acting-party, and a person instigates. THE FIRST QUALIFICATION LIVES IN A FIELD CODED IN ONE AREA OF TEN.
What this does not tell you That agentic capabilities CANNOT bind, or that none does anywhere. This rests on an estate with 94 nil routes across 74 named estates, 31 of them hard retrieval blocks.
Where a machine performs the binding act in this corpus, the machine is a configured deterministic rule, in two areas on two unrelated object families.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-02
- binding-frontier-v1.csv - requisition-guided-buying O-2 and supplier-onboarding O-1, both execution_basis 'configured-deterministic-rule'
- arenas/requisition-guided-buying/qualification C-002 limitation: 'This is deterministic workflow automation configured by the buying organisation, NOT an agentic capability'
- arenas/supplier-onboarding/qualification C-001 limitation: 'no agent is named in this flow and none is claimed'
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-02
- binding-frontier-v1.csv - requisition-guided-buying O-2 and supplier-onboarding O-1, both execution_basis 'configured-deterministic-rule'
- arenas/requisition-guided-buying/qualification C-002 limitation: 'This is deterministic workflow automation configured by the buying organisation, NOT an agentic capability'
- arenas/supplier-onboarding/qualification C-001 limitation: 'no agent is named in this flow and none is claimed'
The strongest thing against it Purchase order and fulfilment C-003, CONTESTED - a scheduled job finalizes an autonomously awarded negotiation and generates purchasing documents under an integration user with Associated Person Type set to None. Refused on THREE NAMED GAPS, not on absence.
What this does not tell you Any deployment, adoption or prevalence. Both cases are documented product behaviour on a configured path; neither artifact names a customer or a date of use.
In Microsoft Marketplace, the publisher's Activate Subscription API call was removed from the path between a customer's purchase and the start of billing, and the party holding the authoritative subscription state was the same party before and after.
The records this rests on
- historical/hc-04-marketplace-autoactivation/historical-case-record-marketplace-autoactivation-v1.jsonl - outcome_class infrastructure-reinforcement, confidence high, object_identity_test passed
- the holder sentence is WORD-FOR-WORD IDENTICAL in both periods: 'The end user's bill is based on the state of the SaaS subscription that Microsoft maintains'
- dependency_changed 'established': the summary table moves four rows from Yes to No and 'Billing starts' from 'After activation' to 'Immediately after purchase'
- authority_moved 'explicitly absent'
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- historical/hc-04-marketplace-autoactivation/historical-case-record-marketplace-autoactivation-v1.jsonl - outcome_class infrastructure-reinforcement, confidence high, object_identity_test passed
- the holder sentence is WORD-FOR-WORD IDENTICAL in both periods: 'The end user's bill is based on the state of the SaaS subscription that Microsoft maintains'
- dependency_changed 'established': the summary table moves four rows from Yes to No and 'Billing starts' from 'After activation' to 'Immediately after purchase'
- authority_moved 'explicitly absent'
The strongest thing against it The interface-only-change counterexample is UNRESOLVED, not refuted: the archive holds no capture of the plan-configuration page, so whether auto activation existed as a setting before it was announced is open.
What this does not tell you How many plans are configured this way. Existing plans default OFF, only new plans flipped ON, and the announcement states no adoption level. Nothing here is an observation about revenue: that billing begins earlier is an observation about a record state.
In the Microsoft Marketplace case the publisher held a request that gated a transition, not the state itself; the state, the suspension power and the unilateral 30-day void were the incumbent's in the baseline period.
The records this rests on
- historical/hc-04-marketplace-autoactivation - baseline artifacts archived 2026-03-28 and page-dated 2025-12-01
- 'The subscription state is changed to Suspended on the Microsoft side before the publisher takes any action'
- the publisher's own activation call returns a 200 whose text calls Microsoft's stored status 'the definitive answer'
- 'The publisher has 30 days to resolve the asset when the status is PendingFulfillmentStart. Otherwise, the asset is voided'
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- historical/hc-04-marketplace-autoactivation - baseline artifacts archived 2026-03-28 and page-dated 2025-12-01
- 'The subscription state is changed to Suspended on the Microsoft side before the publisher takes any action'
- the publisher's own activation call returns a 200 whose text calls Microsoft's stored status 'the definitive answer'
- 'The publisher has 30 days to resolve the asset when the status is PendingFulfillmentStart. Otherwise, the asset is voided'
The strongest thing against it Recorded rather than suppressed: a JSON field comment in the same baseline artifact reads 'This is the date when the subscription was activated by the ISV and the billing started.' It is a field comment on startDate describing the manual flow, in a document whose normative text calls the publisher's call a request. It does not establish that the publisher held the state.
What this does not tell you That the publisher gained or lost anything economically. No pricing power, value capture, market share or bargaining outcome is established.
Across the nine areas on the shared infrastructure schema, the 68 adjudicated infrastructure rows carry seven distinct role values, of which transaction infrastructure that holds the official state (18) and public registers (13) are the two that hold state, form-defining-body (10) sets grammar without holding an instance, and transaction-enablement-layer (6) does neither.
The records this rests on
- arenas/*/qualification/qualification-infrastructure-*.jsonl - mechanically counted: authoritative-transaction-rail 18, unresolved 18, public registers 13, form-defining-body 10, transaction-enablement-layer 6, not-applicable 2, hybrid 1
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- arenas/*/qualification/qualification-infrastructure-*.jsonl - mechanically counted: authoritative-transaction-rail 18, unresolved 18, authoritative-register 13, form-defining-body 10, transaction-enablement-layer 6, not-applicable 2, hybrid 1
The strongest thing against it requisition C-009 - GSA's FAS Catalog Platform HOLDS the MAS catalog record AND, in its own channel, DISPLACES one of the document forms that governs it. Form-defining and record-holding are not always separate parties.
What this does not tell you That these roles are exhaustive, or that 'unresolved' at 18 of 68 is a role. It is an evidence state and the second most common value in the field.
In seven of ten areas the party that defines the permissible form of the consequential object holds no instance of it, and names the systems that do.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-05
- ten-arena-control-atlas-v1.csv - form_defining_body populated 10 of 10 and distinct from authoritative_record_holder in 7
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-05
- ten-arena-control-atlas-v1.csv - form_defining_body populated 10 of 10 and distinct from authoritative_record_holder in 7
The strongest thing against it requisition C-009 again, and it is the same counterexample: one party occupies both.
What this does not tell you That form-setting is worth less or more than holding. No economic comparison is available.
In the one historical comparison with an admitted baseline on both sides, the counterparty's dependency on the incumbent system increased while the counterparty's control did not decrease, because it had none of the relevant control to begin with.
The records this rests on
- historical/hc-04-marketplace-autoactivation - dependency_changed 'established'; authority_moved 'explicitly absent'; object_holder identical in both periods
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- historical/hc-04-marketplace-autoactivation - dependency_changed 'established'; authority_moved 'explicitly absent'; object_holder identical in both periods
The strongest thing against it requisition-guided-buying O-2, and it is UNRESOLVED: there the binding act itself became machine-performable inside the incumbent - a review step ELIMINATED rather than routed. HC-02 was the case positioned to adjudicate it and returned not-adjudicable-on-inspected-evidence.
What this does not tell you That this generalises. One case, one piece of transaction infrastructure, one vendor. HC-04's own limitation states it is NOT portable to other transaction infrastructure, and this area's own record contains the contrary path where the vendor activates.
The authoritative record holder is named in first-party documentation in ten of ten areas; it is the only element of the seven-element chain that is fully populated with no not-established cell and no derived value.
The records this rests on
- ten-arena-control-atlas-v1.csv authoritative_record_holder - 10 of 10 populated, 0 not-established
- structural-taxonomy-v1.csv D02 object-holder - established in 10 of 10
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- ten-arena-control-atlas-v1.csv authoritative_record_holder - 10 of 10 populated, 0 not-established
- structural-taxonomy-v1.csv D02 object-holder - established in 10 of 10
The strongest thing against it None on coverage. The strategic inference that holding is therefore the decisive position is the PRODUCT'S inference and is filed as P2-16, a Hypothesis.
What this does not tell you That holding confers advantage. Coverage of a field is not evidence about the value of the position it names.
Nine adjudicated rows across six areas are coded participation_mode 'execution', and that field records THAT a named subject performs an operation, not what kind of performer the subject is; three of the nine disclaim an agentic mechanism in their own limitation fields and a fourth has had its mechanism ruled unresolved.
The records this rests on
- mechanical count over the canonical capability registers: execution 9, across contingent-workforce, invoice-to-payment, purchase-order-fulfilment, requisition-guided-buying, supplier-onboarding, saas-acquisition
- requisition C-002 limitation: 'NOT an agentic capability'; Supplier onboarding C-001 limitation: 'no agent is named in this flow and none is claimed'
- cross-arena/historical-reconciliation/hc01-identity-consequence-ruling-v1.md - contingent-workforce C-008 ruled machine-operation-mechanism-unresolved
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- mechanical count over the canonical Population A registers: execution 9, across contingent-workforce, invoice-to-payment, purchase-order-fulfilment, requisition-guided-buying, supplier-onboarding, saas-acquisition
- requisition C-002 limitation: 'NOT an agentic capability'; Supplier onboarding C-001 limitation: 'no agent is named in this flow and none is claimed'
- cross-arena/historical-reconciliation/hc01-identity-consequence-ruling-v1.md - contingent-workforce C-008 ruled machine-operation-mechanism-unresolved
The strongest thing against it None. This is a statement about coding, verifiable by re-running the count.
What this does not tell you That nine is a small number or a large one. There is no denominator.
Where an area's grammar attaches the binding act to a RECORD STATE, software has been evidenced performing it. Where the grammar attaches the act to a NAMED OFFICE or to a COUNTERPARTY'S ACCEPTANCE, no software of any kind has been evidenced performing it.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-03, level Pattern
- the decisive pair: requisition-guided-buying O-2 codes institutional closure explicitly absent and software sets the state; goods-receipt-acceptance O-2 codes it established - 'acceptance is the responsibility of the contracting officer' - and the corpus's most capable agent stops at a documented dialog
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-03, level Pattern
- the decisive pair: requisition-guided-buying O-2 codes institutional closure explicitly absent and software sets the state; goods-receipt-acceptance O-2 codes it established - 'acceptance is the responsibility of the contracting officer' - and the corpus's most capable agent stops at a documented dialog
The strongest thing against it FILED BY THE AREA THAT PROPOSED THE MECHANISM, and it is the corpus's first Hypothesis-level claim: 'The Peppol Receipt Advice attaches acceptance to a document state rather than to a named office, and this area found no capability setting it either.' A record-state binding act with nothing performing it REFUTES THE SUFFICIENCY of the pattern. It must appear wherever this claim appears.
What this does not tell you That record-state grammars CAUSE machine binding, or that named-office grammars PREVENT it. HC-03 was commissioned to test this historically and returned not-adjudicable-on-inspected-evidence. THIS CLAIM IS CURRENT-STATE ONLY.
Across the areas where an agentic capability was inspected at the binding step, the capability stops on the composition side of the actor, system or institution that makes the outcome official while the system holding the object remains unchanged.
The records this rests on
- TA-04 with TA-01 together across 10 areas
- binding-frontier-v1.csv furthest_state_reached_by_an_agentic_capability - composition in direct-materials, drafting in contingent-workforce and contract-lifecycle, six of seven chain steps in goods-receipt-acceptance
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- TA-04 with TA-01 together across 10 arenas
- binding-frontier-v1.csv furthest_state_reached_by_an_agentic_capability - composition in direct-materials, drafting in contingent-workforce and contract-lifecycle, six of seven chain steps in goods-receipt-acceptance
The strongest thing against it FOUR OF TEN STOPS ARE 'MERELY UNEVIDENCED' - inferred from silence rather than described by an artifact. Only ONE area has a stop documented by the vendor at the binding step itself. The pattern is partly a statement about what vendors publish.
What this does not tell you Anything causal, and anything about how far capabilities will go. No trend, no rate, no direction.
The artifacts that place an operation on an object and the artifacts that carry a date are largely different artifacts, and three areas report this independently as their own finding.
The records this rests on
- 58 of 104 dated events carry source_class 'institutional publication'
- saas-acquisition is the inverse case: 13 of 13 events from vendor and operator estates, ZERO institutional
- of 20 vendor artifacts retrieved in the probe cycle, NONE carried a page-visible date; every institutional artifact did
- 94 nil routes across 74 named estates, 31 of them hard retrieval blocks
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- 58 of 104 dated events carry source_class 'institutional publication'
- saas-acquisition is the inverse case: 13 of 13 events from vendor and operator estates, ZERO institutional
- of 20 vendor artifacts retrieved in the probe cycle, NONE carried a page-visible date; every institutional artifact did
- 94 nil routes across 74 named estates, 31 of them hard retrieval blocks
The strongest thing against it contract-lifecycle is 25% institutional while its grammar is published by the UK Government Commercial Function - the split is not clean in the middle. The candidate that generalised this into a grammar claim was tested against the records and REJECTED.
What this does not tell you That undocumented means absent. A missing capture is a property of the archive, not of the world.
Deploying an agent into an area whose official record, obligation or other binding object is held by another party may increase reliance on that party's system while reducing the deploying company's own work.
The records this rests on
- ONE case is consistent with it: HC-04, where dependency_changed is established and authority_moved is explicitly absent
- NO case demonstrates it for an AGENTIC capability - HC-04 contains no agentic capability on either side, and HC-01, HC-02 and HC-03 all returned not-adjudicable-on-inspected-evidence
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- ONE case is consistent with it: HC-04, where dependency_changed is established and authority_moved is explicitly absent
- NO case demonstrates it for an AGENTIC capability - HC-04 contains no agentic capability on either side, and HC-01, HC-02 and HC-03 all returned not-adjudicable-on-inspected-evidence
The strongest thing against it The mechanism it generalises is drawn from a case with NO agent in it. Generalising from a configuration change to agentic deployment is the step this claim has NOT earned, which is why it is a Hypothesis.
What this does not tell you Anything causal, anything about prevalence, and anything about who gains. HC-04 establishes no value capture and no bargaining outcome.
The durable competitive position in these areas is control of the official transaction record rather than possession of the most capable agent.
The records this rests on
- the UNDERLYING RULE is Observed: who holds the record is established in 10 of 10 areas and is the method's most load-bearing separation (P2-10)
- the STRATEGIC INFERENCE from coverage to durability is the product's and is not measured anywhere in the corpus
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- the UNDERLYING RULE is Observed: who holds the record is established in 10 of 10 arenas and is the method's most load-bearing separation (P2-10)
- the STRATEGIC INFERENCE from coverage to durability is the product's and is not measured anywhere in the corpus
The strongest thing against it requisition C-009 - GSA's FAS Catalog Platform holds the MAS catalog record AND displaces a governing document form. If holding were the whole position, holder and form-setter would be different parties; here they are one.
What this does not tell you That holders capture more value, earn more, or win. Every economic limb of this claim is barred by the economic evidence boundary and by the absence of a denominator.
A layer that neither holds the official record, obligation or other binding object nor sets its form may still be defensible if it becomes the route by which many parties reach the holder.
The records this rests on
- transaction-enablement-layer is an evidence-backed role value carried by 6 of 68 infrastructure rows
- NO evidence in the corpus bears on whether that position is defensible, durable or valuable
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- transaction-enablement-layer is an evidence-backed role value carried by 6 of 68 infrastructure rows
- NO evidence in the corpus bears on whether that position is defensible, durable or valuable
The strongest thing against it None available, which is itself the problem: a hypothesis no row can bear on is not testable from this corpus.
What this does not tell you Everything economic. This is a position description, not a prediction.
No single stable answerable party has been evidenced for a consequential procurement object, in ten areas and three probes.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-07, level Not established
- structural-taxonomy-v1.csv D18 - not established in 10 of 10 areas
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-07, level Not established
- structural-taxonomy-v1.csv D18 - not established in 10 of 10 arenas
The strongest thing against it The nearest thing, recorded so it is not mistaken for one: the UK debarment regime names a Minister of the Crown and the FAR names the contracting officer. Both are named authorities for ONE act, on ONE object, in ONE jurisdiction. Neither is a stable answerable party across the object's life.
What this does not tell you NEVER 'no one is accountable' and NEVER 'agentic procurement has an accountability gap'. Publishable only as: answerability was tested in ten areas and was not evidenced in any of them.
Whether a completed binding act can be undone, by whom and with what remainder, is coded as a first-class property in one area of ten.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-08
- structural-taxonomy-v1.csv D11 - not established in 7 of 10; two further areas carry 'partial' values that surfaced without being sought
- D17 consequence-of-error - not established in 9 of 10
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-08
- structural-taxonomy-v1.csv D11 - not established in 7 of 10; two further arenas carry 'partial' values that surfaced without being sought
- D17 consequence-of-error - not established in 9 of 10
The strongest thing against it None. This is a statement about the instrument.
What this does not tell you That the other nine areas are irreversible, or reversible. THIS IS THE CORPUS'S MOST FRAGILE LOAD-BEARING CELL: the qualification that rescues P2-03's counterexample lives in a field nine areas do not carry. If the other nine had coded it, P2-03 would be stronger or narrower, and nothing in this corpus says which.
What performed the work before the current mechanism is not established in three of the four historical cases.
The records this rests on
- HC-01 - ZERO pre-current-mechanism evidence rows; three permitted searches exhausted across four recorded nil routes
- HC-02 - one pre-current-mechanism row that is SILENT on the mechanism rather than describing its absence, in a one-paragraph-per-feature summary document
- HC-03 - three baseline candidates inspected and ALL THREE REJECTED on stated grounds; eight routes returned no admissible body
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- HC-01 - ZERO pre-current-mechanism evidence rows; three permitted searches exhausted across four recorded nil routes
- HC-02 - one pre-current-mechanism row that is SILENT on the mechanism rather than describing its absence, in a one-paragraph-per-feature summary document
- HC-03 - three baseline candidates inspected and ALL THREE REJECTED on stated grounds; eight routes returned no admissible body
The strongest thing against it None. Each case records the exact routes that returned nothing.
What this does not tell you That nothing existed before. A route that returned nothing establishes that the route returned nothing. A missing capture is a property of the archive, not of the world.
Whether the SAP Fieldglass 'GLA agent' is a person, a role, a scheduled process or a model-driven capability is not established.
The records this rests on
- cross-arena/historical-reconciliation/hc01-identity-consequence-ruling-v1.md - ruled machine-operation-mechanism-unresolved
- 'GLA' expands to General Ledger Account in SAP's own abbreviation list; 'agent' in SAP Fieldglass's own administration guide denotes a scheduled background process, and that meaning may NOT be transferred because no artifact connects it to the GLA agent
- no inspected artifact describes any determination, which is what the agentic-capability definition requires; the same guide lists the act among things 'users take'
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/historical-reconciliation/hc01-identity-consequence-ruling-v1.md - ruled machine-operation-mechanism-unresolved
- 'GLA' expands to General Ledger Account in SAP's own abbreviation list; 'agent' in SAP Fieldglass's own administration guide denotes a scheduled background process, and that meaning may NOT be transferred because no artifact connects it to the GLA agent
- no inspected artifact describes any determination, which is what the agentic-capability definition requires; the same guide lists the act among things 'users take'
The strongest thing against it None. The refusal to resolve is the finding.
What this does not tell you That it is not agentic. NO inspected artifact states that either, and 'not established' is not a negative fact. THIS CASE IS REMOVED FROM EVERY HEADLINE REQUIRING A DETERMINATE CLASSIFICATION.
No causal link is established between any institutional event in the corpus and the behaviour of any capability, platform, product or buying system, in either direction.
The records this rests on
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-12, level Not established, filed in nine areas
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/ten-arena/ten-arena-claim-ledger-v1.jsonl TA-12, level Not established, filed in nine arenas
The strongest thing against it None available, and none constructible from this method.
What this does not tell you Any sentence in which a structural property is the subject of a verb of causation.
No capability recorded in any register is established as being in production use by any named buyer.
The records this rests on
- area claim ledgers record this per area, e.g. Contingent workforce CL-07 at level Not established across all eight participant rows
- every participant row rests on product documentation, a release note or an announcement, all of which evidence that a capability is DESCRIBED
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- arena claim ledgers record this per arena, e.g. Contingent workforce CL-07 at level Not established across all eight participant rows
- every participant row rests on product documentation, a release note or an announcement, all of which evidence that a capability is DESCRIBED
The strongest thing against it None. No retrieved artifact names a buyer using any capability recorded.
What this does not tell you Any deployment, adoption, usage, customer count, share or momentum statement whatsoever.
Whether the buying organisation's own ERP or master-data system belongs in the infrastructure population is not established, because no such system was ever retrieved.
The records this rests on
- supplier-onboarding NR-22 records it: the buying organisation's own ERP or MDM is ABSENT from the infrastructure examined entirely
- the area states this against itself as the one custodian most likely to refute its own claim
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- supplier-onboarding NR-22 records it: the buying organisation's own ERP or MDM is ABSENT from Population B entirely
- the arena states this against itself as the one custodian most likely to refute its own claim
The strongest thing against it None.
What this does not tell you That buyer systems do not hold official records, obligations or other binding objects. They very plausibly do, and the corpus cannot see them.
The corpus establishes no prevalence, share, rate, ranking, momentum, forecast, pricing power, value capture, revenue effect, switching cost or winner-or-loser status of any kind.
The records this rests on
- cross-arena/historical-design/economic-evidence-boundary-v1.md
- every one of the four historical case records carries the identical economic_boundary_ack
- there is NO DENOMINATOR anywhere in the corpus
As the record words it
The corpus's own vocabulary, unedited. The lines above translate it into publication language; these are the words the record uses.
- cross-arena/historical-design/economic-evidence-boundary-v1.md
- every one of the four historical case records carries the identical economic_boundary_ack
- there is NO DENOMINATOR anywhere in the corpus
The strongest thing against it The nearest economic-sounding observation in the programme is HC-04's earlier billing start, and that case's own record refuses the reading: 'That billing begins earlier is an observation about a record state and is not an observation about revenue.'
What this does not tell you Everything in the sentence above.
How much did the evidence leave open?
Eighteen questions asked of each of the ten areas. Where the sources did not answer one, it is reported as unanswered and never shown as a low score or an empty box.
Two of those gaps carry more weight than the rest. Whether a completed action can be undone, and by whom, was recorded in only one area of the ten. And whether any single party is answerable for a record across its life was asked in all ten and answered in none. The second one is not an oversight: the question was asked ten times and came back empty ten times, which is a very different thing from finding that nobody is answerable.
Why is one area counted separately?
Nine areas were assessed against a shared method. One was assessed before that method existed, so its rows answer slightly different questions. They are reported apart and never added into one figure.
| How it was assessed | Areas | Capabilities examined | Systems examined |
|---|---|---|---|
| Shared method | 9 | 55 | 68 |
| Assessed before the shared method existed | 1 | 23 | 13 |
The two are reported separately. A single figure that quietly folded in the area assessed under the older method would be doing something the records do not support.
Where did the evidence run out?
Searches that were actually run and came back with nothing usable. They are recorded per area, with the source and how it failed, so what could not be reached is visible rather than left to be guessed at.
| Area of procurement work | Searches recorded here |
|---|---|
| Goods receipt and acceptance | 22 |
| Supplier onboarding | 22 |
| Requisition and guided buying | 12 |
| Contract lifecycle | 12 |
| Purchase order and fulfilment | 9 |
| Direct materials | 9 |
| Invoice to payment | 6 |
| Supplier risk | 0 filed elsewhere by this area, so a zero here is a filing convention rather than a finding that nothing was looked for |
| Contingent workforce | 0 filed elsewhere by this area, so a zero here is a filing convention rather than a finding that nothing was looked for |
| SaaS acquisition | 0 filed elsewhere by this area, so a zero here is a filing convention rather than a finding that nothing was looked for |
Ninety-two are filed in the searchable records; the full count of 94 adds two an area wrote up in prose instead. Four areas show zero here because they filed their searches elsewhere, so a zero is a filing convention rather than a finding that nothing was looked for.
What holds when all ten are read together?
Each one names how many of the ten areas support it, and the strongest case against it.
Across ten areas and three probes, no inspected artifact evidences an AGENTIC capability performing the binding act on a consequential procurement object.
The strongest thing against it purchase-order-fulfilment C-003. Oracle's Autonomous Sourcing Assistant: 'After an autonomously awarded negotiation is approved, the subsequent ESS job run finalizes the award and generates the purchasing documents', with the write privilege held by 'an integration user (a new user with the Associated Person Type set to None)'. It is refused on three NAMED GAPS in the artifact — which document type is created, the status it is created in, and whether any buyer runs it with approvals disabled — and not on absence.
DETERMINISTIC configured automation HAS performed the binding act, in two of the ten areas, on two unrelated object families, evidenced in each vendor's own first-party documentation.
The strongest thing against it None to the claim itself. The nearest limit is that BOTH cases are documented product behaviour on a CONFIGURED path: neither artifact names a customer, a deployment or a date, and supplier-onboarding's carries no page-visible date at all. requisition's own artifact poses the question 'What expenditures can be automatically approved?', which is a setting, not a practice.
Where an area's grammar attaches the binding act to a RECORD STATE, software has been performing it. Where the grammar attaches the binding act to a NAMED OFFICE or to a COUNTERPARTY'S ACCEPTANCE, no software of any kind has been evidenced performing it.
The strongest thing against it goods-receipt-acceptance CL-12's own attached counterexample, filed by the area that proposed the mechanism: 'The Peppol Receipt Advice attaches acceptance to a document state rather than to a named office, and this area found no capability setting it either.' A record-state binding act with no software performing it REFUTES the sufficiency of the pattern. It is the strongest objection to this claim and it comes from inside the corpus.
Agentic capability is evidenced composing, preparing, recommending, routing and extracting on consequential procurement objects in every area where any agentic capability was inspected at all.
The strongest thing against it goods-receipt-acceptance CL-03. In one dated announcement naming FOURTEEN supply-chain AI agents, not one is evidenced acting on a goods receipt, an acceptance state, an inspection disposition, a return, a three-way-match receipt state or a service entry sheet. Composition is not universal — in some areas the agentic capabilities do not reach the object at all.
The party that defines the permissible FORM of a consequential object very often holds no instance of it, and names the systems that do.
The strongest thing against it requisition-guided-buying C-009. GSA's FAS Catalog Platform BOTH holds the MAS catalog record AND, in its own channel, displaces one of the document forms that governs it. Form-defining and record-holding are not always separate parties, and the area records this against its own CL-04.
Where an area's admissibility state is held by an institution, that institution transacts with none of the parties the state binds.
The strongest thing against it THE ABSENT ONE, and supplier-onboarding names it against its own claim. Its frozen contract names the buying organisation's own ERP or MDM as a candidate holder, NR-22 records that no artifact naming a specific buyer's master was ever retrieved, and the area states that if that unit were inspected the claim could fail. the infrastructure examined uniform institutional orientation is an artifact of that gap, not a finding about the area.
Across ten areas and three probes, no single stable answerable party has been evidenced for a consequential procurement object.
The strongest thing against it supplier-risk and supplier-onboarding come closest: the UK debarment regime names A MINISTER OF THE CROWN as the party whose decision creates the designation. That is a named authority for one act on one object in one jurisdiction. It is not a stable answerable party for the object across its life, and neither area claims it is.
Reversibility is coded as a first-class property in only one of the ten areas, and in that area it is the area's central finding. In the other nine it is not observable and has never been filled by analogy.
The strongest thing against it Two areas carry PARTIAL reversibility that was found without being sought. contingent-workforce: work orders and revisions can be withdrawn before a supplier takes action. goods-receipt-acceptance: the Reverse Goods Receipt quick action is documented and Joule performs it. Neither area coded reversibility as a field, and both facts surfaced anyway.
The two-register design across ten areas measures the availability of dated evidence, not change in capability.
The strongest thing against it purchase-order-fulfilment, the one area where the gap is partly substantive: the capabilities examined had 0 members at the cutoff and 2 now, and C-003 is not-qualified-at-cutoff because its artifact belongs to a 2026 release rather than because it carries no date.
The disclosure boundary closed measurably between Wave 2 and Wave 3: the same method applied to three fresh areas returned 38 percent fewer dated events against 87 percent more nil routes.
The strongest thing against it Area selection is not held constant. Wave 3's three areas were chosen for structural contrast across the procure-to-pay spine, not for estate richness, and requisition's shortfall is partly a cap artifact — two publishers reached the three-event-per-actor cap with further qualifying artifacts available. A yield comparison across differently-selected waves is not a measurement of the estate.
A machine may be able to perform a binding act only where the grammar of the object supplies a state to set WITHOUT also naming who is answering for setting it.
The strongest thing against it Supplied by the area that filed the hypothesis: 'The Peppol Receipt Advice attaches acceptance to a document state rather than to a named office, and this area found no capability setting it either.'
No causal link is established between any institutional event in the ten-area corpus and the behaviour of any capability, platform, product or buying system.
The strongest thing against it requisition-guided-buying EV-07 and C-012 both name the federal micro-purchase, which is the closest the corpus comes to a link. It establishes that the threshold governing a channel changed; it establishes nothing about how the channel or its operators behaved.
What method produced each product's numbers?
One methodology destination rather than a methods section at the foot of every page. Each product's offering selection, coding rules, class definitions, non-comparability rules and limitations live here, under stable anchors the product pages link to.
Agentic Pressure
Offering selection 54 offerings, selected rather than enumerated
The 54 offerings were selected, not enumerated. This is not a census of procurement software. It cannot say what share of the market is agentic, how many companies use any of it, or whether the selection represents anything outside itself.
66 of 70 evidence records are vendor self-published. That is evidence a capability was described by the party selling it, not that a customer ran it.
The stage model nine stages, frozen order, canonical ids preserved
Nine stages run from a need arising to money leaving. The canonical stage ids and the analytical labels are the corpus's and are untouched; the action phrases a reader meets (Need, Define, Find, Compare, Check, Negotiate, Approve, Order, Pay) are a second, reader-facing layer over them. Neither reading may reorder, filter or hide a stage.
Every offering was examined against every stage, so the grid is complete and square: 54 × 9 = 486 offering-stage observations. A count at one stage is directly comparable to a count at another because the denominator is the same 54 at every one.
Effect coding 184 demonstrated, 282 none, 20 unsettled
Each observation is coded demonstrated, no evidenced effect, or evidence-insufficient. Evidence-insufficient is not an absence. The documents were examined and did not establish an effect either way, and those 20 stay in the denominator rather than being counted as a no.
Activity classes, and the three-stage pattern three natural-break bands over a constant denominator
Activity is demonstrated effects over a constant denominator of 54. The three bands are set by natural breaks across the nine stages rather than by a threshold anyone chose, at 22.2% and 42.6%. A break may not split equal values, so two stages with equal activity always share a band.
- Higher activity — Define, Check, Pay
- Middle activity — Need, Find, Compare, Negotiate, Approve
- Lower activity — Order
The higher band holds exactly three stages and they are not adjacent, which is what the product page's central argument rests on. The membership is derived from the banding rather than chosen, and a build-time gate fails if it ever stops being Define, Check, Pay.
Participation depth, and why the third rung is a question two rungs read a corpus band; the third asks about authority
Every demonstrated effect carries one of three corpus bands. The rungs name what those mean for a reader, and each carries the corpus band it reads so the mapping can be checked. The depth reading shows the deepest band reached at a stage, which is a ceiling and not a typical case.
- Advises — Interpret, recommend or prepare. 104 of 184. Corpus band Advises: Informs, retrieves, summarises, drafts, classifies or flags, without shifting control.
- Executes — Perform a workflow action. 78 of 184. Corpus band Judges or completes: Makes a material judgment, completes a core sub-process, or coordinates a consequential step.
- Binds the outcome — Execute or bind an outcome so it counts. 2 of 184. Corpus band Executes or binds: Executes, binds, governs, bypasses or collapses the stage, or independently controls it.
The third rung reads “Binds the outcome”, which is what the corpus band records. The band's own verb is “Executes or binds”: an outcome executed or bound, and so made official. That is not the same as an agent holding authority to apply or control the rule governing the outcome. The examined evidence does not establish that an agent independently applies or controls the rule governing an outcome. None of the following is evidenced anywhere in the examined set: refuse an action; stop or reverse one; compel compliance; override an exception; make the binding determination; control the authoritative state rather than write to it.
The rung used to read “Enforces”, with the corpus verb printed beside it to hold the label honest. That was not enough: a reader meeting the word reads an authority the evidence does not show, and the two effects actually recorded are executions inside a rule somebody else configured. A build-time gate now forbids the word in the label rather than pinning a particular string, so no later edit can reintroduce it in another form.
The established-emphasis comparison, and its sources an archetype from product documentation, not a measured population
Authority. Vendor product documentation for established procurement systems. Not the 54-offering corpus, not a measured population, and carrying no denominator.
Digital procurement is an archetype drawn from vendor product documentation, not a measured population. It describes characteristic product emphasis, not what established systems could or could not do. Only the Agentic offerings column is counted, over the 54 examined offerings.
- S1 SAP — About reverse auctions
- S2 SAP — RFx response evaluation
- S3 SAP — Strategic sourcing with RFx
- S4 Oracle — Price breaks and price tiers
Every claim of a characteristic strength in that comparison carries at least one of these, checked at build time; a row that claimed one without a source would fail the build. The comparison describes emphasis, never exclusive capability - established systems support approvals, ordering, payment and much else, and a gate rejects the words that would turn the claim into an incapability.
Non-comparability rules three counts that must never be crossed
The journey and the domain views are separate populations. The 54 offerings were selected before any procurement area was defined, and no key joins an offering to an area. A domain-by-stage grid would have to invent both the join and the axis, and it would look like evidence while being a guess. The domain analysis is therefore disclosed here, under the rule, rather than drawn beside the journey.
- ExecutesPerforms the operation itself.
- Prepares the operationComposes or stages what another party then acts on.
- Unresolved: executes or preparesThe documents do not settle which of the two it is.
Contingent workforce
1 currently qualified of 8 examined
Contract lifecycle
Participant rows exist; none is currently qualified.
9 examined
Direct materials
Participant rows exist; none is currently qualified.
6 examined
Goods receipt and acceptance
1 currently qualified of 6 examined
Invoice to payment
4 currently qualified of 19 examined
Purchase order and fulfilment
2 currently qualified of 4 examined
Requisition and guided buying
1 currently qualified of 6 examined
SaaS acquisition
No participant file: this domain was assessed before the shared method existed.
not examined under this method
Supplier onboarding
3 currently qualified of 6 examined
Supplier risk
1 currently qualified of 2 examined
One mark per currently qualified capability row, in the order the domains were recorded rather than by depth. Ordering them by how agentic they look would be a ranking this evidence does not carry. Counts are of inspected capability rows, never of vendors, products or spend.
Two different objects share the integer 184. The journey view's 184 is demonstrated stage effects. The operating-model register's 184 is dated event rows. They are not the same population and must never be quoted as one.
Nothing here is a trend. 47 of 70 records carry an explicit undated limitation, so two thirds of the comparable evidence has no date on it and no rate of change can be read from any of it.
Evidence limitations what the four measured absences do and do not establish
Four absences were measured across all 54 offerings. Not one documents an agent that can be reversed, appealed or overridden, or that holds the authority to refuse.
- 0 of 54 — evidenced authority to block or refuse
- 0 of 54 — evidenced reversibility
- 0 of 54 — evidenced appeal
- 0 of 54 — evidenced override
An absence of documented activity is an absence in the inspected documents. It is not an absence of capability, and it is never rendered as a zero, a blank or a low score.
At paying the supplier, no effect reaches the binding band at all, and the strongest inspected record states that payment confirmation is a separate act not evidenced as the agent's. The product page may therefore say an approved invoice is posted ready for payment; it may not say an agent releases, confirms or controls payment. A gate fails the build if that record ever changes.
Claim standings what each Agentic Pressure claim rests on, and what would move it
Every claim the instrument supports, its population, and the boundary around it. Two populations run through this table and are never divided into one another: the breadth instrument of 184 demonstrated effects across 486 offering-stage cells over 54 offerings, and the mechanism instrument of 21 supported cross-stage interactions.
Updated 2026-08-23. Source commit
a46c47265e58. The classification model behind
the mechanism rows is the normalized agenticity model: four conditions, all required, each
carrying a quotation from the reopened source, with eight refused bases including a product
name, an AI brand, the word automatic, an act of execution and a consequential effect.
Where does this data come from?
This page shows a fixed copy of an evidence record kept separately. The copy holds no authority of its own; the record behind it does.
What this may not be used for
No prevalence, adoption, share, rate, ranking, momentum or forecast - there is no denominator anywhere in this corpus. No causality. No economic content and no company ranked. No deployment: documented product behaviour is not deployment. A zero is not an absence and a blank is not a zero. Never 'no one is accountable' - answerability was tested in ten arenas and was not evidenced in any of them.
Derived from the corpus at commit b5a347de7316aa7e3ddf1379a6cf8d6816486d16,
generated 2026-08-17. Figures are counted across ten areas of procurement work, from documents published by the companies and institutions themselves - not a market, not a sample, not a survey.