🧵 Reusable infrastructure-as-code building blocks for the Ego Hygiene ecosystem.
Status: architecture-first and provisional. Filament now has a defined target boundary, but its provider/tooling implementation should be proven through real consumers before becoming stable.
Filament is intended to own reusable infrastructure-as-code modules, stacks, interfaces, validation, examples, and provider adapters that multiple Ego Hygiene repositories can consume without copying infrastructure implementation into each product.
The core idea is:
product/platform intent
↓
versioned Filament module or stack
↓
reviewable infrastructure plan
↓
consumer-controlled deployment/state
Filament should make infrastructure reusable without becoming the owner of every deployed environment.
Filament does not replace:
- Hygiene — organization architecture, policy, and repository ownership.
- Realm — developer environments, Dev Containers, workstation/runtime profiles.
- Mantle — portable shell and workstation behavior.
- Relay — GitHub Actions and CI/CD orchestration.
- Holon — repository/template materialization.
- Pace — fleet reconciliation and upgrades.
- Observatory — organization visibility and evidence.
- Product repositories — product-specific infrastructure intent, credentials, budgets, and deployed state.
The earlier deferred Firmament concept overlaps this newly clarified boundary and should be reconciled at the organization level before any separate Firmament repository is created.
Start with PURPOSE.md, ARCHITECTURE.md, DECISIONS.md, and ROADMAP.md. META.md indexes the complete architecture graph.
Prove Filament's boundary with one small, reusable, independently testable infrastructure vertical slice before selecting a broad provider strategy.