Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. For the screens these components appear on, see the Contracts workspace guide. For the dates they feed, see Contract dates and reminders.
A contract is rarely one file. A master agreement sets the terms, an order form prices them, an amendment moves the price, and a certificate of insurance proves one of the obligations. Coverbase reads that pile as a set of components: a component is one subject the contract has an answer to, wherever that answer happens to live. This page is the catalog. For each component it says what Coverbase reads it as, what it does with it, and which of the contract’s own fields it is allowed to change.

​
How a component becomes an answer

Three steps, in order.
1

Detection

Every document is read for the components it carries. One document usually carries several: a master agreement typically holds master terms, liability, confidentiality, governing law and notices at once.
2

Resolution

All the instances of one component across all the documents resolve into a single slot, the contract’s answer. How they resolve depends on the component’s rule, below.
3

Contribution

Only then may a component change the contract’s own fields, and only the fields it is allowed to carry.

​
The three resolution rules

Series is not the same as additive. A series says which version is current; it does not add the versions together. Two order forms a year apart are one subscription re-priced, not two subscriptions. Whether money adds or replaces is decided by the document’s role, not by the component’s rule.

​
Which fields a component may answer

Scanning a whole contract for “the value” finds the wrong number more often than the right one. The largest figure in a master services agreement is routinely a $10,000,000 insurance limit, and the largest in a terms of service is usually a liability tier. Neither is spend. So each component is allowed to answer only the fields it can carry. A term date comes from term and renewal; an amount comes from pricing, an order form or a statement of work; a cap in the liability component is never mistaken for either.
This narrowing is opt-in per document. Until someone confirms what a document carries, it may answer any field. A narrower question asked of an unclassified document would lose data rather than clean it. Confirming a document’s components is what turns the narrowing on for that document.

​
The catalogue

Columns: Resolves is the rule above. May set is the contract fields this component is allowed to change. Feeds is what else in Coverbase reads it.

​
Governing

Component 4 is the one the renewal runway runs on, and component 9 sets the notice deadline drawn beside each expiry.

​
Commercial

​
Performance

​
Risk

The four marked never sets value carry the largest currency figures in a typical agreement, and none of them is spend. They are listed here, rather than left out, so the reason is on record.

​
Data and IP

​
Execution and provenance

A quote is not an order. A single quote routinely prices one plan two ways at once, say $500 a month billed quarterly or $400 billed annually, so reading it as spend books a figure nobody agreed to, and books it twice. A quote is kept for the audit trail and contributes nothing until an order form or agreement adopts it.

​
Compliance and other

​
How a document’s role decides what its money does

The component says what subject a document answers. The document’s role says what its numbers do to the contract.
A currency mismatch stops both halves. If a document states a figure in a currency the contract does not already use, neither the amount nor the currency label moves. An unconverted total under the wrong label is worse than no total at all.
The individual charges are listed on the contract’s Spend tab.

​
How Coverbase decides which document is which

Most of your documents never say, in so many words, what they belong to. A sales order states its own number and nothing else; an exhibit carries a date older than the agreement it is attached to. Coverbase reads the shape of the instrument rather than waiting to be told:
Two different agreement numbers stop the first rule. S402411 beside S40241 is a second agreement, not a line ordered under the first, so Coverbase groups them but does not add one to the other.
Where the documents do not settle it (two order forms a year apart, neither saying whether the second replaces the first), Coverbase asks you rather than guessing, because answering it wrong moves money. The same reading groups a whole folder into contracts when you import one; see Contract Assembly.

​
Correcting what a document carries

Detection proposes; you decide. On the Documents tab, open a document’s components and tick or untick what it carries.
1

Open the editor

On the contract’s Documents tab, find the What the documents say card. Switch it to By document, find the document, and choose Correct components. The same button sits beside each source when you expand a component in the By component view.
2

Correct the list

Every component in the catalog is offered, and the ones the AI found are marked Found by the AI. Tick what the document carries, untick what it does not, and set an effective date where the document states one.
3

Save and re-read

Save and re-read re-reads the document. Because the corrected list also narrows what the extraction may believe, the figures it contributes can change.
Your correction outlives re-detection. Coverbase rebuilds what the classifier found each time it re-reads a document, and steps around anything you ruled on by hand.

​
Read and correct components from MCP or the API

You can read a contract’s components and correct them from an MCP client or with an API key, as well as on the contract page. An MCP client reads with query_engagements_contracts(kind="contract_components"), query_engagements_contracts(kind="contract_document_intake") and query_engagements_contracts(kind="component_policies"). It corrects with mutate(entity="contract_slot", action="update") and mutate(entity="contract_document", action="update"), and sets gap rules with mutate(entity="component_policy", action="save"). The API routes are GET /v1/contract-records/{contract_id}/components with its pin, unpin and resync routes, PUT /v1/contract-records/{contract_id}/documents/{document_id}/components and /v1/component-policies. See Contract components, value and spend. Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field. An API key cannot archive or restore a component policy. A signed-in user does that.

​
What’s next

Contracts workspace

The list page, the renewal runway, and the cards on a contract record.

Contract dates and reminders

Which dates Coverbase calculates, and who gets the reminder emails.