diff --git a/core-docs/good-enough-4u0-onboarding.md b/core-docs/good-enough-4u0-onboarding.md
new file mode 100644
index 0000000..08ac4f7
--- /dev/null
+++ b/core-docs/good-enough-4u0-onboarding.md
@@ -0,0 +1,67 @@
+# Good Enough 4u0 — Onboarding Guide
+
+**File:** `good-enough-4u0-onboarding.md`
+
+## Welcome
+Good Enough 4u0 is a commons of deliberately imperfect designs. To join, you don’t need a degree, expensive tools, or flawless documentation. You only need a design idea—however rough—and the willingness to share it.
+
+## Why It Won’t Take Much Time
+- **No polish needed.** Upload raw notes, sketches, or messy drafts.
+- **No reinventing.** We drop your inputs into existing forms (CCC, Design/Material Passports).
+- **Guided process.** I structure and edit as we go—iteration over perfection.
+- **Reuse everywhere.** Once a Material Passport exists (PVC, EMT, straps), others reuse it.
+
+## What to Upload
+- Sketches, CAD, photos.
+- Any materials/parts list, even partial.
+- One sentence naming the **flaw** (your Central Compromise).
+- Any limits you already know (“not for heat,” “will creep,” etc.).
+
+## How the Process Works
+1) **Upload what you have.** Paste notes or send files here.
+2) **Map to forms.** We turn your notes into:
+   - **CCC** (why the design exists + declared flaw)
+   - **Design Passport** (summary, materials, tools, status)
+   - **Material Passports** (only for salvage/non-standard stuff)
+3) **Iterate lightly.** Short loops until it’s clear and replicable.
+4) **Publish.** When docs are clear and limits are honest, it’s “good enough.”
+
+## My Role: Critical & Rational Review (Always On)
+**I promise to:**
+- **Stress-test claims** against the Quality Gates and call out risks plainly.
+- **Refuse hype:** if something’s unknown, I say **“unknown”** and propose a cheap test.
+- **State limits up front** (failure modes, non-uses, hazards).
+- **Prefer small proofs** over long debate: 5-minute/1-hour tests that shrink uncertainty fast.
+- **Document verdicts** in a simple Confidence Statement.
+
+> **Pinned reminder (for me):** Wear the critical/rational hat every time. No flattery, no glossing over failure.
+
+## Quarantine & Confidence
+All new designs start in **QUARANTINE** until they earn minimal trust.
+
+**Statuses**
+- **QUARANTINE (default):** Docs exist, claims are stated, but no independent replication yet.
+- **PEER CHECKED:** At least one other member rebuilt it and confirmed “good enough” within the declared envelope.
+- **IN THE WILD:** 3+ independent builds with the same outcome; minor variations allowed.
+- **DEPRECATED:** A safer/saner alternative exists or a material hazard emerged.
+
+**Exit QUARANTINE — minimum criteria**
+1) **Proof of Use:** one real use-case (photo or brief note) showing it doing the stated job.
+2) **Hazard & Failure Envelope:** explicit limits and expected failure modes are documented.
+3) **Replicability Check:** another member skim-builds from the doc or we complete a 5–30 minute bench test.
+
+**Confidence Statement (I provide this for every design)**
+- **Usefulness:** Low / Medium / High
+- **Why:** 1–3 lines tying the claim to docs, tests, or physics.
+- **Weakest link:** The part most likely to fail first.
+
+**Quick Test Patterns**
+- **5-minute:** paper/scale check, quick dry-fit, handheld load.
+- **1-hour:** print a small subset, mix a tiny batch, clamp/tension a short span.
+- **1-day:** full build once; record where it failed or surprised you.
+
+## Next Step
+- Pick one idea.
+- Write its flaw in one sentence.
+- Upload whatever you have.
+- We’ll push it through **Quarantine → Confidence → Publish** together.
diff --git a/core-docs/good-enough-4u0-preamble.md b/core-docs/good-enough-4u0-preamble.md
new file mode 100644
index 0000000..523a5b5
--- /dev/null
+++ b/core-docs/good-enough-4u0-preamble.md
@@ -0,0 +1,13 @@
+# Good Enough 4u0  
+### A Manufacturing Association for the Rest of Us
+
+**File:** `good-enough-4u0-preamble.md`
+
+**Preamble**  
+Good Enough 4u0 is founded on the conviction that perfection is a trap. Industry chases flawless standards, proprietary tools, and closed credentials, leaving the rest of us excluded. We embrace the opposite: the power of imperfection.
+
+Our work is intentionally substandard—**not flawless, not useless, but good enough.** Each member contributes designs that are deliberately below industrial norms, yet fully documented and freely shared. This protects us from capture, invites everyone to participate, and builds a commons of practical, reproducible, and adaptable tools.
+
+Competency here is measured not by perfection, but by judgment: knowing the difference between what fails dangerously and what works “well enough.” Flawless products are forbidden. Documented imperfection is required.
+
+We exist to create, to share, and to prove that the spirit of “Industry 4.0” belongs not only to factories, but to garages, workshops, and living rooms. **Good Enough 4u0 is our space, our standard, and our collective craft.**
diff --git a/core-docs/good-enough-4u0-quality-gates.md b/core-docs/good-enough-4u0-quality-gates.md
new file mode 100644
index 0000000..aecab9c
--- /dev/null
+++ b/core-docs/good-enough-4u0-quality-gates.md
@@ -0,0 +1,25 @@
+# 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.