Find a reply
1
Open Submitted Issues
Use the drawer’s Submitted Issues row. An amber count shows how many submitted items
need your reply, and the same count sits as a small badge on the hamburger menu button,
visible even on the empty chat home. The Submitted page also places those items in a
Needs your reply section at the top.
2
Open the submitted item
The item shows the employee and operator messages in one chronological thread. A cold-open
notice may also point you to waiting replies; V1 notifications appear only in the app on
open or refresh.
3
Read the delivery state
Sent means the message was accepted for delivery. Seen means the other party’s seen
cursor has reached it. Neither label proves that anyone approved, assigned, scheduled, or
completed the maintenance work.
4
Reply while online
Type and send from the submitted item. V1 has no offline queue: if the app cannot send, it
must say that the reply was not sent instead of displaying false success.
Thread and access boundaries
The operator’s visible name comes from a real Clerk identity. A missing trustworthy name must
not be replaced with a fabricated operator identity.
What does not exist yet
- An owner-started conversation. There is no door for the owner to open a conversation with an employee that no issue started. That change is Planned as a spec phase (Owner starts a staff conversation from Maintenance inbox, FILD-167, 2026-09-09); nothing on this page should be read as that feature.
- The Wave 4 reply record. The Wave 4 session of 2026-08-10 proved the submission chain (the app → the Fieldwork API → the engine → the Maintenance Inbox) but found the inbox reply composer dead-ended. That record (Wave 4 landed — enable replies, FILD-58) remains Planned with an open founder verification checklist dated 2026-08-29. The per-item thread described on this page comes from the later, founder-verified proof of 2026-08-19 (FILD-77); the Wave 4 record is not closed by this documentation.
What a message does not do
A reply can clarify the report. It does not itself approve cost, assign a person, contact a vendor, schedule work, close the item, or verify completion. Those remain explicit operator actions and truth states in Lucia.See also
Verification basis
Verified on September 10, 2026 against the evidence named in this page’s metadata. The
per-item message loop is bounded to the founder-recorded round trip of 2026-08-19 and to the
app source at
692a71c, which carries the drawer count, the hamburger badge, and the Needs your
reply section. The claim does not certify unrelated operator actions.