How it works

The premise

Disegno (called "Specs" inside the product) is the fifth app in the suite. It holds the specification for a product as the source of truth for building it: prose sections, requirements with stable IDs and acceptance criteria, Mermaid diagrams, a freehand canvas for wireframes, and supporting files. Every edit is kept, and a named version is a snapshot that a build pins to.

It’s made for agents as much as people. Everything you can do in the web app, an agent can do through its hosted MCP server, from reading the context for a build to marking a requirement implemented. Each requirement links to the Andare issues that build it and the Trama pages that document it. A whole spec can be written as one markdown file and imported in one call.

What’s included

Requirements with stable IDs and numbered acceptance criteria that a commit or a test can cite

Every edit kept, with immutable named versions, diffs and restore

Mermaid diagrams, a freehand canvas and attached files in the same spec

A hosted MCP server that gives agents everything the web app gives people

Traced to the Andare issues that implement each requirement and the Trama pages that document it

How it’s built

Disegno is built on React 19, TypeScript, Vite, Firestore, Zod and MCP.

It carries 132 commits since Sep 2026, most recently changed in Oct 2026.

How the work is done

Every project here starts as a written spec, and the spec stays the source of truth once there’s code. The repository keeps a build plan with current status, an append-only decision log of where the code departed from the plan, and a handoff document that describes where things stand, including the unfinished parts.

That’s how one person keeps this many projects moving, and it’s what this page is written from.

Current state

In development. Being worked on now.

The source is private, so the way to check what this page says is to use the product.