# Build record: [project or workflow name]

Use this blank template with evidence from your own work. Keep unknowns visible.
Do not replace an unrun check with an expected result.

## 1. Job and constraints

- Owner and intended user: [roles; omit private names in public copies]
- Job to be done: [concrete task]
- Useful result: [what the user needs back]
- Constraints and boundaries: [data, authority, time, hardware, access]
- Out of scope: [what this build does not attempt]
- Must not change: [state, behavior or material to preserve]

## 2. Version and dates

- Build or version: [identifier]
- Original publication date, if public: [date or unknown]
- Record updated: [date and meaningful change, or unknown]
- Check date: [date of the actual check, or not run]
- Lifecycle: [developing / in use / paused / complete / archived]
- Availability: [public tool / download / private app / record only]

A record update is not a new runtime check. Keep those dates separate.

## 3. Decisions and alternatives

- Chosen approach: [what and why]
- Useful alternatives considered: [options and tradeoffs, if needed]
- Rejected or changed direction: [what changed the decision]
- Decision owner: [who had the authority to choose]

## 4. Checks and scope

For each actual check:

- Question or requirement: [the claim being checked]
- Expected behavior: [defined before accepting the output]
- Actual result: [what happened, or not run]
- Build/version checked: [exact candidate]
- Device or environment: [actual model, browser, emulator/core or other setup]
- Command or procedure: [reproducible steps without secrets]
- Evidence: [approved link, report or recording]
- Limits of this check: [what it cannot establish]

Independent review, if used:

- Assignment and selected evidence: [bounded question and sources]
- Reviewer: [appropriate attribution]
- Findings: [specific issues, or no findings reported]
- Lead's decision and verification: [accepted, rejected, fixed, unresolved; why]

## 5. Failures and repairs

- Failure: [what went wrong, or no observation recorded]
- Detection: [how it was found]
- Change: [what was repaired]
- Follow-up check and evidence: [actual result, or pending]
- Assistance required: [keep assisted repair distinct from the first attempt]

## 6. Limits and human acceptance

- Not tested or not proven: [remaining questions]
- Release gate: [what must be true]
- Current gate result: [met / not met / not run / pending human decision]
- Person or role making the remaining decision: [authority]
- What would change the decision: [specific new evidence]

## 7. Operation and handoff

- How to check health: [what the owner can inspect]
- Safe recovery: [bounded steps and required confirmation]
- Stop or escalation condition: [when to stop acting and ask]
- Persistence check: [how a saved change is read back, if relevant]
- Next action and owner: [concrete step]

## 8. Evidence, attribution and publication

- Source records: [approved evidence links]
- Collaborators and contributions: [accurate roles]
- Asset sources and permissions: [source, license and required credit]
- Fictional or demonstration material: [explicit labels]
- Public/private boundary: [what may be shared and what must stay out]
- Corrections: [date, corrected claim and supporting evidence]

Before publishing, check that no private data, credentials, personal identifiers,
or unapproved source material entered the record or its downloads.