/sandbox

Interactive governance demo — creates a real GitHub project with algorithmically generated governance scenarios, then discovers them live using the same tools that govern real projects.

Invocation

/ido4dev:sandbox

How It Works

The sandbox uses a pipeline-based creation process:

1. A technical spec (methodology-specific) defines capabilities, tasks, and dependencies
2. The ingestion pipeline parses it into structured data — same pipeline used for real projects
3. The ScenarioBuilder algorithmically generates the full scenario: assigns containers, distributes task states, embeds violations, seeds audit events, registers agents, and creates context comments
4. Everything is created as real GitHub issues in a real GitHub Project V2

This means sandbox scenarios aren’t hardcoded test fixtures — they’re generated by the same infrastructure that governs real projects. The violations are embedded algorithmically based on the scenario’s narrative and the methodology’s integrity rules.

What It Creates

Component	Details
GitHub Issues	Tasks with full governance fields, dependencies, and container assignments
Parent Issues	Capabilities as epics (Hydro/Scrum) or bets (Shape Up)
Execution Containers	Waves, sprints, or cycles — methodology-specific
Pull Request	For review bottleneck detection
Audit Events	Realistic temporal distribution for analytics
Agents	Registered with role and capabilities
Context Comments	Structured ido4 context blocks on key tasks

Embedded Governance Violations

Each methodology scenario embeds violations that governance tools discover:

• Cascade blocker — A critical-path task blocking multiple downstream tasks
• False status — A task in “In Review” with no linked PR
• Review bottleneck — A PR open for days with zero reviews
• Integrity violation — A grouping container split across execution containers (epic across waves, bet across cycles)
• Stale work — A task in progress too long, high effort and risk

The specific violations and their narrative context vary by methodology — Hydro scenarios embed epic integrity violations, Shape Up scenarios embed circuit breaker pressure, Scrum scenarios embed DoR violations.

Demo Flow

Phase 1: Setup

Creates the sandbox via the ingestion pipeline + ScenarioBuilder (2-3 minutes).

Phase 2: Live Governance Analysis

The skill runs governance tools and narrates each finding:

• Container status overview
• Cascade blocker discovery via analyze_dependencies
• Review integrity check via find_task_pr + get_pr_reviews
• Integrity analysis via container grouping
• Work distribution via get_next_task for both agents
• Merge readiness gate via check_merge_readiness

Phase 3: BRE Enforcement Gauntlet

Demonstrates that governance is enforcement, not just visibility:

• Shows all transitions blocked for a blocked task (except unblock)
• Shows valid transitions allowed for a ready task
• Proves the BRE is deterministic and cannot be bypassed

Cleanup

• Keep — Continue experimenting with other skills
• Reset — Destroy and recreate fresh
• Destroy — Close all issues, delete PR, remove project

Three Methodologies, Same Infrastructure

The sandbox works identically for Hydro, Scrum, and Shape Up. The ScenarioBuilder reads the methodology profile and adapts:

Element	Hydro	Scrum	Shape Up
Execution container	Waves	Sprints	Cycles
Grouping container	Epics	Epics	Bets
Integrity violation	Epic across waves	—	Bet across cycles
Methodology-specific	Wave singularity	Type-scoped DoR	Circuit breaker countdown

Related Skills

• /ido4dev:onboard — Zero-friction first touch: auto-clones demo codebase, creates sandbox, guided discovery
• /ido4dev:guided-demo — Four-act governance walkthrough over an active sandbox
• /ido4dev:sandbox-explore — Interactive exploration: 13 structured paths across governance capabilities

Use Cases

• Onboarding — New team members experience governance firsthand
• Sales demos — Show governance to potential clients/investors
• Skill testing — Validate skills against a known scenario
• Training — Practice governance workflows in a safe environment