Developer docs · In-source foundation
Make every decision inspectable.
Validation is useful only when the result can be connected to the exact input, revision, and check set that produced it.
Scope. The source models deterministic correction evidence in a private synthetic workflow. Evidence records do not prove carrier execution, tracking, delivery, notification, or production customer impact.
Evidence record
| Element | Purpose | Review question |
|---|---|---|
| Source identity | Connect the held record to one immutable creation input. | Are we validating the intended record? |
| Revision | Identify the exact version reviewed by the operator. | Has accepted state changed since review began? |
| Fingerprint | Bind evidence to the material correction input. | Does this result belong to the current proposal? |
| Check results | Record deterministic passes and actionable failures. | Which condition allowed or stopped progression? |
| Actor and decision | Attribute approval or rejection to authorised context. | Who accepted the evidence, and under which scope? |
| Operation link | Connect local release to the evidence it relied on. | Can the final local decision be reconstructed? |
Freshness algorithm
- Read the canonical record and current revision.
- Calculate validation against that exact revision and material correction input.
- Persist the attempt as evidence; do not replace history with a single boolean.
- Before approval or local release, confirm the revision and fingerprint still match.
- If either changed, mark prior evidence stale and require validation again.
Interpreting results
| Result | Meaning | Action |
|---|---|---|
| Passed and current | The recorded checks passed for the active revision. | Continue to any required local approval. |
| Failed | At least one deterministic check stopped progression. | Keep the order held and correct the named issue. |
| Stale | The evidence belongs to an older revision or input. | Re-read state and validate again. |
| Unavailable | The validation boundary cannot produce trustworthy evidence. | Fail closed; do not infer a pass. |
Data handling
Minimise retained values, avoid credentials and raw provider payloads, and use synthetic or irreversibly redacted fixtures during evaluation. Operator-facing explanations should expose the reason and safe next action without leaking inaccessible records.