Prose Map Driver

The map spec parser still exposes the structural discriminator this sprint introduced. A non-comment assignment or section header makes the source spec-shaped, and only text without those declarations is treated as prose. Current driver documentation repeats that rule, so operators can predict the branch without relying on filenames or model judgment.

The generated artifact contract still stands, though the prompt now lives in the bundled agent prompt tree under the write-map-spec name. That prompt tells the planner to author the machine rather than the work list, to use direct command syntax, and to reference support files through stable orchestration paths. The prompt catalog documents the same generated files and the current repair context placeholder.

The modern map pattern still treats the operator source as the declared plan source and stores the generated spec under the orchestration directory. Resume proceeds from recorded artifacts rather than asking the planner again once the generated spec is accepted. Later pattern-runtime work changed the implementation surface, but the durable generated-spec handoff remains part of map mode.

The old smoke harness file from this sprint is no longer present, but its coverage purpose survives in current map and pattern tests. Map mode still has a stubbed, money-free route for proving generated specs can reach ordinary fan-out behavior. Malformed spec-shaped input also remains on the spec-error path rather than being silently reclassified as prose.

The generated spec checker still begins by running the real map enumerator with the same slice arguments fan-out will use. Its accepted report carries actual units and observed field names, while rejection carries an operator-facing diagnostic. The map unit model still exposes the field map that later template and schema checks inspect.

The current checker still rejects unresolved or malformed placeholders in prompt, artifact, gate, skip-test, and checkpoint templates. It also verifies that the generated worker preamble exists and that a checkpoint prompt exists when the spec references one. The artifact placeholder is resolved through the same unit substitution behavior later used by the fan-out.

The checker still scans generated enumerator, gate, and skip-test commands for shell syntax that would not work under direct spawning. It allows an explicit shell program when that is intentionally named, while rejecting bare pipes, redirects, boolean chains, variables, and glob assumptions. It also preserves the older literal work-list rejection for obvious printers before deeper provenance checks run.

Generated specs are still rejected when a build gate or skip-test passes for a unit whose artifact is absent. The checker fills the same command templates the map driver will later use and reports failures as generated-spec diagnostics rather than per-unit worker problems. That keeps a bad authority from being promoted into the fan-out ledger.

The current map pattern has an explicit validate-map-spec step between writing the generated spec and entering the fan-out. A rejected spec branches back through the spec authoring loop rather than reaching unit workers. Hand-written specs still avoid the prose planner, preserving the existing map startup contract.

Map mode now retries rejected generated specs with the checker diagnostic supplied back to the spec-writing prompt. The bundled pattern declares a spec-writing loop before fan-out, and the prompt catalog describes the repair record and accepted-spec promotion. Once a generated spec has been accepted, the ordinary map fan-out consumes that artifact instead of rerunning the planner.

The current checker inspects the enumerator command text and planner-authored files reachable from it for complete static row data. It rejects generated specs that appear to replay a planner-authored work list instead of deriving rows from committed repository data. The code also follows referenced helper files, which extends the old literal-printer guard while leaving the documented caveat about clever laundering shapes.

The documentation now explains when map mode treats a source as prose, what generated files the planner writes, and how rejected specs are retried. The prompt catalog and driver docs both describe the empirical validation before fan-out. Current smoke and unit tests continue to cover successful prose-to-spec flow, invalid generated specs, resume behavior, support artifacts, shell syntax, static rows, and gate falsifiability.