How sudheerdvn/lanegate works
LaneGate coordinates coding agents through a ticket-centered workflow: scope work, assign isolated worktrees, execute and inspect changes, require review and guards, then merge and optionally promote. Markdown tickets are the project-state source of truth; operational artifacts remain local. The graph also includes documented MCP and terminal-UI access, safeguards, and deployment promotion. API and several feature modules are represented from the tree and README capabilities; their internal wiring was not sampled, so uncertain call paths are omitted.
Main entry points: loop.py Orchestration loop · ticket.py Markdown tickets · cli.py Command-line interface · merge.py Merge and recovery
Components 21
Ticket workflow
- Markdown tickets
lanegate/ticket.py - Scoping and analysis
lanegate/analyze.py - Worktree isolation
lanegate/worktree.py - Lifecycle commands
lanegate/lifecycle/core_cmds.py
Coordination and gates
- Touches and locks
lanegate/lifecycle/touches.py - Orchestration loop
lanegate/orchestrate/loop.py - Executor dispatch
lanegate/executor.py - Pool routing
lanegate/config_routing.py - Configuration
lanegate/config.py - Safety checks
lanegate/safeguards.py - Independent review
lanegate/orchestrate/review.py
Merge and delivery
- Merge and recovery
lanegate/lifecycle/merge.py - Staged promotion
lanegate/promote.py - Local run records
lanegate/context_log.py
User interfaces
- Command-line interface
lanegate/cli.py - MCP tools
lanegate/mcp.py - Loopback API
lanegate/api.py - Terminal UI
tui/internal/app/update.go - UI API client
tui/internal/client/client.go
Other components
- Operator
- Coding agent
Connections 28
- Operator → Command-line interface: issues commands
- Coding agent → Command-line interface: requests work
- Command-line interface → Scoping and analysis: analyzes requests
- Scoping and analysis → Markdown tickets: creates ticket specs
- Command-line interface → Orchestration loop: starts runs
- Orchestration loop → Markdown tickets: reads and updates
- Orchestration loop → Pool routing: resolves executor
- Pool routing → Configuration: reads settings
- Orchestration loop → Worktree isolation: assigns isolated worktrees
- Orchestration loop → Touches and locks: checks file ownership
- Orchestration loop → Executor dispatch: dispatches tasks
- Executor dispatch → Coding agent: runs agent process
- Coding agent → Worktree isolation: edits ticket work
- Orchestration loop → Safety checks: runs configured checks
- Orchestration loop → Independent review: dispatches review
- Independent review → Markdown tickets: records verdict
- Operator → Lifecycle commands: manages ticket state
- Lifecycle commands → Markdown tickets: updates status
- Operator → Merge and recovery: requests merge
- Merge and recovery → Markdown tickets: records merge state
- Merge and recovery → Worktree isolation: removes worktree
- Operator → Staged promotion: promotes release
- Orchestration loop → Local run records: logs run costs
- Operator → MCP tools: uses native tools
- MCP tools → Lifecycle commands: invokes commands
- Operator → Terminal UI: views run and board
- Terminal UI → UI API client: requests data
- UI API client → Loopback API: fetches API data