A project intelligence platform that organizes project knowledge into reusable, structured context for AI-assisted development.
Project knowledge lives everywhere except where it's needed: docs, tickets, chat threads, meeting notes. When it's time to brief an AI tool or hand context to someone else, it has to be reassembled by hand - every time.
Cuetoba treats project knowledge as structured, reusable material instead of scattered notes - something you organize once and reuse as AI-ready context.
A live product built as four coordinated applications: a marketing site, a customer workspace for project knowledge and context recipes, a node-based visual flow workspace, and an internal backoffice - all on a shared domain model.
03Complexity & Concurrency
4 case-specific challenges
Storing notes is easy; making them reusable is the product. Recipes define instructions and an output format, then compile a project's knowledge into context a person or AI tool can actually consume.
This isn't generic diagramming. Every node type has domain semantics - a decision is not a requirement is not a question - and statuses like draft, needs_review and confirmed carry product meaning through the flow.
A flow is edited continuously, but sharing and review need stable targets. Versions store immutable snapshots with their own schema version, so a shared link or review session stays valid while the canvas keeps moving.
Marketing, customer app, flow workspace and backoffice share domain concepts - workspaces, projects, plans - without sharing a codebase. The seam between them is the data model, which forced the domain language to stay consistent.
04System Blueprint
Service boundaries / data model
Application surfaces
Client-facing
cuetoba.com - positioning & acquisition
Client-facing
app.cuetoba.com - projects · knowledge · context recipes
node-based project flows
bo.cuetoba.com - users · workspaces · subscriptions · promotions · audit
Data / Persistence
Prisma domain model · Supabase auth
05Engineering Trade-offs
Deliberate choices made to preserve velocity without sacrificing correctness.
Instead of coupling the product to one AI provider, recipes compile project knowledge into portable structured output - text, markdown, JSON or HTML - that works with whatever tool the customer already uses.
Nodes and edges persist as domain records, and versions store full snapshots with a schema version. Sharing and review operate on versions, so they stay meaningful as the graph evolves.
Projects and subscriptions belong to workspaces with membership roles rather than to individual accounts - the access model matches how a product is actually shared inside a team.
Plans, subscriptions, promotions, users, workspaces and audit live in a separate application, so operational tooling doesn't leak into the customer-facing product.
Auth, PostgreSQL and storage come from Supabase, with Prisma owning the domain model - the effort goes into product surface area instead of infrastructure plumbing.
06Surface Breakdown
Product surface / Cuetoba
Product surface / Cuetoba
Product surface / Cuetoba
07Project Status
Live across three public surfaces - cuetoba.com, app.cuetoba.com and bo.cuetoba.com. The flow workspace is implemented as its own application within the product.
Status: live - shipped and running.
Current project status
LIVE08Retrospective & Takeaways
PROJECT INDEX / 09
The next chapter starts here