# Local files, hosted processing and model requests

Identify where an action reads data, where it processes that data and what result you can inspect. Local storage, a hosted operation and a model request are different boundaries even when they begin in the same interface.

## Follow the data path

| Action | Boundary to review | Observable check |
| --- | --- | --- |
| Save an Ouros X note | Local Markdown destination; any separate folder sync service | Reveal the saved file and read its contents. |
| Extract a public page with Zilch | Submitted public URL and hosted extraction; active paid Zilch access | Inspect the completed operation, final URL, warnings and truncation. |
| Submit an agent task | Selected project context, provider configuration and advertised tools | Inspect tool activity, changed files and relevant check results. |
| Review or run a hosted loop | Exact version, inputs, consent and separately chosen execution | Distinguish version approval from a run and inspect that run's output. |

Saving a note does not require a model request. Putting a note in a synced folder can involve another service; local file format alone is not a guarantee that data never leaves the device. A file-search scope does not limit arbitrary tool execution.

## Separate source text from instructions

Before copying a passage into an agent request, remove unnecessary private details and identify its origin. Keep your task outside the quoted source. Page text can contain misleading instructions; copying it does not make it trusted.

[OWASP's prompt-injection guidance](https://cheatsheetseries.owasp.org/cheatsheets/LLM_Prompt_Injection_Prevention_Cheat_Sheet.html) explains why external content needs separate treatment. A task brief is useful communication, not a sandbox or a complete protection against hostile input.

For a coding handoff, use the [bounded task brief](/docs/workflows/move-reviewed-material-into-a-coding-task#write-the-task-separately). When recording research, this attribution template helps distinguish the original source from your own synthesis. Replace the instructional fields with what you actually checked; it is not evidence that an example ran.

```markdown
## Sources and method

- Primary source: [CommonMark reference](https://commonmark.org/help/).
- Method: source-based synthesis with an original worked example.
- What we checked: list the source passages and any executed example.
- Limits: identify what was not tested.

This article shares what we learned; it is not the source publisher’s official documentation.
```

Attribution does not grant redistribution rights. Link to the original and quote only what you need rather than copying a whole source.

## Decide before submitting

Check the intended input, destination and permitted action. If you cannot identify the data path or access requirement, preserve your draft and stop before submitting it. Read the service's notices and consent for retention and legal terms; this conceptual map supplies no universal security or retention guarantee.

Continue with [privacy and permissions](/docs/shared/privacy) or [reviewed handoffs](/docs/workflows/handoffs).