CTR-DMS · version 1
Document and Matter Management — Matter documents
Privilege is the blocker. A document management contract cannot be ratified until counsel has ruled on which matters an agent may see at all, and that ruling has not been asked for.
What the contract says
These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.
Review state
Neither review is performed by the team that wrote the contract.
Validation and drift
Drift is only detectable on a contract that has been read against a sample.
The field list
5 fields · 2 key · 1 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.
| Field | Source | Target | Type | Flags | Drift | Validation |
|---|---|---|---|---|---|---|
| Document id | docId | document.ref | string(20) | keyinternal | Never checked | Unique within the library. |
| Version | version | document.version | integer | keyinternal | Never checked | Monotonic. |
| Matter id | matterId | document.matterRef | string(20) | internal | Never checked | Must resolve to a matter. |
| Privilege flag | privileged | document.privileged | boolean | internal | Never checked | A true value excludes the document from every agent-readable surface. The contract cannot be ratified until counsel confirms the flag is reliable. |
| Author | author | document.authorHash | string(64) | personalrestricted | Never checked | Pseudonymized. |
What has passed the staging boundary against this contract
1 batch · 880 arrived · 0 admitted · 880 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0020 | Aug 17, 19:00 | 880 | 0 | 880 | 0 | Nothing admitted | No record cleared the gate. 880 are in quarantine and 0 were rejected outright. |
Rejects raised against these batches
1 reason covering 880 records. Each one names a field, what was observed and what the contract expected.
Replay windows
No replay has been requested against this contract.
Write-back routes into this system
No write-back route is designed into this system.
What goes stale when this feed does
1 asserted figure depends on Document and Matter Management. The rule on each row is what the surface does when the feed misses its commitment.
| Figure | Where it is shown | Role | On stale | Note |
|---|---|---|---|---|
| Contract value under management | Legal cockpit | contributing | Mark it stale | Executed documents confirm the value. This feed is outside its freshness commitment. |
A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.
This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.