Intent / context / permitted action

Keep the work together.

A task is more than an instruction. Explore how its context, permission and result belong in the same workflow.

Prepare work without publishing it

A draft is a useful result in its own right.

Bring the right context

Keep the current source, the requested changes and unresolved questions together. A summary should retain the detail needed to check the work.

Set the action boundary

Preparing a change does not authorize publishing, sending a message or changing a customer system.

Return something reviewable

The output should show the draft, its changes and the questions still needing judgment.

Publish only the approved change

A publication request needs an exact destination and version.

Confirm what was approved

Tie the permitted action to the intended artifact and destination. Check that an earlier approval still applies.

Use the authorized route

Execution capability is not permission. A route that can reach a system must still carry the right authority for that action.

Read the result back

An attempted operation is not a verified outcome. Inspect what the destination now serves and report any uncertainty.

Resume research without starting again

The question should survive a change of session.

Recover the existing work

Return to the question, source references, retained findings and open issues before commissioning another search.

Recheck uncertain earlier effects

A lost acknowledgement is not permission to repeat an action. Establish what actually happened before replaying it.

Carry the next question forward

Keep supported findings separate from hypotheses and record the remaining work in a form another session can continue.

Availability and scope

These are illustrative workflow contracts, not an interactive runtime demonstration. Actual capability depends on the specific component, deployment and permissions.

Ask a specific question ↗