Contract lifecycle
The path from what a machine is documented doing to the party holding the record that makes the result official, with how well each step is backed. Where the sources settled nothing, the step says so.
-
What a machine is documented doing
Established by the evidence. Nine capability rows; NONE evidenced setting or completing a signature or execution state -
The record it touches
Established by the evidence. The contract record; the executed instrument; the statutory contract-details notice -
What still has to happen first
Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. STRUCTURAL - authority and binding are not established for every machine mechanism inspected We looked and the sources we inspected did not settle it.Assumed, because nothing says otherwise no document describes a step here; that it stops is inferred from nothing saying otherwise authority and binding are not established for every machine mechanism inspected
UK7 Contract Details Notice - Published after a contract has been signed
the source's own words, quoted exactly -
What makes the change count
Established by the evidence. The UK Government Commercial Function and Government Legal Department publishing standard contracts -
Who holds the official record
Established by the evidence. Vendor repositories hold agreement records; the statutory notice register holds the notice -
What the area relies on
Established by the evidence. Docusign eSignature — transaction data and Certificate of Completion (NOT the Docusign company, and NOT the eDocument); The published standard contracts for public procurement — Short Form Contract, Mid-Tier Contract, Model Services Contract
The action that makes it official Execution of the instrument; the statutory notice follows it Done by The contracting parties. It counts because of a signature act. No machine is documented doing this.
What could this area not settle?
What this area recorded against its own findings, in its own words.
Recorded against itself by this area
nine undated artifacts of which eight are vendor-operated; twelve retrieval routes returned nothing; 4 of 6 infrastructure rows carry no established role
Can the act be undone, and by whom?
What did the evidence settle, dimension by dimension?
Eighteen structural dimensions, each carrying its own evidence state and what it does not establish.
| Question asked | What the evidence says | What it does not tell you |
|---|---|---|
consequential-objectD01 | Established by the evidence. The contract record; the executed instrument; the statutory contract-details notice | Not recorded by the method used for this area |
object-holderD02 | Established by the evidence. Vendor repositories hold agreement records; the statutory notice register holds the notice | Not recorded by the method used for this area |
grammar-or-form-setterD03 | Established by the evidence. The UK Government Commercial Function and Government Legal Department publishing standard contracts | Not recorded by the method used for this area |
composerD04 | Established by the evidence. In-scope organisations form instruments on those forms; capabilities turn user inputs into review-ready contracts | Not recorded by the method used for this area |
validatorD05 | Established by the evidence. Review of the composed instrument | Not recorded by the method used for this area |
binderD06 | Established by the evidence. A separate later execution act - the UK7 Contract Details Notice is published AFTER a contract has been signed | Not recorded by the method used for this area |
deterministic-automationD07 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. Authority and binding are not established for ANY machine mechanism inspected We looked and the sources we inspected did not settle it. | The stop is MERELY UNEVIDENCED. |
agentic-capabilityD08 | Established by the evidence. Nine capability rows; NONE evidenced setting or completing a signature or execution state | Not recorded by the method used for this area |
furthest-deterministic-actionD09 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. No deterministic mechanism evidenced at or across the execution act We looked and the sources we inspected did not settle it. | authority is recorded as not established for any machine mechanism. |
furthest-agentic-actionD10 | Established by the evidence. Turning user inputs into review-ready contracts | C-004's 'automatically initiate a contract' names no object, so no row could be built on it. |
reversibilityD11 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. Not coded and not observable We looked and the sources we inspected did not settle it. | Not recorded by the method used for this area |
externality-radiusD12 | Established by the evidence. The statutory contract-details notice is published to a register and reaches parties outside the contract | Established for the statutory notice only, not for the instrument. |
counterparty-assentD13 | Established by the evidence. Required: the contracting parties execute the instrument | Not recorded by the method used for this area |
rule-codifiabilityD14 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. Whether execution is expressible as a rule any system evaluates is not established for any inspected mechanism We looked and the sources we inspected did not settle it. | Recorded as not established rather than as absent: nine undated artifacts, eight vendor-operated, twelve retrieval routes returning nothing. |
institutional-closureD15 | Established by the evidence. The statutory notice register must carry the notice; publication follows signature | Not recorded by the method used for this area |
authoritative-state-centralizationD16 | Established by the evidence. SPLIT: vendor repositories hold agreement records; the statutory register holds the notice | 4 of 6 infrastructure rows carry no established role. |
consequence-of-errorD17 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. What follows an erroneous contract record or notice is not established We looked and the sources we inspected did not settle it. | Not recorded by the method used for this area |
accountabilityD18 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. No stable answerable party evidenced We looked and the sources we inspected did not settle it. | Not recorded by the method used for this area |
What is each capability evidenced doing?
The mode records that a named subject performs an operation. It does not record what kind of performer that subject is, and several rows disclaim an agentic mechanism in their own limitation.
| Capability | How far it goes | What it does | Human work still needed | What this does not tell you |
|---|---|---|---|---|
Luminance Autonomous Negotiation (formerly Autopilot)C-001 | advises only | "It reads and analyzes the contract, remediates areas of risk, manages negotiation workflows on key collaboration channels, sends revised drafts to counterparties, tracks responses, and reacts in real time to changes made by the counterparty's AI." | NOT STATED on either inspected artifact. No passage says whether a human must sign, approve or execute. Recorded as absence, not inferred. | This row does NOT establish that Luminance cannot perform a binding act. It establishes that no inspected artifact says it does. The words "autonomous" and "100% AI" were refused as evidence of mechanism (operating rule 5). |
Workday Contract Intelligence, powered by Evisort AIC-002 | advises only | "extract and move data from business documents into Workday"; "analyze large volumes of contracts and related documents (like POs, SOWs, and invoices)"; users are "notified of upcoming renewals". | Not stated as a requirement. The evidenced outputs are notifications and extracted data, both of which presuppose a human or system acting on them. | Boundary-calibration case BC-05. "Being notified of a renewal does not renew anything" is the ruling that decides this row. The acquisition event EV-05 remains admissible independently of this outcome (I-08). |
Docusign Navigator — obligation and renewal managementC-003 | advises only | "Surface and track key obligations with automation, maximizing agreement value with less effort and fewer risks."; "Get notified of important milestones, such as renewals, before they happen to stay proactive and avoid expensive errors." | All acting on the surfaced obligation or renewal. The inspected artifact states notification only. | Designated thin-evidence case. The X-6 conditional limb is met on one undated sentence and no more. |
Icertis Vera agents (Composer / Insights / Fulfillment) and Icertis Contract Intelligence for SAPC-004 | the sources do not settle whether this belongs in scope | "create a legal transaction in SAP S/4HANA that can automatically initiate a contract in the Icertis solution"; and separately "Reduce contract drafting times from days to minutes by instantly turning user inputs into review-ready contracts." | "review-ready" states that a review follows. "They run proactively 24/7 to execute multi-step workflows and accelerate strategic outcomes with humans in the loop" — the word EXECUTE here attaches to WORKFLOWS, not to contracts, and is coded accordingly. | This is the only unit among the capabilities examined whose evidenced operation might change the state of an record in scope for the area, and the artifact does not say. It is left unresolved rather than resolved toward either answer. |
SAP Ariba Contracts — intelligent contracting with JouleC-005 | advises only | "Intelligent contracting will use Joule to automatically extract key information, generate summaries, and search historical contracts for discrepancies and compliance issues." | Deciding. The artifact's own framing is that the capability HELPS people decide. | The same artifact's only agent that decides anything is a bid-analysis agent operating on an AWARD, which is excluded by X-1. That exclusion was applied and is recorded here so the reader can see it was tested. |
Adobe Acrobat AI Assistant — contract capabilitiesC-006 | advises only | "automatically recognizes when a document is a contract—including scanned documents"; "Quickly see differences between versions, check for consistency and catch discrepancies". | Signing. The artifact states the product lets users "request e-signatures", which is a request and not a signature. | Included as a deliberate structural contrast: a general document capability reaching INTO the area through X-6's conditional limb, rather than a procurement platform reaching out. |
Agiloft AI-driven Obligation ManagementC-007 | prepares the work, stops before it counts | "automatically analyzes the contract, extracts key obligations, and sends the results directly back into the Agiloft platform"; "enable all extracted obligations to automatically populate a linked set of tables designed for tracking tasks, deadlines, and dependencies"; "sends automated reminders and escalates overdue tasks". | "ready for review, reporting, and follow-up" — review and follow-up remain human. | This is the area's clearest O-5 MIRROR: the obligation tracker writes state into its own tables, and the obligation itself lives in the instrument. Mode is coded operational-preparation rather than advisory because records are written, and participation is still not established because the records written are not the object. |
Sirion agentic CLM platformC-008 | the sources do not settle whether this belongs in scope | Not recorded by the method used for this area | Not recorded by the method used for this area | This row carries NO evidence and makes NO claim about Sirion in either direction. It is recorded so the blocked estate appears in the population rather than vanishing from it (operating rule 8). T-01 does not apply to unresolved rows. |
Two autonomous agents (ClawBank / Shodai) negotiating and executing a Ricardian contract on the Arc NetworkC-009 | the sources do not settle whether this belongs in scope | "They discussed terms. They reached an agreement. They created a Ricardian contract that contained both human-readable legal language and machine-executable instructions." | "No human reviewed the terms. No human approved the transaction. No human signed anything." | Recorded because a nil result on the binding step must be an honest nil. This is the ONE candidate for a machine-performed binding act that the collection surfaced, and it fails the area's own admission rules on three separate grounds. Reporting it and refusing it is the finding; suppressing it would overstate the nil, and admitting it would fill H-05's binding step by analogy. |
Whose systems does this area run on?
What part each system plays was decided by what it does to the area's records, never by what kind of company runs it. Where the sources leave that open the entry says so, because an open question is not a kind of system.
| System | Who runs it | What part it plays | What it does to the official record |
|---|---|---|---|
Docusign eSignature — transaction data and Certificate of Completion (NOT the Docusign company, and NOT the eDocument)C-010 | Docusign, Inc. | authoritative-transaction-rail | holds — the transaction data and Certificate of Completion evidencing the execution act (O-4), held in the Docusign eSignature service; mirrors — the eDocument itself (O-1), which the customer owns and the sender may purge |
Docusign Navigator — agreement repositoryC-011 | Docusign, Inc. | unresolved | holds — stored executed agreements; mirrors — the same agreements as executed in Docusign eSignature; the artifact states they are accessed automatically FROM that service |
Find a Tender Service / central digital platform — the Procurement Act 2023 notice regime (UK7 contract details, UK10 contract change, UK11 contract termination)C-012 | UK Cabinet Office | unresolved | holds — the contract change notice, the contract details notice and the contract termination notice; mirrors — the signature state (UK7 is "Published after a contract has been signed") and the termination state (UK11 is "Published after a contract has ended") |
The published standard contracts for public procurement — Short Form Contract, Mid-Tier Contract, Model Services ContractC-013 | UK Government Commercial Function and Government Legal Department | authoritative-register | holds — the standard contract forms; constructs-for — the parties, who form specific instruments on the published terms |
SAP S/4HANA and SAP Ariba as the systems holding procurement contract stateC-014 | SAP SE | unresolved | creates — a contract is automatically initiated in the Icertis solution from an SAP S/4HANA legal transaction; none-established — whether SAP holds any authoritative contract state of its own is not established by any inspected artifact |
Oracle Fusion Cloud Procurement — Procurement ContractsC-015 | Oracle Corporation | unresolved | none-established |
What may be said from this area, and what may not?
Each one carries how far it is backed and, where it was recorded, the exact stronger sentence that may never be written from it.
In UK public procurement, a party that is not a party to any of the contracts changed what a buyer is entitled to do to a supplier, by revising a published standard contract form.
The strongest thing against it None was found. No inspected artifact states that suppliers or buyers negotiate the standard form's termination clause bilaterally.
What may not be said from this Must never be stated as "institutions control procurement contracts", as a claim about UK contracts generally, or as a claim about any jurisdiction other than the one inspected.
Under the inspected UK guidance, a contracting authority must publish a contract change notice before modifying a public contract, and may not modify it before the end of the standstill period that notice states.
The strongest thing against it The same regime's other two notices cut the other way: UK7 is published after a contract is signed and UK11 after it has ended, so most of the notice regime mirrors states rather than gating them.
What may not be said from this Must never be stated as "publication platforms control contract modification", and must never be stated without the post-cutoff date limitation.
One e-signature operator states that it retains transaction data after a customer's subscription ends and that it cannot delete or export that data, while the signed document itself is customer-owned and may be purged by the sender.
The strongest thing against it The same artifact is its own counterexample on the other object: the eDocument is stated to be customer-owned and purgeable.
What may not be said from this Must never be stated as "the e-signature provider holds the executed contract", which the same artifact contradicts.
No capability in this area's participant population was evidenced, on any inspected artifact, to set, change or complete a procurement contract's signature or execution state.
The strongest thing against it C-009 — two autonomous agents reported to have executed a Ricardian contract with no human signature. It is refused on three independent grounds: the artifact postdates the window, no primary artifact was retrieved, and no inspected passage places it on a procurement contract object.
What may not be said from this Must never be stated as "no AI can sign a contract", "machines do not execute contracts", or as any claim about capabilities that were not inspected.
The one inspected artifact describing a procurement contract object being brought into existence by an automated act does not state what object state that act creates.
The strongest thing against it None was found. No other inspected artifact in the area describes an automated act creating a contract object at all.
What may not be said from this Must never be stated as "SAP and Icertis create contracts automatically", nor as "they do not".
Across the participant units inspected in this area, evidenced operations on obligations and renewals produce representations — extractions, tracking tables, notifications and escalations — and no inspected passage states that the representation's state changes the obligation or the renewal.
The strongest thing against it Agiloft writes obligation records automatically into linked tables, which is closer to an operation on state than notification is; the artifact still does not say the table's state discharges anything.
What may not be said from this Must never be stated as a rate, a share, a market characterisation, or a claim about obligation management products generally.
An agent named the Fulfillment Agent is evidenced by its own vendor to track commitments.
The strongest thing against it None was found. The same artifact's other named agents — Composer, Insights — describe operations consistent with their names.
What may not be said from this Must never be stated as a claim that the vendor misrepresents its product, and must never be supported by citing any other area's instances.
Whether a renewal is an act by a party or a state change that occurs because nobody acted is not established by any artifact inspected in this area.
The strongest thing against it None. No inspected artifact takes either side.
What may not be said from this Must never be filled by reasoning about how auto-renewal clauses generally work.
Nine distinct artifacts inspected in this area carry no page-visible date, and eight of the nine are vendor-operated; all twelve admitted events rest on artifacts that do carry page-visible dates, and nine of those twelve are vendor-published.
The strongest thing against it Nine of the twelve admitted events are vendor-published and dated, which cuts directly against reading this as vendors not dating their artifacts. The asymmetry is between ESTATES, not between publishers.
What may not be said from this Must never be stated as "vendors do not date their artifacts", nor offered as support for any other area's finding.
No causal link is established between any institutional event in this area and any platform's behaviour.
The strongest thing against it None sought; none would be admissible under this design.
What may not be said from this Must never be inverted into "institutional change does not affect platforms".
No artifact inspected in this area names a party answerable for a consequential contract-lifecycle object who is neither the actor, nor the authority holder, nor the actor, system or institution that makes the outcome official, nor the holder of the object.
The strongest thing against it The closest inspected case is the UK standard-contract publisher, which changes a termination entitlement without being a party — but it is the HOLDER of the form, so it fails the test's first condition rather than meeting it.
What may not be said from this Must never be stated as evidence that answerability is singular, nor as evidence against the field. It is an absence.
Twelve retrieval routes in this area returned no usable artifact, across twelve distinct hosts, of which nine are vendor-operated and three are institutional.
The strongest thing against it None applicable.
What may not be said from this Must never be stated as deliberate concealment by any named party.
What dated acts touch this area's records?
A list, in date order. It is not a timeline and carries no rate: the collection capped each publisher, so this is a floor on what was retrievable rather than a count of what occurred.
| Date | Kind of act | Consequence recorded | Source |
|---|---|---|---|
2024-04-11 day precision | named deployment | none | source |
2024-04-17 day precision | transaction infrastructure access | none | source |
2024-05-24 day precision | institutional rule change | The guidance suite that operates the statutory modification and termination regime is placed in the public domain, naming Contract Modifications and Contract Termination as separate published guidance documents. | source |
2024-09-10 day precision | transaction infrastructure access | none | source |
2024-09-17 day precision | ownership change | none | source |
2025-02-04 day precision | named deployment | none | source |
2025-02-21 day precision | institutional rule change | A termination entitlement is added to the published standard form, and termination clauses grounded in the superseded Public Contracts Regulations are removed. | source |
2025-03-27 day precision | named deployment | none | source |
2025-04 month precision | institutional rule change | The institution changes which permissible contract FORM may be used for which procurement, without touching any individual instrument. | source |
2025-09-10 day precision | named deployment | none | source |
2025-10-08 day precision | workflow expansion | none | source |
2025-12-08 day precision | named deployment | none | source |
Where did the search stop, and why?
A route that returned nothing establishes that the route returned nothing. A missing capture is a property of the archive, never a property of the world.
| Source checked | How it failed | What was recorded |
|---|---|---|
| Docusign eSignature envelope-status documentation | page returned a header and a CSS error with no document body (client-side rendering) | Not recorded by the method used for this area |
| Docusign eSignature REST API Envelopes resource | page returned a title only with no document body (client-side rendering) | Not recorded by the method used for this area |
| Adobe Acrobat Sign audit report configuration and content | HTTP timeout after 60s on two separate paths | Not recorded by the method used for this area |
| Sirion agentic CLM platform and next-generation platform press release | HTTP 403 Forbidden on two separate paths | Not recorded by the method used for this area |
| SAP Ariba Contracts product page | HTTP 403 Forbidden | Not recorded by the method used for this area |
| Contract Management with SAP Ariba Contracts (4AZ) | page returned a title only with no document body | Not recorded by the method used for this area |
| Oracle Procurement Contracts Cloud datasheet (PDF) | HTTP 403 Forbidden | Not recorded by the method used for this area |
| Oracle Fusion Cloud Procurement 25B release-readiness and 25b procurement documentation | retrieved and inspected; contained no procurement-contract content and no page-visible date | Not recorded by the method used for this area |
| Coupa newsroom release on agentic AI capabilities | HTTP 403 Forbidden; the syndicated copy on www.prnewswire.com returned ECONNRESET | Not recorded by the method used for this area |
| Procurement Act 2023 sections on modifying and terminating public contracts | HTTP 504 Gateway Timeout on two separate paths | Not recorded by the method used for this area |
| Procurement Act 2023 guidance: contract modifications | HTTP 403 Forbidden | Not recorded by the method used for this area |
| Directive 2014/24/EU Article 72, modification of contracts during their term | retrieved but TRUNCATED before Article 72's publication requirement; the summarising retrieval returned a paraphrase which was REFUSED rather than quoted | Not recorded by the method used for this area |