CONTINUITY & HISTORY

Take another direction. Keep the original.

More matches. Another fact. A fresh check. A better question. One piece of work should give the next one somewhere to begin.

Recorded in the Specstream frontend · Example data

Follow the thread.

Keep the intent.

Save the spec behind the work. Give it a name, retain the requirements, and return to the question itself.

Make a revision.

Refine the conditions or change the facts you want. Preserve the parent revision so the new direction remains understandable.

See how the work connects.

Explore specs, collections, requests, schedules, and fixed deliveries together. A relationship explains where the work came from.

Find more.

Continue discovery from retained context instead of rebuilding the request from memory.

Know more.

Research new fields about the same matches. Add information while keeping earlier observations inspectable.

Check again.

Refresh existing facts and qualification. Changed, unresolved, unavailable, and not reached remain distinct outcomes.

Does a new revision overwrite the previous one?

No. Revisions retain their ancestry, and fixed deliveries keep their original output.

Does saving a revision start new work?

No. Editing and saving intent are separate from authorizing execution. New acquisition follows its own scope and quote.