A record is created around the exact governed state.
CICP separates the thing being executed from the record that proves what was approved and produced.
Bind the contract
Record the FieldObject identity, version, contract hash and execution host before release.
Bind approval
Capture the human approval statement and approval timestamp against the exact contract digest.
Bind the result
Attach the artifact or effect digest and evidence references after the governed execution completes.
Lifecycle
Draft → Review → Approved. Approved records are immutable. Revocation or supersession creates explicit lifecycle events rather than rewriting history.
What CICP does not do
A CICP record does not automatically certify the factual truth of an input, a model answer, a third-party source, or the legality of an action. It records the governed contract, approvals and evidence lineage so those claims can be inspected.