Ecosystem intelligence for the Constructs Network. The quietest stall in the bazaar.
/constructs install gecko| Command | What |
|---|---|
/observe |
Single-pass network health check |
/patrol |
Autonomous observation loop with ratcheting score |
/diagnose <slug> |
Deep investigation of one construct |
/report |
Synthesize observations into health report |
Network Health Score (0-100), computed from:
- API Liveness (20%) — is the registry responding?
- Version Freshness (25%) — are constructs being maintained?
- Category Coverage (15%) — are all 8 categories populated?
- Identity-Reality Drift (20%) — do constructs do what they claim?
- Composition Density (10%) — are constructs composing?
- Verification Flow (10%) — are constructs graduating?
Inspired by Karpathy's autoresearch (the loop) and Pi (the minimalism). 4 skills, lean harness, frozen metric, git-as-memory.
MIT