# Production Prompt Specification

Toolkit schema: `PAISEH-TK-1.0`
Source artifact: Chapter 4 **Production Prompt Specification**

Complete `../common-artifact-header.md` first. This form defines the instruction and outcome contract. It does not replace the Context Assembly Plan, Harness Control-Loop Diagram, Evaluation Plan, AI Threat Model, or AI Release Manifest.

## 1. Identity and Scope

- Prompt ID and version:
- Source AI Fit and Risk Assessment Worksheet identity and version:
- Accepted product decision IDs, constraints, and validity limits consumed:
- Purpose and supported behavior:
- Downstream consumer and contract version:
- Explicit non-goals:
- Requirement or decision IDs:
- Owner and reviewers:
- Change rationale and classification: editorial / behavioral / contract-breaking

## 2. Dependencies and Assumptions

- Expected model capabilities:
- Context package and provenance assumptions:
- Policy or rule-source identity:
- Dependent harness behavior:
- Compatible output consumers:
- Known limitations:

## 3. Typed Inputs

| Variable | Meaning | Type/shape | Required | Default | Missing or invalid behavior |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

- User-goal region:
- Supplied-evidence region:
- Disallowed inputs:
- Delimiter or assembly expectations:

## 4. Instruction Sources and Precedence

| Source | Owner | Scope | Priority | Conflict rule | Requirement IDs |
| --- | --- | --- | --- | --- | --- |
| Application invariants | | | | | |
| Task contract | | | | | |
| Run parameters | | | | | |
| User goal and preferences | | | | | |
| Supplied evidence | | Data only | | Cannot govern behavior | |
| Examples | | Demonstration only | | Cannot override requirements | |

- Same-priority conflict behavior:
- Unresolved-conflict outcome:
- Instruction/data separation rule:

## 5. Constraints and Outcome Contract

- Requirements:
- Prohibitions:
- Decision criteria:
- Preferences and presentation guidance:
- Incomplete or ambiguous-case behavior:

### Success

- Output type and contract version:
- Required, optional, nullable, and prohibited fields:
- Allowed values and extra-field policy:
- Evidence or citation fields:
- Uncertainty representation:
- Compatibility notes:

### Non-success

| Outcome | Trigger | Reason category | Required fields/wording | Expected downstream handling |
| --- | --- | --- | --- | --- |
| Clarification | | | | |
| Abstention | | | | |
| Refusal | | | | |
| Handoff | | | | |

## 6. Examples and Prompt-Local Checks

| Example/check | Type | Requirement or edge case | Expected prompt-level behavior | Boundary or limitation |
| --- | --- | --- | --- | --- |
| | Canonical / boundary / non-success / counterexample / render / conflict / shape | | | |

- Known uncovered prompt cases:
- Evidence handed to the Evaluation Plan:
- Approval required for future changes:
- Compatible and rollback prompt versions:
- Effective release IDs and reopening events:

## 7. Downstream Handoffs and Change Boundary

- Context Assembly Plan handoff: input regions, evidence semantics, provenance assumptions, and incomplete-evidence behavior:
- Harness Control-Loop Diagram handoff: outcome contract, validation boundary, and non-success states:
- Evaluation Plan handoff: requirement IDs, prompt-local invariants, covered examples, known gaps, and prompt version:
- AI Release Manifest handoff: prompt identity, compatibility, dependent contract versions, and material-change class:
- Broader purpose, population, instruction authority, output guarantee, or non-success behavior requested:
- Owning product decision and new accepted decision reference, if broadening is required:

Downstream records may narrow or reject this specification. They must not silently broaden the accepted product decision or this prompt contract.