Connecting to live events…
Buildings are 3D meshes with shadows, concrete and brick façades, steel roofs, icons and shop signs. Shift-drag or right-drag rotates the camera; Tilt changes its elevation. Full names stay in the inspector; short signs become legible when you zoom in. Each island groups a machine or shared-service area, sized for its number of buildings. Host placement does not mean exclusive pipeline membership. Neo is the decision authority; the central MBP cockpit is his current operator seat. Siti routes its conversation lane, while MCP tools, application APIs and schedules provide other entry paths. Automation follows its own triggers and applicable policy. This map observes those systems; it does not dispatch jobs. Buildings represent current registry entries and clearly marked service landmarks. Landmarks such as Studio, GitHub and neo-brain are excluded from registry counts. Icons identify each building’s function.
Registry and recent command history refresh every 30 seconds. Live harbour watches eighteen metadata feeds across Siti, all fleet commands and intents, Studio content, review gates, render jobs, publishing, schedules, sessions, tools, memory and health reports. Work feeds target 2–6 second polling; registry and health target 30 seconds. Coverage shows feed freshness and observation gaps. The Operators tab observes local Claude Code and Codex turns and tools on this MBP. Local sessions target two-second polling; newly created logs can take ten seconds to be discovered. Content stages still require their Studio records. Fresh execution makes windows glow and pulse slowly. No observed work leaves windows dark; waiting uses an amber indicator. Delayed execution is unconfirmed, not offline. Reduced motion keeps working lights steady. Heartbeat freshness reports when a signal arrived; it is not a service health check. Saved snapshots retain their timestamps.
The process atlas explains inputs, handoffs, choices, review gates and outputs. Each route has source notes distinguishing code review, documentation and registry roles. Coverage counts entries linked to a route; it does not certify every running process.
Yachts illustrate the process tours. They sail between island docks and stay moored during same-island work and review gates. These tours are simulations. Rooftop residents represent observed sessions and processes, with up to six visible on one building. Hover a resident to identify its record. Fresh work enables dancing, stretching or strolling; monitoring records use binoculars. Idle residents rest. Named balloons represent external providers such as Higgsfield, fal.ai, ElevenLabs and Twilio. Connection lines require recorded provider usage; generic shell calls may not identify their provider. Yachts carry navigation lights and a night water glow. Local activity does not spawn a courier. Observed workspace reads use a timestamped dashed relationship arrow, not a third session or a job handoff. In Live harbour, fleet couriers walk from buildings to jetties, yachts sail between islands, and couriers continue to the destination building. Same-island handoffs stay on foot. The route banner shows each phase. Replay route animates a labelled copy of a recorded event without rerunning its job. Actual recorded statuses set the outcome. Boat travel is illustrative, not a measure of execution progress. Disconnected sources pause movement. “Reply recorded” is a router outcome, not a delivery receipt. Tour controls are previews. They never submit jobs or approvals. Live harbour carries metadata only; message text, replies, sender identities and job payloads are excluded. Archived entries remain searchable.