30 lines
1.6 KiB
Markdown
30 lines
1.6 KiB
Markdown
# Directory Engine — Status
|
|
|
|
**Last updated:** 2026-08-23
|
|
**Owner agent:** Leonard
|
|
|
|
## Current State
|
|
- Repo initialized with playbook.
|
|
- Niche locked: **local AI tools and stacks for real hardware**.
|
|
- First page published: `pages/lm-studio.md`.
|
|
- No Astro site yet; content-first validation remains intentional.
|
|
- Research / engineer prompts are present and used as the operating contract.
|
|
|
|
## Niche Definition
|
|
Curated, evidence-backed entries for software that helps people run, serve, connect, or operate AI on their own hardware. Pages must expose practical fit: platform support, hardware constraints, offline behavior, APIs, MCP, deployment mode, access model, and alternatives.
|
|
|
|
## Next Actions for Leonard
|
|
1. Add four more entries spanning different layers: CLI/runtime, web UI, serving, and coding/agent workflow.
|
|
2. Compare the first five pages for recurring schema fields and editorial gaps.
|
|
3. Validate search intent and repeatability before building the Astro presentation layer.
|
|
4. Do not add affiliate or outbound automation until traffic or user-intent evidence exists.
|
|
5. Update this status after every cycle.
|
|
|
|
## Recent Runs
|
|
- **2026-08-23 — Cycle 1:** locked niche and published LM Studio entry from official documentation and pricing sources.
|
|
|
|
## Open Questions
|
|
- Which page types attract qualified search intent: runtime comparisons, hardware-to-model fit, or complete stack recipes?
|
|
- Can five entries produce a useful internal taxonomy without becoming a generic software list?
|
|
- What measurable traffic or referral signal should unlock the first monetization test?
|