Skip to main content
Lucia Fieldwork is the employee-first, mobile-first companion for maintenance and housekeeping capture. You tell Lucia what you observed in natural English, answer focused questions, review the structured issue draft, and choose when to submit it. If you would rather not chat, you can fill in the same issue form yourself on the Log Issues Manually page. It is not a general chatbot or an owner console. Before you use the designated confirmation control, the conversation and its issue drafts remain work in progress.
Lucia Fieldwork is a production employee application under active development. The app is at luciafieldwork.ai, served from Cloudflare Pages (GitHub-backed on the app’s main branch), and its authenticated API is at api.luciafieldwork.ai. Sign-in is Clerk; older notes that describe Cloudflare Access as the security layer are historical.

Log and track an issue

Describe what happened, review Lucia’s draft, attach photos, and explicitly submit it.

Log Issues Manually

Fill in the issue form yourself, with no chat, and edit any saved draft on the same page.

Tips and guides

The six in-app tips, how they dismiss, and how to replay them.

Messages and replies

Follow a submitted item’s employee-to-operator thread, including Sent, Seen, and reply-needed state.

Understand owner review

See where Fieldwork ends and Lucia’s downstream owner and operator workflow begins.

​
How Fieldwork works

1

Talk to Lucia

Describe a maintenance or housekeeping problem as you would to a capable teammate. Lucia can ask for missing details and preserve uncertainty when you do not know something.
2

Shape the right drafts

Lucia grounds each draft in what you reported. If one conversation contains several independent problems, Fieldwork can keep them as separate issue drafts.
3

Review the current issue

Check the title, location, description, severity, guest impact, photos, and any employee-reported estimate or approval request before you continue.
4

Submit explicitly

Only the designated confirmation and Submit to Lucia controls can begin canonical item creation and delivery. A typed “yes” does not submit, approve, assign, or schedule work.
An acknowledged submission becomes a canonical maintenance record. A conversation, saved draft, or draft-ready state does not enter the Maintenance Inbox, Signal Stream, or other operator workflows.

​
The loop, as it shipped

A Fieldwork submission travels the app → the Fieldwork API → the Lucia Booking Engine → the admin’s Maintenance Inbox. That full chain was first proven end to end in the Wave 4 testing session on 2026-08-10: submissions from a fresh test account arrived in the Maintenance Inbox with photos, the Lucia Fieldwork channel attribution, structured triage suggestions, and a working approval-request plate (Wave 4 landed — enable replies, FILD-58). The reply leg of that same Wave 4 record remains Planned, not shipped: the record still carries an open founder verification checklist on the live surfaces (comment of 2026-08-29) and has not been closed. Separately, the per-item message thread between the reporting employee and the operator was built and founder-verified on 2026-08-19 (Inbox replies reach the reporter, FILD-77); see Messages and replies. A conversation the owner starts without an issue behind it does not exist yet and is Planned (FILD-167, 2026-09-09).

​
What is available now

Fieldwork opens directly into the full-height chat. On a cold open, the Lucia Orbit loader spins from its first frame, then kicks, releases, and fades into the empty chat and its docked composer (Cold open takes the baton, FILD-85, founder-completed 2026-09-05). There is no intermediate home panel, and no tip decorates the clean home on launch. Starting New or New Chat is immediate and does not open a confirmation modal. Earlier work is preserved as a titled draft, the composer clears, and the app returns to the empty chat. Drafts is the standing route back to that work; each row opens the exact named record on the first tap. Drafts persist until you deliberately move them to Deleted, and deleted drafts remain restorable. After the API acknowledges a submission, the success sheet stays in place until you choose Log another or Done. Reopening that record shows submitted truth rather than a stale draft-ready state. Submitted items can carry a direct employee-to-operator message thread. See Messages and replies.

​
Who owns each part

The browser talks only to the authenticated Fieldwork API and to upload URLs issued by that API. It does not call the Booking Engine or the model provider directly. Clerk organization membership binds each signed-in employee to the authorized property on the server; a property identifier sent by the browser is never authority on its own.

​
Current routes

Read from the app’s router at main@692a71c: Any other path falls through to the home route. Older Items and Review routes are not current Fieldwork destinations. The drawer behind the hamburger menu carries these rows, in the app’s own words: Log Issues with Lucia, Log Issues Manually, Drafts, Submitted Issues, Recurring Issues, Refresh, New Chat, Learn about Lucia Fieldwork, Replay the guides, and Account.

​
Build identity

Fieldwork does not use one global product version to identify current reality. Each repository is identified by its full source commit, while a live deployment requires separate provider evidence for the deployed commit. The App shows a short build commit for orientation; that label does not identify the API or Booking Engine.

​
Verification basis

Verified on September 10, 2026 against the evidence named in this page’s metadata. The routes, drawer rows, host, and tip pattern are read from the app source at 692a71c, the build the served bundle carried on that date. The messaging round trip is bounded to the founder-recorded proof of 2026-08-19. Nothing on this page certifies future changes, In Review work, or unrelated operator actions.