Evidence missing or contradictory
The requested action or interpretation lacks stable source support.
Safe refusal and blocked growth
No-Op Receipts
Record why action, claim widening, memory use, endpoint access, structural growth, or publication was not justified—and what evidence could reopen review.
Orientation
Doing nothing can be justified work, but silence is not a receipt.
A no-op receipt identifies the request, affected node, evidence reviewed, blocking constraint, decision owner, safe alternative, and reconsideration trigger. It lets a reviewer distinguish disciplined restraint from hidden refusal or abandoned responsibility.
No-op does not erase legal duties, emergency obligations, accessibility repair, or required human review. It must not be used to conceal discrimination, avoid accountability, or turn uncertainty into permanent denial.
No-op decision flow
- Proposed action Name the requested expansion or consequential change.
- Evidence test Is source support specific and sufficient?
- Authority test Is the actor authorized for this purpose and scope?
- Viability test Can maintenance, review, and repair costs be carried?
- No-op receipt Record the gap, preserved state, and safe alternative.
- Reconsideration State what new evidence or human review could reopen the decision.
Read the diagram as text
- Proposed action: Name the requested expansion or consequential change.
- Evidence test: Is source support specific and sufficient?
- Authority test: Is the actor authorized for this purpose and scope?
- Viability test: Can maintenance, review, and repair costs be carried?
- No-op receipt: Record the gap, preserved state, and safe alternative.
- Reconsideration: State what new evidence or human review could reopen the decision.
Triggers
Common reasons to preserve state and request review.
Authority ambiguous
The actor, source domain, endpoint permission, delegation, or reviewer authority is unclear.
Consent or memory boundary unresolved
The operation would use data, memory, identity, or a file outside the disclosed scope.
Cost or maintenance burden unjustified
The proposal creates ongoing work without enough benefit, ownership, or retirement plan.
Review capacity unavailable
A material consequence cannot receive the required human or bounded-system review.
Claim would widen beyond source support
The requested wording implies certification, proof, legal authority, runtime control, or merged ecosystem authority.
Required trace
A strong no-op says what would change the result.
- Request, requester, affected node, and requested authority.
- Evidence reviewed, missing evidence, and source domains.
- Blocking constraint and why narrower alternatives were insufficient.
- Immediate safe alternative or preservation action.
- Human-review route, appeal path, and response owner.
- Reconsideration trigger, expiry, or next review UTC.
Counterpart set
Fictional example
Conflicting release metadata blocks machine-summary widening.
An AI reader finds a current homepage and a stale root manifest that report different names and versions. It records the conflicting URLs, preserves the narrow statement that the sources disagree, avoids merging the identities, and routes the conflict to human review. The reconsideration trigger is a consistent deployment manifest, vnwo.json, llms.txt, and page metadata.