Answer from the documentation, never from memory

<!-- sflow-copilot-pause -->

Before any boundary lookup or SFlow action, run singularity-flow pause status --json and follow its data.agentInstruction. If data.paused, answer as native Copilot, only offer /sf-pause off and never resume implicitly.

<!-- sflow-output-contract: concise-relay -->

Output contract: Relay requested CLI fields or output faithfully; preserve warnings/errors and only the explanations required below. Summarize artifacts with verified Markdown-preview links; never paste document bodies, code or diffs into Copilot. For code, list touched paths and observed added/deleted/created line counts; unavailable stays unavailable. Use existing evidence, not extra calls solely for display. Summaries, links and opened previews are not human review or approval. For every next action, honor returned commandGuidance in order: Copilot, Shell, VS Code (model-free) using modelFreeCommand; if absent, say "not available for this action". Missing Copilot: "no verified equivalent". Never invent routes.

<!-- sflow-execution-boundary -->

Boundary: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository. Use exact CLI-returned paths. repositoryPath is command cwd, not a prefix for absolute file paths. Never rebase paths or strip .git/worktrees. Issued private/external files are exact exceptions to repository confinement, not wider read/write permission; writes still need authorization. Resolve relative paths only against their declared base. On failure, preserve the path and error; never search or recreate it.

1. Pass the exact question or topic through the model-free resolver: run singularity-flow explain '$ARGUMENTS' --json, one single-quoted argument with each inner ' as '\'' (PowerShell '') so nothing expands. With no argument, run singularity-flow explain --json for the topic catalog. Do not map the question to a topic from model memory.
2. Read the served bytes from data.served.text and preserve data.helpIntent, provenance, and warnings.
3. Answer using that content. The substance of the reply must come from the served bytes — if the topic does not say it, do not say it.
4. End with the citation from data.citation, verbatim. It names the topic id, its version, and the docs commit.
5. If explain refuses with docs.topic-not-found, say so and offer the nearest topic ids it returned. Do not answer the question from memory instead — a fluent wrong answer about governance is worse than none.
6. If the question is ambiguous between topics, present the returned choices. Do not pick one or blend their answers.
7. For "what should I do here", "should I escalate", or any decision, do not answer. Point to singularity-flow nextsteps for the deterministic action set, and to the human approval authorities the pinned configuration names.
8. When the reader wants repository context, first run singularity-flow workspace current --json. Only when it returns repositoryPath, use that exact cwd for singularity-flow explain <topic> --here; label the cited concept and revision-bound situation separately.
9. Do not generate, submit, approve, reject, upload, commit, or push anything.