Catalog expansion · 2026-07-15

From 43 to 59 tools without losing the evidence boundary

The catalog grew across AI coding, application security, infrastructure, and wearable computing—but the useful work was keeping every new profile inside one source model with an honest experience label.

Who, how, and why

Written by Tom from project records, repository evidence, and the actual operating decision. AI may assist organization and drafting; the founder remains responsible for factual review, disclosure, and publication.

01 · What changed

The implementation move.

01Added AI coding and engineering agents, application-security tools, hosting and infrastructure, and wearable AI and ambient-computing profiles.
02Modeled GitHub Copilot as a workflow that can expose Claude, Codex, and Gemini provider coverage without erasing their standalone profiles.
03Kept tool-catalog coverage separate from the smaller owner-approved founder-project registry.
04Replaced hard-coded catalog counts with values derived from the shared catalog.

02 · Evidence

What supports the current claim.

The rendered-route suite checks representative new tool pages and category hubs.
The JSON and CSV export tests assert 59 tool records and 13 categories.
The same source data drives the website and downloadable research catalog.

03 · What I learned

The reusable lesson.

Lesson 01A larger directory is not automatically a better publication. The expansion only improved the product because every addition carried a job, evidence boundary, failure case, and operating role.

Lesson 02Provider coverage and product ownership need separate fields. Otherwise a workflow layer, model vendor, sensor, and application runtime collapse into a misleading flat list.

Lesson 03Catalog counts should be derived from the source, not repeated across pages and documentation.

04 · Security and control impact

How the authority or release boundary changed.

No new affiliate relationship was implied by adding a tool.
Owned-product claims remained visibly separated from independent tool profiles.
The publication stayed private and non-indexed while the expanded catalog was reviewed.

Current limitationA passing catalog build proves the pages and exports are internally consistent. It does not prove complete product mastery or public-launch readiness.

Next decisionUse the expanded catalog as the foundation for a project registry and founder build records without diluting the publication's primary tool-decision purpose.