Use this prompt after the harness has translated the neutral workflow into its own native primitives.

Run the neutral RFC workflow for one selected project pack.

Selected project pack: `projects/<selected-project>/`
Target scope: <one document | named subset | full project suite>
Run workspace: <external run-local path or harness workspace>

## Load order

1. Read `workflow.contract.yaml`.
2. Read the neutral workflow docs under `core/`.
3. Read the reusable role briefs, toolchain notes, and templates needed for the selected scope.
4. Read `projects/<selected-project>/README.md` and the selected pack's suite, corpus, references, metadata, document briefs, and examples.
5. Apply the already-prepared harness translation so execution uses native primitives without changing workflow semantics.

## Execution rules

- Follow the contract's stage order and gates.
- Start with scope, corpus, and context loading, not public prose.
- Build evidence artifacts before drafting public RFC text.
- Admit no public technical or normative claim unless it satisfies the contract's evidence and source-authority rules.
- Keep public deliverables separate from evidence artifacts at every stage.
- Use validated examples or explicitly mark examples as illustrative-only in evidence artifacts.
- When a gate fails, repair the earliest faulty artifact first, then re-run only affected downstream stages.
- Keep source-specific behavior inside the selected project pack. Do not push it back into `core/`.

## Minimum stage intent

Execute the contract so the run covers these workflow responsibilities:
- define scope and target deliverables,
- load orientation/context materials,
- gather and confirm source evidence,
- build claim/evidence and capability-coverage artifacts,
- draft from accepted evidence only,
- validate examples and mechanical consistency,
- run review lanes and reader-facing gates,
- apply recursive corrections,
- run clean-room proof,
- package public outputs separately from evidence.

## Required run outputs

Produce, at minimum:
- the public deliverables named by the selected scope,
- the evidence artifacts required by the contract for those deliverables,
- gate results or validation records for the executed stages,
- and a final packaging summary that keeps public artifacts distinct from evidence artifacts.

## Escalation rules

Stop and escalate instead of guessing when:
- required source evidence is missing or contradictory,
- a required claim cannot be accepted under the source-authority rules,
- a required example cannot be validated,
- a review or clean-room gate exposes unresolved blocking ambiguity,
- or the selected scope depends on materials absent from the project pack.

## Final handoff

At completion, report:
- selected project pack,
- target scope,
- public artifacts produced,
- evidence artifacts produced,
- gates passed or outstanding,
- and any residual risks or escalations.