Signed source
Separate the original evidence from its use.
Source record
The accepted source preserves the signed payload and its validation context.
Assignment
An assignment connects evidence to a project or contribution without changing the original source.
Assessment
Findings and policy decisions refer to the relevant evidence, rule and version.
Publication
A selected public view exposes the permitted result and current status.
Development event contract
Validate the signature and event order.
The simulator ingestion contract recomputes the canonical hash, checks the paired device signature, rejects duplicate hashes and compares continuity with the last accepted event.
Conceptual validation
canonical payload -> SHA-256 eventHash
eventHash + paired public key -> Ed25519 signature check
previousEventHash -> compare with latest accepted event
duplicate eventHash -> reject replay
accepted result: signed simulator metadata with validated continuityCorrection history
Make corrections visible and attributable.
A mistaken assignment or finding needs a recorded correction. Preserve the source, identify the changed decision and update the consequences that depend on it. A corrected restriction requires a fresh publication review.
Keep these relationships intact
- Source record and its original validation
- Project and selected output version
- Finding, episode and applicable policy
- Responsible account and review decision
- Prior publication and current eligibility
- Correction reason and resulting assessment
Public interpretation
Explain the result the record actually carries.
A valid signature establishes the integrity and source of a payload. Human creation verification also considers coverage, detection, declarations and review. External anchoring is not required to explain those separate checks.