Ethos Configuration

## Setup: Track this exercise with Beads

```bash
bd create "Praxis: Configure ethos for [project/domain]" --type=feature --labels=learn,agents
bd create "Define 1+ DRY-level principle with learn_ethos" --type=task --labels=learn
bd create "Define 1+ Rams-level principle with learn_ethos" --type=task --labels=learn
bd create "Define 1+ Heidegger-level principle with learn_ethos" --type=task --labels=learn
bd create "Add constraint to enforce a principle" --type=task --labels=learn
bd create "Add health check with measurable threshold" --type=task --labels=learn
bd create "Export ethos and commit to repository" --type=task --labels=learn
```

---

Help me create MY ethos—a living document of principles that guide my work.

I'm building my own version of CREATE SOMETHING's ethos layer. Guide me through:

1. **Define 3 principles** (one at each Triad level):

   **DRY level** (Implementation):
   - What implementation pattern do I always follow?
   - Example: "Single source of truth for configuration"

   **Rams level** (Artifact):
   - What standard determines if something "earns its existence"?
   - Example: "Every UI element must serve a user task"

   **Heidegger level** (System):
   - How do I ensure things serve the larger system?
   - Example: "Components must be usable in isolation"

2. **Add constraints** that enforce my principles:
   - File patterns they apply to (e.g., "src/components/**/*.svelte")
   - Rules to check (e.g., "no inline styles")
   - Severity (error/warning/info)

3. **Add health checks** with measurable thresholds:
   - Metrics I care about (bundle size, test coverage, complexity)
   - Acceptable thresholds
   - Commands to measure them

4. **Export and persist**:
   - Create .ethos/ directory in my project
   - Save principles.json, constraints.json, health.json

Use learn_ethos to save each principle. Show me what I'm creating as we go.

My domain is: [YOUR_DOMAIN - e.g., "React component library", "API services", "content site"]