Compare access-first and capacity-first branches

Create both strategies

{
  "tool": "venue.create_proposal_branch",
  "input": {
    "name": "Access first",
    "strategy": "access-first",
    "goal": "Maximize accessible route clearance",
    "idempotencyKey": "tutorial-access-branch-001"
  }
}

{
  "tool": "venue.create_proposal_branch",
  "input": {
    "name": "Capacity first",
    "strategy": "balanced",
    "goal": "Increase usable seating without reducing required clearances",
    "idempotencyKey": "tutorial-capacity-branch-001"
  }
}

Develop and validate independently

1. 1Switch to Access first, preview its goal, and call venue.validate_layout.
2. 2Switch to Capacity first, preview its goal, and call venue.validate_layout.
3. 3Keep both Branch IDs and Validation fingerprints.
4. 4Do not reuse one Branch result as evidence for the other.

Compare evidence

Use the Branch IDs returned by the two create calls. In a fresh seeded Project they are branch-2 and branch-3.

{
  "tool": "venue.compare_proposal_branches",
  "input": {
    "leftBranchId": "branch-2",
    "rightBranchId": "branch-3"
  }
}

• Review capacity, access width, circulation, egress, sightlines, risk, inventory cost, and Constraint deltas.
• Open Plan history → Branches → Compare to inspect the spatial overlay.
• Enter a decision note and choose the evidence-backed Branch.

Completion criteria

• Both Branches retain independent Changes and Validation results.
• The chosen and rejected Branch IDs, comparison fingerprint, and rationale appear in the Activity Ledger.
• The accepted Plan remains unchanged until a separate human Approval.

Verify the workflow

Run the executable fixture from the repository root. Completion requires a zero exit code.

node --test tests/venue-planner.test.mjs