source-mappinglisted

# source-mapping The source-mapping gate is the kit's one load-bearing rule (constitution Principle IV): **before any `silver.*` SQL is written, the source MUST be profiled and mapped into committed, reviewed artifacts.** This skill runs that gate: profile -> author the five artifacts -> stop at judgment calls -> hard-stop before silver. It formalizes Phases 1-4 of the medallion playbook; the playbook stays authoritative on HOW to decide, the templates on WHAT to record. ## Scope boundary (read first) This skill profiles a source and authors the mapping artifacts, then STOPS. It does NOT write `silver.*` or `gold.*` SQL, does NOT call pbi-cli or Power BI Desktop, and does NOT decide the judgment calls Principle V reserves for a human. Silver is downstream of an APPROVED map -- approval is the reviewer's action, not this skill's. ## The five artifacts (write the blanks with `seshat scaffold-source <table>`) Run `seshat scaffold-source <table>` to materialize the canonical blanks into `mappings/<table>/`. Do NOT hand-author these files, and do NOT copy from a `templates/` path: `templates/` exists only in the Seshat development repo, so that instruction fails for anyone who installed the kit as a tool -- and a hand-written `source-map.yaml` silently misses the canonical shape that `seshat validate` and the gold stages require (issue #488). The scaffolder ships inside the package and never overwrites an existing file. Per ADR 0003 (mapping-artifact location), a table's fil