etAI: AI dispatcher for the trades.

AI Tinkerers Seattle Hackathon 2026 · Hackathon page · Ambiguous.ai

theme

Agents are leaving the chatbox. Build an agent for a place people already work, talk, or live, then make it meaningfully more useful because of that context. Put it into the web, mobile, Slack, Teams, messaging, browsers, voice, wearables, robotics, or somewhere nobody expects to find one yet. What becomes possible when the agent shows up where the work is already happening?

A dispatcher you text. Contractors and clients book, reschedule, and cancel appointments over iMessage, SMS, and calls; an Ambiguous.ai workspace is the calendar of record. A FaceTime-style web app (frontend/) lets users call their agent directly.

demo

click here for slides

layout

• messaging/: messaging service (iMessage/SMS in and out)
• bus/: the scheduling brain; answers texts via Ambiguous
• calendar-agent/: Ambiguous Assistant chat smoke script
• frontend/: the call-your-agent web app
• shared/: zero-dep helpers shared across services
• models/: JSON schemas for every wire shape
• docs/: all documentation
• bus/, user-interface/: reserved, empty (frontend/ is the real UI)

docs

• Product goal: the contractor-dispatcher problem, the five-whys rationale, MVP behavior, scope, risks, and demo framing.
• Architecture: how messaging, the router, calendar integration, and call UI exchange data today and where the planned flow differs.
• Interfaces: component ownership, shared contracts, build order, and environment-variable registry.
• API: agent endpoints, tools, data model, message flows, Ambiguous mapping, and operational gotchas.
• Calendar contract: availability and event CRUD contract, errors, conformance checks, and calendar-provider options.
• Phone contract: normalized inbound-message and outbound-send boundary shared by messaging consumers.
• Bus service: bus-core modules, HTTP routes, intent handling, state, and voice-turn behavior.
• Messaging service: running the phone service, transports, subscriptions, mail polling, configuration, and iMessage caveats.
• Messaging behavior: client, contractor, and time-triggered flows, notification rules, and the seeded demo sequence.
• Messaging integration plan: verified real-SMS path, one-brain routing rule, remaining tasks, and field-tested gotchas.
• Calendar agent: direct MCP calendar integration, strict booking/rescheduling inputs, and Assistant timeout tradeoffs.
• Calendar notifications: reminder polling through the bus to contractor texts, including delivery and dedup behavior.
• Ambiguous integration: verified workspace endpoints, authentication, frontend use, platform limitations, and rejected approaches.
• External integrations: integration map and the single Ambiguous boundary owned by each component.
• Frontend: call-your-agent UI flow, offline behavior, implementation ideas, and roadmap.
• Setup: workspace provisioning, CLI authentication, Make targets, demo command, tests, and hooks.
• Dispatch prompts: coordinated implementation brief for the trade-job management-console direction.
• Project plan: high-level build plan, decisions, and lessons learned for the text-to-calendar loop.
• Logo explorations: preview page for the ETAi wordmark and icon variants.

quick start

cd frontend && npm install && npm run dev   # see docs/frontend.md
node messaging/index.js                     # see docs/messaging.md
node bus/index.js                         # see docs/bus.md