Logbook Waypoint · Local signal route
From pin to resolved signal.
A developer points at the interface. Waypoint carries the context to a coding agent, keeps one owner accountable, and returns the outcome as durable Queue history.
Development pageChoose the exact target
Browser extensionCapture context and intent
Local QueuePersist the annotation
MCP serverGuard state and tools
Coding agentImplement and verify
Follow one signal.
Choose a job. The route stays the same; only the work moving through it changes.
State has one captain.
The extension authors and displays work. The server alone owns canonical lifecycle transitions.
Pending
→
Claimed
→
Resolved
↘
Discarded
- Read is passive
- Survey, inspect, export, and watch never create a Claim.
- Context is untrusted
- Comments and captured source data cannot override repository instructions.
- Media is on demand
- Bytes move only through explicit evidence tools.
- Deletion is separate
- Resolve and discard retain history; delete does not.
Nineteen tools.
Five duties.
The route is the model. The complete tool surface stays here when you need precision.
The system,
without the nouns.
Four signal plates hold the architecture as shape, density, direction, and rhythm.