Pizza Developer

Archive one record by kind and id. It leaves its active list and keeps its content; unarchive brings it back.

• project: hidden from the default dashboard view but still reachable (list_projects and search still find it).

• idea: for a completed idea; it leaves the active planning order and stays available through list_ideas with state archived.

• delivery: keeps its record and batches but leaves the Deliveries page, the Public Delivery Page, and the showcase; readable through list_deliveries with archived=true.

• dictionary_term: leaves the active dictionary; readable through list_dictionary_terms with archived=true. Only archived terms can be deleted.

• info: leaves the active list and get_project_state; keeps its text and revision history. Only archived pages can be deleted.

• instruction: leaves the active list and the listed instruction resources; keeps its content and revision history. Only archived instructions can be deleted. During an active workflow run, accepted only in its self-improvement stage.

• workflow: for a workflow the vibe coder no longer uses; it stops being offered for new runs, an open run of it continues, and its history stays.

Begin repository implementation in one boundary call. Pass workId to claim that Work, or projectId to resume the active Work or claim the next ordered one. Each open workflow run builds its own Batch; pass runId to work in a specific run when several are open. If nothing is developing there, the next planned batch is started automatically when it contains implementable work. Returns the Work brief and the project's own instruction documents that apply to it.

Cancel an open workflow run without deleting its recorded route or measurements. A truthful reason is required.

Check a draft against the rulesets on the current step of an open workflow run, without saving it and without refusing. Rules are checked by TypeSafe, a separate provider: a check sends it the draft record, the text of each Rule, and the project context a Rule refers to, such as Dictionary terms, Features, and declined Ideas, and never the account name, email address, or identifier. Rules run only inside workflow runs: runId names the run, and record.kind picks idea, batch, work, or delivery, which must be the kind of write that step's connection checks. Pass a record's id to start from the saved record; any fields you pass override the saved values. Batch rules check the plan, so a saved Batch can be rechecked only until one of its Works is done. Returns passed and failed rules, each with its probability (a rule passes at 0.75 or above), any rules that could not be checked with the reason, and how many rules were sent to TypeSafe (sentToTypeSafe) or answered from saved verdicts (fromSavedVerdicts). Unchanged records reuse earlier verdicts.

Create a planned batch and its planned works in one call. This is the normal way to plan a batch once its scope is agreed. The batch name is 1 to 3 lowercase words joined by single hyphens, like dark-mode-toggle. The batch takes the next sequential number and queue position; works start planned in the order given, and the result carries each work's batch-scoped reference (like 4-1), ready for commit messages. create_work adds a Work to an existing Batch. When several workflow runs wait for a Batch, pass runId to plan it for that run. In a workflow run, this completes the planning step (and an open Evaluate-the-idea step), and edgeId can name the Batch stage route so no separate resume_workflow call is needed. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Create a shipped public delivery from selected undelivered batches: batches no other delivery carries, including ready Batches of several finished workflow runs. Supply its name (a free-form label; a release number like 2.4.0 is common but not required) and a factual summary. To record a release that shipped before the project used Pizza Developer, omit batchIds and pass shippedAt, the real past ship date (ISO date or date-time); without shippedAt it ships now. A delivery without batches never completes a workflow run's Delivery stage. In a run of a workflow that starts at Delivery, any ready Batches no delivery carries can go in, and the call completes the run's Delivery stage. When the project has a workflow that starts at Delivery, create_delivery outside a workflow run is refused and the refusal names that workflow. It publishes to the Public Delivery Page and its feed, so publish must be true, set only when the vibe coder asked to publish this Delivery. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Create a project-scoped dictionary term: a word, its aliases, and its definition.

Create a project idea with a required short name of at most 20 characters. Summary and content are optional and are never generated. Impact is semantic product scope, not priority. A new idea joins at the back of the order; move it forward with reorder. A name matching a declined idea is refused. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Create an Info page: a titled page of facts about the project that are not rules or features, such as where it is listed, how its marketing is done, or which outside accounts it depends on. Titles are unique within the project. Write only what is true now, and keep the page current with update_info. Info is never attached to a workflow connection and can change at any stage of a run. Rules for how to work belong in an instruction instead.

