In flight
Active workstreams
Each card below is a real, scoped piece of work that is either in progress or next-up in the queue. They are listed in priority order.
A
Catalog freshness
Keep this static site aligned with service behavior, especially when endpoints, workflows, or operator capabilities change. Treat the site as code: PR-reviewed, versioned, deployed alongside the services it documents.
B
SOD deep-doc
Son of Duplo is the least-documented service. Code-level analysis of the EC2 + Kameleo + Playwright stack is the next priority — fingerprint config, scaling model, observability via Amazon DCV.
C
Inbound classification
Beyond contract PDFs — interpret and route arbitrary client emails (intent extraction, response routing) back into the pipeline. This unlocks event-confirmation conversations and unblocks Pillar 4 work upstream.
D
Trigger engine layer
A first-class trigger engine sitting above the data layer — event signals fire playbooks across services with explicit decisioning and observability. Replaces the implicit scheduling currently scattered across cron and pollers.
E
Contract intelligence & negotiation
Move the agent from passive intake to active negotiation. Draft and counter-offer offline block contracts directly with hotels (rate, commission, cut-off, attrition); raise and confirm amendments on already-live online blocks (rate changes, room-count adjustments, deadline extensions); reason over historical contract terms and pickup data to inform every offer.
F
SOD-driven hotel bookings
Wire the Son of Duplo booking worker (sodr-booking + sodr-booking-api) into the live Magellan flow. When a guest books on a Magellan-managed page, the fleet completes the reservation on the hotel’s own site end-to-end, captures the confirmation, and reports it back through the booking pipeline — closing the loop from contract to confirmed stay.