CTR-FPA · version 2
Planning and Consolidation — Plan version lines
The baseline surface reads from this contract, which is why baseline immutability depends on the source keeping versions immutable.
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 · 3 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 |
|---|---|---|---|---|---|---|
| Version id | version.id | planLine.versionRef | string(24) | keyinternal | In contract | Published versions only. The contract relies on source-side immutability and names that reliance. |
| Account id | account.id | planLine.glAccount | string(10) | keyinternal | In contract | Must resolve to a GL account. |
| Period id | period.id | planLine.period | string(7) | keyinternal | In contract | Year and month. A quarter value quarantines because it changes the grain. |
| Planned amount | value | planLine.amount | decimal(15,2) | internal | In contract | Signed. |
| Driver | driver.name | planLine.driver | string(60) | nullableinternal | In contract | Null on directly entered lines. |
What has passed the staging boundary against this contract
1 batch · 2,210 arrived · 2,114 admitted · 96 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0032 | Aug 17, 10:00 | 2,210 | 2,114 | 96 | 0 | Partly admitted | 2,114 admitted · 96 quarantined · 0 rejected outright. |
Rejects raised against these batches
1 reason covering 96 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 Planning and Consolidation.
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 18,000 records 20 days ago, which is 75% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.