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:

​
Source-implemented maintenance-task creation

Engine Development source at 9a15b1da199923d1ecb0927be2507feda2cb4c71 implements linked operational-task creation when maintenance intake resolves a booking. No fresh provider delivery or end-to-end task-creation interaction was performed on 2026-08-12. The source-implemented task contract preserves:

​
Source-implemented task classification

Accepted maintenance intake becomes a maintenance-repair task without changing unrelated booking or guest truth.

​
Source Tracking

The source-implemented contract records that the task came from accepted maintenance intake and that automation created it. This provenance preserves traceability from an accepted signal to an operational task. Its presence does not prove that a provider delivered a new signal or that the task was created in a live operator workflow.

​
Routing Goal

Every operational task should be routed to the correct lane. Maintenance tasks should surface in the property-operations maintenance lane. The Focus Ops source contract verified on 2026-08-12 assigns the Dynamic Action Workspace as the default destination for structured actions. Specialized pages may remain supporting or future-specialized surfaces; they are not the default destination. Plain-language routing contract:
Infinite CTA languageResolver Matrixfinite Action Workspaceoperator can actually do the thing
CTA label is copy. Machine-readable action semantics are routing truth. Durable routing doctrine treats DAW as the action/save surface rather than a copy-to-clipboard scratchpad. A normal DAW workflow should have one of these persistence targets:
DAW copy implemented in the audited Admin source and recorded at the 2026-05-29 Development checkpoint:
The 2026-05-29 Development checkpoint recorded saved workflow state returned through the bounded operator-workspace contract. Durable doctrine remains that 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

Durable Focus Ops routing doctrine:
Calendar / booking spineBooking PulseSignal StreamGuest Signal review/link surface when relevantLucia Workspace / Focus with LuciaResolver MatrixDynamic Action Workspace action/save surface
The Focus Ops source contract verified on 2026-08-12 requires named guest, service, or request scope to override generic ranking and survive routing. 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. Durable routing doctrine assigns Calendar booking review to the Full Booking Page, not DAW. That click behavior was recorded at the 2026-05-26 Development checkpoint and remains implemented in the audited Admin source; no fresh authenticated click was performed on 2026-08-12. Cockpit doctrine:

​
See Also