CTR-PLM · version 1
Product Lifecycle Management — Part revisions
Export control is the open question: a part revision carrying a controlled classification cannot cross a residency boundary, and the contract has to say how that is enforced.
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
4 fields · 2 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 |
|---|---|---|---|---|---|---|
| Part number | item_id | part.ref | string(30) | keyinternal | Never checked | Unique within the product line. |
| Revision | item_revision_id | part.revision | string(6) | keyinternal | Never checked | Alphabetic, monotonic. |
| Release status | release_status | part.state | enum(5) | internal | Never checked | Five declared states. |
| Export classification | ecc_number | part.exportClass | string(12) | nullableinternal | Never checked | Null is admitted but blocks cross-border replication until classified. This rule is what the security review is examining. |
What has passed the staging boundary against this contract
1 batch · 1,940 arrived · 1,882 admitted · 58 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0027 | Aug 18, 02:00 | 1,940 | 1,882 | 58 | 0 | Partly admitted | 1,882 admitted · 58 quarantined · 0 rejected outright. |
Rejects raised against these batches
1 reason covering 58 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 Product 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 |
|---|---|---|---|---|
| Research lineage confidence | Research and development cockpit | contributing | Mark it stale | Part and program structure gives the confidence figure something to hang on. |
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.