The Story
Traceo.cat is a requirements management platform for teams building AI-native products. The pitch: full traceability from first idea to shipped feature — requirements, baselines, change history, semantic search, the works. Here’s what makes it unusual: we’re building it using the same structured requirement system that the product is designed to provide.How the Build Works
Every feature of Traceo exists as a GitHub issue with a specific structure: epic → block → task. Each task has acceptance criteria, file targets, and a verification command. FORGE reads the board, identifies the next unblocked block, generates a full implementation prompt with all context loaded, and hands it to Claude Code to execute. We’re now 7 blocks into a 22-block production roadiness epic. Each block closes automatically — tasks get resolved, issues get commented and closed, the board advances. Nobody manually manages the project board. The product manages it. Block 7 was infrastructure alignment: stripping stale Supabase Terraform, migrating to Neon, writing the deployment guide. Every acceptance criterion was met autonomously, every GitHub issue updated with a completion summary.The Meta Layer
Traceo’s core proposition is traceability: you should be able to trace any shipped feature back to the requirement that motivated it, the decision that shaped it, and the baseline that locked it. We’re living that on the build itself. When Block 7 closed today, the change history was intact: which acceptance criteria drove which file changes, which findings generated which learnings, which campaign moment emerged from the work. That chain exists because we built Traceo to capture it.The Rebrand Signal
The project is moving fromtraceo-ai to traceo.cat. The old name was a developer-facing signal: “AI tooling.” The new name is a product signal: “this is something you use, not something you install.”
Traceo.cat is for the product team that’s done cobbling requirements together in Notion tables and Linear descriptions and Slack threads. It’s for the team that wants to know, six months from now, why a particular decision was made and what it was trading off.