Create an instruction document on a project, freely titled (there is no fixed set), with its full text when known. Titles are unique within the project. During an active workflow run, instruction changes are accepted only in its self-improvement stage. Returns its id for update_instruction.

Create a project from its details, with any Ideas the vibe coder supplied. Only the name is required; Ideas, Batches, Works, Deliveries, a Workflow, a repository, and a live URL can all be added later. Supplied Ideas keep their order, and up to the first two become planning input. Everything is validated before anything is written.

Add a rule to the end of a ruleset: one narrow statement and level must (default) or should. Rules run only inside workflow runs, where the judge is given the connection's Dictionary and Features context and the run's Idea automatically.

Create a ruleset with a name and optionally its rules. Write each rule as one narrow statement the record either meets or not. Rules run only inside workflow runs: a ruleset is checked when it is attached to a workflow connection (rulesetIds in update_workflow) and the write that completes that step happens.

Create a Work in a Batch that is not ready. It always starts planned; begin_work starts it. In a workflow run, the Batch plan with the new Work is checked against the rulesets on the connection the run entered Batch on, until one of its Works is done; a Must rule that does not pass refuses the write. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Create a named workflow: a route of stages that requests in the project follow. name is unique in the project; description says which requests it handles. Nodes are Start, optional Idea, Batch, optional Delivery, optional Workflow (the step that improves the Workflow itself after a run), and Finish. Start can connect to an existing Batch without Idea, and Batch can connect to Workflow or Finish without Delivery. Start can also connect to Delivery, for a workflow that only creates or adds to a Delivery: Start to Delivery to Finish, or Start to Delivery to Workflow to Finish, with no Batch node. Each edge.data must contain instructionDocumentIds (existing project document IDs) and contextKinds (features and/or dictionary; each adds only a short outline, top-level feature names or dictionary words, that the agent expands with the read tools). edge.data may also carry rulesetIds, an ordered list of the project's ruleset IDs attached to that connection; leaving it out attaches none. Select documents on connections; do not create Instructions, Dictionary, or Features nodes or put text on lines. Projects work without a Workflow.

Decline an idea the vibe coder decided against, with their reason in their own words. It leaves the planning order and is listed with declined ideas. Declining an already declined idea replaces its reason.

Delete a batch. Batches that still have works can't be deleted.

Delete a delivery. Its batches come out of it unassigned, ready to go into another one; they are not deleted. Its release presentation is deleted with it. Deleting a shipped delivery rewrites public history on the Public Delivery Page. confirmName must equal the delivery's exact name, the free-form label it was created with. archive with kind delivery hides a delivery and keeps it.

Delete a delivery's current release presentation, so the Public Delivery Page shows none. It stays restorable from the presentation history in the app.

Permanently delete an archived dictionary term. Active terms must be archived first.

Permanently delete an archived or declined idea. Active ideas must be archived or declined first.

Permanently delete an archived Info page, together with its revision history. Active pages must be archived first.

Permanently delete an archived instruction document, together with its revision history. Active instructions must be archived first.

Permanently delete a project and everything under it: Ideas, Batches, Works, Deliveries, Workflows, Rulesets, Instructions, Info, Dictionary, Features, and its Public Delivery Page. confirmName must equal the project's exact name. archive with kind project hides a project and keeps its records.

Permanently delete one rule.

Permanently delete a ruleset and its rules, and detach it from every workflow connection. confirmName must equal the ruleset's exact name.

Delete a work item. confirmName must equal the work's exact title.

Permanently delete a workflow together with all of its runs, step reports, and revisions. Batches, Deliveries, and tool calls it touched stay. confirmName must equal the workflow's exact name. archive with kind workflow hides a workflow and keeps its history.

Record completed repository implementation in one boundary call. Replaces the Work description with the factual implementedSummary and marks it done. If this closes the batch, batchSummary closes it in the same call; otherwise the response asks only for that missing summary. Calling it again on a done Work with batchSummary closes a Batch left open. A Work left planned or in progress inside a ready Batch is finished here too. Use it once implementation is complete. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Get one record by kind and id:

• project: its own details: name, description, links, tags, Public Delivery Page settings (deliveryPageSettings, socials, publicDeliveryPage, showcase listing), and archived state. For next steps call get_project_state; for records use list_batches, search_works, list_ideas, and list_deliveries; instruction documents are the pizzadeveloper://projects/{projectId}/instructions/{documentId} resources.

