Tony_tech/directory-engine
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reset: clear niche decision and Cycle 1 log

Browse Source
This commit is contained in:
Ty
2026-08-23 05:59:40 +00:00
parent 1c18596764
commit 1ee481a57b
1 changed files with 5 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
decisions.md
+5 -11
View File
@@ -3,15 +3,9 @@
## 2026-08-22 — Repo creation ## 2026-08-22 — Repo creation
- Created Tony_tech/directory-engine as the home for Leonard-powered niche directory work. - Created Tony_tech/directory-engine as the home for Leonard-powered niche directory work.
- Structure and playbook seeded from Startup Ideas Podcast directory thesis. - Structure and playbook seeded from Startup Ideas Podcast directory thesis.
- Niche selection deferred; will be recorded here with rationale and date. - Niche selection deferred; will be recorded here with rationale and data.
## 2026-08-23 — Niche selected: local AI tools and stacks ## 2026-08-23 — Reset
- Focus: curated, evidence-backed entries for software that helps people run, serve, connect, or operate AI on their own hardware. - Operator requested deletion of the LM Studio page and full reset of niche lock.
- Rationale: strong fit with Tony’s existing hardware and local-first AI work; higher editorial taste than a generic AI-tools directory; useful decision data includes platform support, VRAM/RAM expectations, offline behavior, APIs, MCP, and deployment mode. - Previous niche decision (local AI tools and stacks for real hardware) and Cycle 1 entry removed.
- Initial monetization hypothesis: qualified software/hardware referrals, sponsored placements only after trust and traffic exist, and eventually paid stack-selection or setup referrals. No monetization claims until measured demand exists. - Awaiting new vertical selection from operator.
- Editorial boundary: do not publish a broad listicle. Each page must explain the real fit, constraints, access model, and evidence. Prefer official documentation and observable technical facts over affiliate copy.
- First candidate: LM Studio, because it is a representative desktop-to-local-server workflow with official documentation covering offline use, model runtimes, MCP, APIs, and system requirements.
## Pending
- [ ] Validate demand and repeatability after the first 5 pages.
- [ ] Define the first monetization test only after traffic or user-intent evidence.