us-ingestlisted

# us-ingest — capture and validate the source Follow the shared contract in `../README.md`. Everything downstream treats `00-source.md` as *the requirement*. That is what makes this step worth its rules: a capture that quietly gained content nobody designated produces a test book about a specification that does not exist. ## Steps 1. **Identify the source.** Ask the user for the US if not already provided. Accepted: pasted text, a file path, a URL, or a **Jira issue**. That is the supported list — other trackers are not supported yet; say so rather than improvising a connector. Fetch or read exactly that source, **nothing else**. - **Jira**: follow `connectors/jira.md`. Portable-first — the user provides an export (REST v3 JSON, CSV, or a pasted issue). With a Jira MCP connected, optionally fetch **only the one designated issue key**: bounded, opt-in, no link crawling. US-ID = the issue key, links recorded as `dependencies:`. Never read credentials, never persist the internal instance URL. No MCP and no export → say so, do not fabricate. - **If the source yields nothing usable** — typically a JS-rendered page returning an empty shell — report the gap. Do **not** fill it from anywhere else. This is the rule most often rationalised around: see `references/source-fidelity.md`. 2. **Triage gates** — before anything is written, blocking. Inspect the captured content and STOP with the stated outcome if any gate fires: - **E