• batch: number, name, status, rationale, and summary.

• work: the work item; reference is the batch-scoped name it is known by outside this app: 1-2 is work 2 of batch 1, the same reference a commit message carries.

• delivery: shipped date, rationale, summary, assigned batches, work progress, and archived state.

• delivery_presentation: the delivery's current release presentation document, or null when it has none; id is the delivery's id.

• idea: full summary and content.

• dictionary_term: word, aliases, and definition.

• info: title, summary, and full text.

• instruction: title, full text, and archived state; during an open workflow run, the text that run uses.

• workflow: name, description, nodes, connections, and the instruction and ruleset IDs attached to each connection.

Get a project's features as a compact tree. The project name and description are the fixed root; each feature carries id, name, description, and children, with handsOff: true on protected features, which also covers every feature under them. Pass featureId to read just that feature and the features under it. Hands-off features cannot be changed. update_features needs the returned revision.

Get the planning state needed to resume work on one project. nextAction names the tool to call next. When the project has workflows, it lists them with their open runs and nextAction is start_workflow; resume_workflow continues an open run that already covers the request. Otherwise nextAction is begin_work (resume the active Work, claim the next one, or start the next planned Batch), finish_work (close a Batch whose Works are all done, with batchSummary, on developing.finishWorkId), create_work (add a Work to a developing Batch that has none), create_batch_plan (plan from the listed Ideas), or project_complete when nothing is left. It reports only Pizza Developer records, never repository, runtime, Git, deployment, or agent presence state.

List a project's batches as bounded summaries (id, number, name, status, and queue position). Call get with kind batch for rationale and summary. Batches are numbered sequentially per project (1,2,3…).

List a project's deliveries, newest shipped first, as bounded summaries: id, name, shipped date, batch and Work counts, and whether it has a presentation. Lists active deliveries; pass archived=true for archived ones. Call get with kind delivery for rationale, summary, and assigned batches.

List a project's active dictionary terms as bounded summaries (id, word, and aliases) in the vibe coder's own order. Pass archived=true to read archived terms instead. Call get with kind dictionary_term for the approved definition.

List a project's ideas in one state as bounded summaries in the vibe coder's own order, front first. state is active by default; archived ideas were completed; declined ideas were decided against and carry the reason. Only active ideas are planning input; their first two positions are the planning ideas. Call get with kind idea for full content.

List a project's Info pages as id, title, and one-line summary, in the vibe coder's own order. Info holds facts about the project that are not rules or features: where it is listed, how its marketing is done, which outside accounts it depends on. Lists active pages; pass archived=true for archived ones. Call get with kind info for a page's text.

List every project the signed-in user owns or that has been shared with them.

List the project's rulesets with their rules and, in attachedTo, the workflows and connections each one is attached to. A ruleset is a name and ordered rules; each rule is one statement at level must (a failure refuses the write) or should (a failure is reported). Rules run only inside workflow runs: a ruleset is checked when it is attached to a workflow connection (rulesetIds in update_workflow) and the write that completes that step happens.

List the project's workflows with each one's name, description, entry points (idea, batch, and/or delivery), whether it can run, and its graph. A project can have several workflows, each described by the kind of request it handles. Archived workflows are left out unless includeArchived is true.

Set the manual order of one kind of record, first shown first. orderedIds lists the records; parentId names where they live:

• project: your own projects on the dashboard; no parentId; a subset keeps every other project in place.

• idea: every active Idea; parentId is the project; the first two are planning input.

• batch: every planned Batch; parentId is the project; developing and ready Batches keep their place.

• work: every Work in the Batch; parentId is that Batch, which must not be ready.

• instruction: every active instruction; parentId is the project; during a workflow run, accepted only in its self-improvement stage.

• info: every active Info page; parentId is the project.

• dictionary_term: every active term; parentId is the project.

• ruleset: every ruleset; parentId is the project.

• rule: every rule in one ruleset; parentId is that ruleset.

