26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# Good Enough 4u0 — Quality Gates
|
|
|
|
**File:** `good-enough-4u0-quality-gates.md`
|
|
|
|
## Purpose
|
|
Define the threshold between **good enough** and **too bad**. Enforce competency by ensuring designs fail gracefully, not dangerously.
|
|
|
|
## Mandatory Gates
|
|
- **Functionality:** Must perform the stated task in normal conditions.
|
|
- **Safety:** No hidden hazards. Failure must be visible and non-injurious.
|
|
- **Replicability:** Another member should be able to rebuild from docs alone.
|
|
- **Transparency:** All known defects/limits must be documented clearly.
|
|
- **Imperfection:** Must declare at least one intentional substandard choice. Flawless designs are disqualified.
|
|
|
|
## Failure Modes
|
|
- **Acceptable:** Slack tolerances, cosmetic flaws, wear over time, visible deformation.
|
|
- **Unacceptable:** Collapse under expected load, brittle fracture with shrapnel, fire/electrical hazards, silent degradation.
|
|
|
|
## Peer Check
|
|
- Each design gets a **sanity check** from another member: “yes, this is good enough.”
|
|
- Builds without peer check are labeled **UNVERIFIED**.
|
|
|
|
## Versioning
|
|
- Use simple version tags (v0.1, v0.2, …).
|
|
- Prefer frequent, small iterations over polish.
|