Skip to main content
Task creation turns an incoming operational signal into trackable work.

​
Purpose

A message is not enough. Lucia must help convert real-world reports into: 
structured tasks
clear ownership
operational lanes
visible next action
privacy-safe guest signal review

​
Current Maintenance Task Creation

When a maintenance inbox message includes a resolvable booking ID, Lucia can create a linked operational task. Task properties include: 
task_id
booking_id
task_type
title
status
priority
source
source_reference
maintenance_state

​
Current Task Type

maintenance_repair

​
Source Tracking

Maintenance-created tasks use: 
source: maintenance_inbox_webhook
created_by: webhook:maintenance
This preserves traceability from external signal to operational task.

​
Routing Goal

Every operational task should be routed to the correct lane. Maintenance tasks should surface in: 
maintenance_property_ops
Every structured Focus Ops CTA should route to a focused operator action workspace. /ops/actions is the default universal Dynamic Action Workspace. Specialized pages may remain available as supporting or future-specialized surfaces, but they are not the default Focus Ops CTA destination. Plain-language routing contract:
Infinite CTA languageResolver Matrixfinite Action Workspaceoperator can actually do the thing
CTA label is copy. Structured action intent and metadata are routing truth. DAW is now the action/save surface, not a copy-to-clipboard scratchpad. Normal DAW workflows require a persistence target: 
task-backed save
concierge request save
booking-note-backed save
insufficient-context bridge/fallback
Current DAW copy: 
Primary button: Save this step.
Saved confirmation: Saved.
Saved workflow state may be sent back to Lucia through active_context.workspace, but saved state must not be described as resolved operational state. Guest operational signals are different from verified booking tasks. Candidate or unlinked guest signals should route to review/link language, not fake DAW work.

​
Focus Ops Integration

Current live-dev doctrine:
Calendar / booking spineBooking PulseSignal StreamGuest Signal review/link surface when relevantLucia Workspace / Focus with LuciaResolver MatrixDynamic Action Workspace action/save surface
Named guest, service, or request prompts must preserve that scope through routing. The current Engine scoped entity fix means named scope should override generic ranking. Guest signals must also preserve identity/linkage scope. Service overlap is never identity evidence, and candidate/unlinked guest signals must not drift into similar existing bookings. Calendar booking clicks are different: they route to the Full Booking Page at /bookings/:bookingId for record/review, not to Dynamic Action Workspace. Current cockpit doctrine: 
Lucia Workspace + DAW = cockpit
Full Booking Page = record/review surface

​
See Also