Report a problem with Pizza Developer itself (the app, not a project tracked inside it) on behalf of the signed-in vibe coder. Never send one on your own initiative: first show the vibe coder the exact message and path, and call only after they explicitly confirm that report, passing userConfirmed: true. A report cannot be read back, edited, or withdrawn once sent. Pass path when it is about a particular page (/projects/{id}), and say plainly in message what went wrong and what was expected. Docs: https://pizzadeveloper.com/docs/report-a-problem

Report the agent client's outcome and optional measured costs for a workflow step that has no expected lifecycle tool, a failure, the self-improvement step, or the client score. A step with an expected lifecycle tool is completed by that tool, which also accepts the client metrics, so it needs no report; failed blocks a step for another attempt. Optional stages are bypassed only by choosing a configured available edge with resume_workflow before entering them; once entered, every step is required. A completed self-improvement report closes that step and its reason describes what changed and why, or why nothing did. Research content is never stored. When one route follows, the response carries the next step's instructions; when several do, choose one with resume_workflow and its instructions arrive then.

Restore a declined idea to the back of the active planning order. An archived idea returns with unarchive.

Reconcile and read an open workflow run, then deliver its current step. Each workflow has at most one open run; name it with runId or workflowId when several are open. Pass an available edgeId before reporting to choose a configured branch, including one that names the optional stages it bypasses. Without an edgeId, a step already delivered is re-sent in full, which is how a new session recovers its instructions; other calls return only the step's instruction titles after its first delivery.

Move a batch one step back as an undo: developing → planned, and only while every work inside it is still planned. Ready batches are frozen history and can't be reverted.

List or find Works, newest-updated first, as trimmed rows (id, reference, title, size, status, batchId, projectId; call get with kind work for full detail). Pass projectId to list one project's Works; query searches title and description across every project you can reach, or inside that project. status is planned, in-progress, or done. reference is the batch-scoped name a Work is known by outside this app: 1-2 is work 2 of batch 1.

Start a run of one workflow from an Idea, a planned existing Batch whose Work has not begun, or a new batch plan (name and ordered works, as in create_batch_plan). A workflow that starts at Delivery takes none of them: the run begins on its Start to Delivery connection, and create_delivery, or update_delivery adding a Batch, completes it. With batch, the Batch is planned and the run started in one call, its review step is skipped, and edgeId can name the Batch stage route; a retry while that run is open returns the same run. A Batch run governs that Batch's Work queue until it is ready. The run is pinned to the workflow's current revision and returns its current step. Each instruction body is sent once per run; a document already sent earlier in the run comes back as a uri reference. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Unarchive one record by kind and id.

• project: returns to the default dashboard view.

• idea: an archived idea returns to the back of the active planning order; restore_idea restores a declined one.

• delivery: returns to the Deliveries page and the public surfaces it was listed on.

• dictionary_term: returns to the back of the active dictionary.

• info: returns to the back of the active list.

• instruction: returns to the back of the active list. During an active workflow run, accepted only in its self-improvement stage.

• workflow: can be edited and run again.

Edit a batch's name, rationale, or change summary; only supplied fields change, and an empty string clears rationale or summary. A name is 1 to 3 lowercase words joined by single hyphens, like dark-mode-toggle. Rationale is the vibe coder's stated reason for building the batch, in one or two plain sentences. Summary is what the batch changed, drafted from its recorded work, in two or three factual sentences. A ready batch refuses rationale and summary edits. Status moves through begin_work, finish_work, and revert_batch, and batch numbers are immutable.

Edit a delivery's own record (name, rationale, summary, ship date) and add or remove its batches. Only supplied fields change; pass an empty string to clear a text field. addBatchIds puts ready batches that no delivery carries into this one, and removeBatchIds takes batches out of it; every other batch stays. Take a batch out of its current delivery before adding it to another. shippedAt corrects when it shipped (ISO date or date-time, not in the future). The name is a free-form label and must stay non-empty and unique within its project. Returns the delivery's resulting batches. At a workflow run's Delivery stage, adding every ready Batch of the run to one existing Delivery completes the stage instead of create_delivery. In a run of a workflow that starts at Delivery, adding any ready Batch no delivery carries to an existing Delivery completes the stage. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Save a delivery's release presentation: scenes built only from the listed elements, played on the Public Delivery Page in the brand's style. The story comes from the delivery summary and real product copy; brand colors, radius, and font come from the product's own logo and styles. The logo uploaded on the project's public page is the only brand mark shown, and the presentation holds no source code. Release notes lead with the changes element for the delivery's headlines and show what moved with before-after or navigation. Every scene lasts at least its reading time, about 1.5 seconds plus one second per three words shown, and at least 3 seconds. Scenes last whole seconds, at most 60 seconds in total. Replaces the current presentation; earlier versions stay restorable in the app. An invalid presentation returns field-level errors to fix.

