CTR-ELN · version 1
Research Notebook and Experiment Data — Experiment records
The second of the two systems that are not connected at all.
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
3 fields · 1 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 |
|---|---|---|---|---|---|---|
| Entry id | entry.id | experiment.ref | string(24) | keyinternal | Never checked | Unique. |
| Project id | project.id | experiment.projectRef | string(24) | internal | Never checked | Must resolve to a project. |
| Author | entry.creator | experiment.authorHash | string(64) | personalrestricted | Never checked | Pseudonymized. |
What has passed the staging boundary against this contract
No batch has been presented against this contract in the recorded window.
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 Research Notebook and Experiment Data. 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 | primary | Suppress the figure | The notebook is not connected. Every research lineage figure on this estate is therefore modeled, and the dependency says so at the point the number is shown. |
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.