CTR-CLM · version 2
Contract Lifecycle Management — Contracts
The clause-level obligations behind the legal cockpit and the works-council commitment tracker.
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 · 1 key · 0 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 |
|---|---|---|---|---|---|---|
| Contract id | contractId | contract.ref | guid | keyinternal | In contract | Source-generated guid. |
| Counterparty | party.name | contract.counterparty | string(200) | internal | In contract | Matched against the supplier master. An unmatched counterparty is admitted but flagged, never silently created. |
| Total value | contract.value | contract.value | decimal(15,2) | nullableinternal | In contract | Null on framework agreements, which is legitimate and excluded from value roll-ups rather than treated as zero. |
| Renewal notice period | contract.noticePeriod | contract.noticeDays | integer | internal | Type changed Mixed units in the last sample: 143 of 600 records carried a value that is only sensible as months. All 143 are held. | Days. A months value must be converted at the source, not guessed here. |
| Governing law | contract.governingLaw | contract.jurisdiction | string(40) | internal | In contract | Must resolve to a declared jurisdiction, because the residency overlay depends on it. |
What has passed the staging boundary against this contract
2 batches · 3,008 arrived · 2,737 admitted · 271 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0018 | Aug 18, 07:00 | 1,520 | 1,377 | 143 | 0 | Partly admitted | 1,377 admitted · 143 quarantined · 0 rejected outright. |
| STG-0019 | Aug 18, 05:00 | 1,488 | 1,360 | 128 | 0 | Partly admitted | 1,360 admitted · 128 quarantined · 0 rejected outright. |
Rejects raised against these batches
2 reasons covering 271 records. Each one names a field, what was observed and what the contract expected.
Replay windows
1 window recorded against this contract.
Write-back routes into this system
1 route designed against Contract Lifecycle Management.
What goes stale when this feed does
1 asserted figure depends on Contract Lifecycle 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 | primary | Suppress the figure | Contract value is a sum over the contract master. The feed has drifted on notice period, which is a separate problem from staleness. |
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.
The last validation read 600 records 27 days ago, which is 67% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.