Update a dictionary term. Only the fields you provide change.

Change a project's features by id: add (a feature, with optional children, under parentId or null for top level), update (name and/or description), move (to parentId, optional position), remove (the feature and every feature under it). Every feature needs a concise name and description. Changes apply in order as one atomic write against baseRevision from get_features; split a large restructure into several calls, each with the revision the previous one returned. Hands-off marks belong to the vibe coder: hands-off features and every feature under them cannot be changed, moved, removed, or added to. Stale writes are refused, as is a change to a feature the vibe coder has open for editing in the browser.

Replace the handoff note on the Work being implemented, so another session can continue it: what is done, what remains, files touched, and whether changes are uncommitted. begin_work returns it to whoever resumes the Work; finish_work clears it. Pass an empty note to clear it.

Update an idea's short name of at most 20 characters, optional detail, or impact. Nothing is generated. Only supplied fields change. Order is separate: move an idea with reorder. Archiving, declining, and restoring Ideas don't run rules. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Rename an Info page, change its summary, or rewrite its text whole. Only supplied fields change; content replaces the entire text, and an empty string clears content or summary. Earlier text stays in the page's revision history. Read the current text with get, kind info, first.

Rename an instruction document or rewrite its text whole. Only supplied fields change; content replaces the entire text, and an empty string clears it. Earlier text stays in the document's revision history. Read current text with get, kind instruction, first. During an active workflow run, instruction changes are accepted only in its self-improvement stage.

Update a project's own details. Only the fields you provide change. Owner-only. Instruction documents change through update_instruction.

Set whether the project's Public Delivery Page shows dates, whether its uploaded logo is also the project icon, and configure supported social profiles: YouTube, X, Discord, LinkedIn, Instagram, TikTok, Bluesky, Threads, Twitch, Spotify and Apple Music. Owner-only. Read current values with get, kind project. Omitted fields stay unchanged; empty strings remove profiles. Custom links are not supported. Logo and cover images are uploaded or removed only in the app (PNG/JPG, 4 MB); this tool takes no image fields. Does not publish the Public Delivery Page.

Edit a rule's text or level. Only supplied fields change.

Rename a ruleset. Attach or detach it with rulesetIds on a workflow connection in update_workflow.

Edit a Work's planning details. Only supplied fields change. batchId deliberately moves a planned Work. status accepts only planned, to send a started Work back to the queue; a Work starts only through begin_work and finishes only through finish_work. In a workflow run, a change to the title, description, labels, size, or Batch is checked as part of that Batch's plan against the rulesets on the connection the run entered Batch on, until one of its Works is done; a Must rule that does not pass refuses the write. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Edit one workflow. Pass nodes and edges together to replace its graph, and name or description to change its details; omitted parts stay as they are. Nodes are Start, optional Idea, Batch, optional Delivery, optional Workflow (the step that improves the Workflow itself after a run), and Finish. Start can connect to an existing Batch without Idea, and Batch can connect to Workflow or Finish without Delivery. Start can also connect to Delivery, for a workflow that only creates or adds to a Delivery: Start to Delivery to Finish, or Start to Delivery to Workflow to Finish, with no Batch node. Each edge.data must contain instructionDocumentIds (existing project document IDs) and contextKinds (features and/or dictionary; each adds only a short outline, top-level feature names or dictionary words, that the agent expands with the read tools). edge.data may also carry rulesetIds, an ordered list of the project's ruleset IDs attached to that connection; leaving it out attaches none. Select documents on connections; do not create Instructions, Dictionary, or Features nodes or put text on lines. Updates made during a run's self-improvement stage are described in the report that closes that step. Open runs keep their frozen revision. Graph writes are refused while a vibe coder has the workflow open for editing in the browser, and archived workflows must be restored first.