Artifact examples: inert vs. decision-grade
This page is a fast self-check, not a first teaching. The chapters explain why each field exists and what happens when it is missing; this page consolidates the four core artifact shapes so you can run a quick test against your own documents without re-reading a chapter.
The four artifacts below are the core surfaces the Hardware OS runs on. Every chapter that mentions "decision record," "requirement," "risk row," or "one-page status" is referring to these shapes.
Requirement
The inert version has a value but gives the team nothing to test, no condition to bound it, and no way to know who approved the current number or why.
| Field | Inert | Decision-grade |
|---|---|---|
| Statement | "System shall be robust" | "Leak rate shall be ≤ 0.5 sccm at 1.2 bar differential, ambient 0–40 °C, measured by Method M-04" |
| Owner | (blank) | Named engineer, week of last review |
| Evidence | (blank) | Link to test result or physics derivation that bounds the value |
| Acceptance method | "TBD" | Specific test method, sample size, pass criterion |
| Revision history | (blank) | Change log with rationale and approver for each revision |
See Ch. 5 for revision discipline and the hygiene checklist.
Decision record
The inert version records an outcome with no trail. Anyone who reads it six weeks later cannot reconstruct the trade, cannot tell who approved it, and cannot find what else changed as a result.
| Field | Inert | Decision-grade |
|---|---|---|
| Decision | "Team aligned to update thermal limit" | "Revise thermal case temperature requirement from 75 °C to 78 °C, per first chamber test evidence" |
| Owner | TBD | Thermal lead |
| Rationale | (blank) | "First chamber test measured 78 °C steady-state; boundary condition error in thermal model confirmed" |
| Alternatives | (blank) | "Considered 80 °C with derating margin — rejected: supplier cannot hold derating at current geometry" |
| Downstream artifacts updated | (blank) | "Supplier package flagged for re-qualification, thermal risk row updated, Gate 0 one-page revised" |
| Approver / date | (blank) | Program lead, Day 9 after first chamber test |
See Ch. 4 for DRI ownership and minimum decision record fields.
Risk row
The inert version looks like an active register. No one can trigger a decision from it, and "yellow" carries no evidence anyone can challenge or update.
| Field | Inert | Decision-grade |
|---|---|---|
| Statement | "Thermal" | "Thermal margin insufficient at full-duty 40 °C ambient" |
| Owner | Engineering team | Thermal lead |
| Likelihood / Impact | Yellow | Medium (first chamber test showed 78 °C vs 75 °C limit) / High (gate hold, supplier re-qual) |
| Trigger | (blank) | Any chamber run exceeding 74 °C |
| Mitigation | In progress | Revise thermal case temperature requirement; re-qual supplier package by Gate 0 |
| Decision date | (blank) | Gate 0 |
| Evidence | (blank) | First chamber test, thermal model |
See Ch. 6 for the full risk-row schema and gate decision logic.
One-page status
The inert version compresses uncertainty into confidence — an exec or PM reading it cannot tell whether the calm tone reflects real evidence or polished slides. When it is wrong, nobody finds out until it is too late to act cheaply.
| Section | Inert | Decision-grade |
|---|---|---|
| Current state | "Program tracking to plan" | "Gate 0 on track; thermal risk open — thermal limit revision decision due Friday; supplier re-qual starts Monday" |
| Top risks | "Thermal risk tracking green" | "Thermal: medium/high — first chamber test measured 78 °C vs 75 °C limit; owner: thermal lead; decision: Gate 0" |
| Decision log deltas | (blank) | "Thermal limit decision closed: requirement revised to 78 °C; supplier notified" |
| Critical dependencies | "Supplier on track" | "Cold-plate extrusion: slip of 8 working days; replanned to Week 22; critical path impact: none if Gate 0 holds" |
| Asks / escalations | "None" | "Need program lead approval on revised supplier qualification plan by Thursday" |
See Ch. 6 for the minimum one-page schema and source-record traceability requirement.
Substitute your program's artifacts; the field shapes hold.