DOCS

VenueMindDocs

Open Studio llms.txt Schemas

Start

Venue planning, built for agents and humans Quickstart

Build

Tutorials

Create your first Project Run the supervised planning loop Compare access-first and capacity-first branches Resolve a stale Proposal Audit an approved Plan Version Install the VenueMind MCP server Use VenueMind through native WebMCP Install and invoke VenueMind agent skills Import, validate, and export a venue plan Recover from offline local state

Agents

WebMCP tools MCP server Agent skills Client examples

Reference

Tool reference Command reference Error catalog Constraint and evidence reference Activity Ledger events Plan and Proposal lifecycle Persistence and recovery Authorization reference Compatibility and deprecation Architecture and contributing Schemas and contracts Documentation changelog Safety and supervision

Trust

Privacy notice Preview terms Trust and safety

State semantics

Plan and Proposal lifecycle

Branch, rebase, conflict, Approval, adjustment, undo, redo, and replay behavior at the shared command boundary.

Project schema 10Ledger schema 1

operators · developers · agentsReviewed for VenueMind 1.0.0

Accepted truth

One immutable Plan Version is accepted truth.
A Proposal names exactly one base Plan Version and contains stable Changes.
Branches isolate competing Proposal revisions; switching a Branch never changes the accepted Plan.

Rebase and conflicts

Conflict detection covers stale base, deleted dependency, Lock, same-object edit, geometry overlap, and Constraint regression.
Rebase retains unchanged Change IDs and creates new IDs only for transformed Changes.
Human conflict decisions use only the published outcomes for each conflict and trigger fresh Validation.

Approval

Approval requires a matching Proposal ID and base version, passing hard Constraints, warning dispositions, and any required Emergency Review.
Approval is human-only and creates exactly one immutable Plan Version plus one ledger transition.
Agent tools stop at validated human review.

Undo, redo, and replay

Proposal editing undo and redo create reviewable Proposal revisions.
Accepted Plan undo and redo restore immutable prior versions and append ledger transitions.
Replay reconstructs accepted history without trusting cached summary fields.

Related contracts

Proposal conflicts Proposal comparison Command receipt

PreviousActivity Ledger events NextPersistence and recovery

On this pageAccepted truth Rebase and conflicts Approval Undo, redo, and replay Related contracts