Review and hand off source material

Carry reviewed material from one product to another without losing its source or confusing one product's success with another's. Use the source product's completed result, not an unfinished operation or an unreviewed response.

Before you start

Use material you are authorized to read and share. Zilch extraction requires active paid Zilch access. Confirm the destination project or note and preserve any draft or existing project changes.

From a public page to a note

1. Extract the public page with paid Zilch access.
2. Inspect the completed document's source URL, relevant passage, warnings and truncation.
3. Copy the selected material into a note with its title and source URL.
4. Save and reveal the Markdown note in Ouros X, then read the saved file.

This is an explicit copy-and-save handoff. For a complete walkthrough, use keep a sourced note. There is no implied background synchronization between Zilch and Notes.

From reviewed material to project work

Select the relevant, non-sensitive passage before supplying it to Agent RX in the intended project. State the task and boundaries separately from the source text. Review tool activity and the resulting diff; the note or extraction grants no tool authority. Follow move material into a coding task.

Keep operation identity

Use this personal worksheet when an existing operation or run needs follow-up. It is not a service configuration or API request schema. Replace the placeholders and omit fields that do not apply; keep local paths and identifiers private when sensitive, and never add tokens.

service: SERVICE_NAME
operation_id: OPERATION_ID
idempotency_key: ORIGINAL_KEY
request_body_file: path/to/original-request.json
version: EXACT_VERSION_IF_APPLICABLE
last_observed_state: STATE

From repeated work to loop review

Use the repeated task's actual inputs and expected result to inform a brief. For an existing hosted candidate, review the exact version. A saved note, agent conversation or exported draft does not automatically become an approved or scheduled loop. Keep the version and run identity for any separately chosen execution.

Check each result separately

• Extraction: inspect the completed operation, URL, warnings and truncation.
• Note: reveal the saved Markdown file and compare the text.
• Coding task: inspect the intended changes and relevant check results.
• Loop: inspect the exact run and its output, not only the reviewed version.

If a downstream step fails, retain the already verified source and the failing step's identity. Do not repeat the entire chain without checking for existing work.