What counts as a good microproduct
Good microproducts share several observable traits—most of them discoverable directly from Markdown contracts plus live demos:
- Narrow decision surface with observable inputs and outputs documented in /standards/folder-contract#markdown-contract-purposes.
- Transparent evaluation—even qualitative rubrics—in /standards/folder-contract#markdown-contract-purposes.
- Honest acknowledgement of brittle assumptions surfaced in README + AGENTS files.
- Repro instructions that do not rely on unpublished secrets (
demo.md).
Signals that should block promotion
| Anti-pattern | Why it fails |
|---|---|
| Dashboards without actions | Humans cannot automate follow-ups |
| Vague personas | Unable to prioritize roadmap |
| Implicit model drift | Silent failures undermine trust |
| Missing agent entrypoints | Blocks hybrid human/agent teams |
Treat this page as prose backing the actionable items listed in /AGENTS.md.