good-enough/core-docs/good-enough-4u0-design-doctrine.md

Good Enough 4u0 — Design Doctrine

File: good-enough-4u0-design-doctrine.md

1) The Three Guarantees

• Never discontinued: Anyone can make more at any time.
• Support never expires: The maker/owner is the maintainer; fixes and improvements are local.
• Price is always right: No royalties, lock-ins, or recurring licenses.

2) COTS Anchor Requirement

• Every design must include at least one Anchor COTS part predicted to remain plentiful (PVC/EMT conduit, mosquito screen, hardware cloth, zip ties, pallet straps, etc.).
• Prefer globally ubiquitous sizes/grades with multiple suppliers and easy substitutes.
• Document a substitution map (acceptable alternates) to keep builds resilient.

3) Ship-Light Pattern

• Ship only custom parts (printed, routed, machined).
• Source Local all Anchor COTS and fasteners.
• Include a simple cut list and tool floor (basic tools only).
• Fasteners: stick to common standards (M-series or Imperial basics).
• Flat-pack if possible for minimal shipping volume.

4) Deliberate Imperfection, Declared

• Each design must state its explicit defect(s) (material downgrade, manual actuation, loose tolerance, etc.).
• Define a clear intended use envelope (“good enough for X; not for Y”).
• Favor soft, visible failure over catastrophic failure.

5) Good-Enough Quality Gate

• Function: Demonstrates the intended task under normal use.
• Safety: No hidden hazards; failure modes are non-injurious.
• Replicability: Another member can rebuild it from the doc alone.
• Transparency: Limits and defects are front-and-center, not footnotes.
• No flawless builds. If it’s perfect, it doesn’t belong here.

6) Scope & Exclusions

• Out of scope: life-critical, medical, structural, high-voltage/power, or any regulated product.
• Focus: everyday utility, not certification-bound applications.

7) Documentation Minimums

• Bill of Materials: split into Ship vs Source Local.
• Anchor COTS rationale: why it’s abundant; acceptable substitutes.
• Build steps: short, photo-friendly, tool-minimal.
• Limitations: where it fails; environments to avoid.
• License: commons/public domain.

8) Credibility Safeguards

• Proof of Use: show it working in a real context.
• Peer sanity check: at least one other member confirms “good enough, not dangerous.”
• Version tag: small, frequent iterations beat polish.