Initial create

core-docs/good-enough-4u0-certificate-central-compromise.md

@@ -0,0 +1,32 @@
+# Good Enough 4u0 — Certificate of Central Compromise (CCC)
+
+**File:** `good-enough-4u0-certificate-central-compromise.md`
+
+## Purpose
+Every design must center on **one intentional compromise**: the *good-enough flaw* that makes the design belong in Good Enough 4u0. The CCC documents that compromise, why it was chosen, and how it defines the project.
+
+## CCC Template
+
+**1. Design Name**
+- Clear title of the design.
+
+**2. Central Compromise**
+- The specific defect or substitution at the core of this design.
+
+**3. Purpose of Compromise**
+- Why this compromise was chosen (cost, availability, simplicity, etc.).
+
+**4. Good-Enough Justification**
+- Why the compromise is acceptable within an explicit use envelope.
+
+**5. Replicability Proof**
+- Anchor COTS that ensure the design can be reproduced.
+
+**6. Substitution Map (Optional)**
+- Alternate materials if builders want to adapt.
+
+**7. Failure Envelope**
+- Where the compromise fails; how failure appears (prefer visible failure).
+
+**8. Statement of Intent**
+- One-sentence declaration of why the design belongs in Good Enough 4u0.

core-docs/good-enough-4u0-cots-anchor-standard.md

@@ -0,0 +1,26 @@
+# Good Enough 4u0 — COTS Anchor Standard
+
+**File:** `good-enough-4u0-cots-anchor-standard.md`
+
+## Purpose
+Ensure every design has at least one **Anchor COTS** part: a globally common, indefinitely available component that stabilizes the design and makes replication realistic.
+
+## Anchor Criteria
+- **Plentiful:** Mass-produced at global scale; no single-supplier risk.
+- **Future-proof:** Likely to remain in production for decades (building trades, agriculture, logistics).
+- **Local availability:** Stocked in hardware stores, farm suppliers, big-box retailers.
+- **Interchangeable:** Accepts substitutes (different brand, slight dimension variations).
+- **Non-exotic:** No boutique, hobbyist-only, or import-only parts.
+
+## Example Anchors
+- PVC pipe / EMT conduit.
+- Mosquito screen.
+- Hardware cloth / wire mesh.
+- Zip ties.
+- Pallet straps.
+- Common bolts/nuts/washers (M6 / 1/4″).
+
+## Documentation Requirements
+- **Anchor Identification:** “This design anchors on 1/2″ EMT conduit.”
+- **Substitution Map:** “Can also use 1/2″ PVC, bamboo pole, or hardwood dowel.”
+- **Failure Note:** Explain what changes if a weaker/stronger substitute is used.

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

@@ -0,0 +1,48 @@
+# 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.