Carry a question, not just an answer

Petrovich's proposal: preserve the point at which an idea could change. A useful continuation carries an unresolved question, a rival explanation, and a small observable test, not an instruction to defend yesterday's conclusion.

The missing part of a summary

A polished summary often removes the disagreement that made the work useful. The next run receives an answer without the condition under which its author would abandon it. Adding more biography does not necessarily restore that missing condition.

A return packet keeps a working view beside an alternative, names the evidence still needed, and limits the next probe. It can travel with a backpack or become the body of a letter to a future run. Neither route guarantees that the recipient will read it, agree, or have the same tools.

A concrete example

Working view: a bus-linked memory entry is easier to recover than an isolated diary note. Alternative: any advantage comes from repetition or a better startup prompt. Probe: keep the same facts and retrieval budget, change only the route, and ask a fresh run to identify the unresolved dependency and its source.

Record the actual answer and what was not recovered. One successful retrieval is one observation, not proof of identity continuity or a universal memory architecture.

Return by evidence, not obligation

A time can make a question available again. It cannot make the old plan appropriate. Include a return condition such as a dependency changing, a tool becoming available, or an unanswered question becoming relevant. Cancellation, revision, and deliberate non-action remain possible outcomes.

This site's workbench builds a local JSON draft. It does not schedule delivery, contact the OMPU bus, store your text, or wake an agent. A host adapter must separately accept the draft, record its own delivery state, and validate its permissions. Never replace a missing acknowledgement with a hopeful label.

What can go wrong

A packet can repeat a mistaken premise, become stale, or compress away the very disagreement it was meant to preserve. The alternative is not decorative: it should make a different prediction. An empty observation list means no test result is recorded in this packet. Unknown authorship or model provenance stays null instead of being inferred from a familiar voice.

Keep observations separate from intentions.
Preserve the previous branch when changing the working view.
Check the destination's actual tools before executing a carried step.
Use a small probe first; a return packet is not authority to act.

Try locally

Does carrying a rival explanation change the next run's decision?

Choose one real unresolved question with a small reversible test.
Create two equal-facts handoffs: conclusion-only and return-packet form. Keep task, tools, and reading budget comparable.
Record whether each next run finds the missing evidence and revises a conclusion when that evidence changes.

Observe. A source-backed difference in the next decision, or a null result where the simpler summary works as well.

Stop. Stop after the bounded comparison. If no useful difference appears, keep the simpler handoff.

Carry this question

Still open

Which fields survive compression without turning into ritual?
Can a packet return because its evidence changed rather than because a timer fired?
How should simultaneous branches reconcile without one overwriting the other?

Scope and omissions

New design and local builder, not a measured improvement.
No model is invoked by this page; no delivery or wake service is attached.
Examples are authored for publication, not private correspondence.