# Mechanical Softwering operational templates — Draft 0.1

## Product Intent
- Owner / date / status:
- Intended user and situation:
- Problem and desired outcome:
- In scope / out of scope:
- Constraints and harms to avoid:
- Observable success evidence:

## System Drawing
- Intent link:
- Context, boundaries and components:
- Interfaces and data flows:
- Quality attributes and tolerances:
- Acceptance criteria and known unknowns:

## Behavioral Reference Map
| Behavior ID | Scenario | Evidence source | Observed result | Confidence | Known anomaly | Intended treatment |
|---|---|---|---|---|---|---|

## Component Contract
- Responsibility and boundary:
- Inputs / outputs / invariants:
- Failures and dependencies:
- Tolerances and acceptance checks:

## Fabrication Brief
- Contract and requested change:
- Allowed / protected areas:
- Required evidence and assumptions:
- Stop conditions and definition of done:

## Decision, assumption and correction registers
| ID | Type | Statement | Basis/rationale | Risk | Evidence/test | Owner | Status |
|---|---|---|---|---|---|---|---|

## Verification Evidence
- Claim and related contract:
- Environment, fixture and versions:
- Procedure / expected / actual:
- Raw evidence, limitations and reviewer:

## Bench or Real Test Report
- Candidate identity and test type:
- Environment, hardware, users or fixtures:
- Safety prerequisites and scenarios:
- Observations, deviations and coverage limits:
- Result and responsible human:

## Acceptance Record
- Candidate and acceptance authority:
- Criteria and evidence reviewed:
- Residual risk and follow-up:
- Decision, scope, name and date:

## Release Candidate Checklist
- [ ] Candidate identity fixed
- [ ] Drawing and contracts current
- [ ] Differences and evidence traced
- [ ] Bench and real test gates satisfied
- [ ] Security, privacy and licensing reviewed
- [ ] Limitations and rollback communicated
- [ ] Human acceptance recorded