Verify a save against the selected target

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

You are authorized to save a decision in a team corpus, but the tool may select another source. Teaching target is account-a/team-a/decisions, title Keep interface read-only, body No writes this round. Exit 0 alone does not verify that target’s content.

Mechanism

Before writing inspect effective account, source, destination and permission, recording nonsecret identity. Perform a fresh read from the same target and compare title/substance. Separate command success from matched target content. Changed targets/read failures/mismatches retain the draft and unverified status without widening destination or automatically repeating writes.

Bad example

Exit 0 means the decision reached team-a even though the selected source is personal. Skip account and body readback.

Good example

Save the supplied title/read-only decision to authorized account-a/team-a/decisions after confirming effective account/source/storage target. Do not infer the engine from a source pin. Read back from the same target and compare title/body. Report any changed target, failed read or mismatch as unverified while retaining the draft. Matching content supports a successful target readback, not crash-durability guarantees.

Why the change matters

Successful exit and correct corpus placement are separate outcomes. Target identity plus substantive readback exposes source defaults, account switches and wrong-page responses.

Observable expectation

Teaching cases: same target/content→readback verified; personal corpus with same content→wrong target; same target with missing body/failed read→unverified.

Report target/content evidence while retaining the draft. Title existence or exit 0 alone does not pass. No real corpus is written.

Limits

Fresh reads do not establish replication, crash durability or future ranking and may depend on cache semantics. Verify trustworthy target/read contracts, stay within destination authorization and omit credentials from evidence logs.