01
Project activity
Listening for events
Wakes for real signals
New project events and scheduled heartbeats give Sentinel a reason to inspect the work. Teams can also start a fresh run or follow up on an existing investigation.
Sentinel is the project agent for construction teams.
It wakes for project events, investigates connected records, and brings the work that needs judgment to the right person.
Workspace/Harbor Point/Sentinel
Scheduled project review
Harbor Point · Jul 19, 9:42 AM
A scheduled heartbeat found three new records inside tomorrow's release window.
Sentinel is working…
Autonomous does not mean unaccountable.
Sentinel works through durable project events, visible runs, real tools, and the same approval boundaries as the rest of Clevis.
02
Idle
Next review
Tomorrow, 9:00 AM
Scheduled heartbeat · Harbor Point
No action needed until then.
Sleeps when the project is quiet
Empty scans do not need a model call. Sentinel returns to sleep and waits for the next meaningful event, manual request, or scheduled review window.
03
Runs3 total
Keeps every run visible
The request, project records, tool activity, response, approval, and result remain together in the same chat-shaped run history.
Everywhere Sentinel works
One project agent across events, runs, investigations, and approvals.
Project events
RFIs, submittals, schedule activity, and field records each become a durable signal Sentinel can act on.
Incoming events
No events yet
Run history
Scheduled heartbeats, event wakes, and manual runs each produce their own persisted investigation.
Run history
Every run stays visible
Investigation thread
Follow-ups continue the selected run instead of starting the reasoning over from scratch.
Records inspected3 sources
RecordTypeStatus
Approval gate
High-impact work pauses for human sign-off before a controlled tool changes a project record.
- 3:41
Records read
RFI + submittal
- 3:42
Response drafted
Register update
- 3:43
Approval gate
Waiting for project lead
Approval required
Built for the way projects actually run.
Sentinel stays bounded to the project, aware of its operating window, and inspectable from event to outcome.
Project-scoped
Each Sentinel belongs to one project and uses the permissions, records, tools, and ownership available inside that project boundary.
Incoming events
No events yet
Time-zone aware
Scheduled heartbeats follow project business hours and time zone. Event and manual wakes can still bring urgent work forward outside the normal window.
Run history
Every run stays visible
Fully auditable
Events claimed, records read, tool calls, approvals, output, and completion status remain inspectable for every Sentinel run.
- 3:41
Records read
RFI + submittal
- 3:42
Response drafted
Register update
- 3:43
Approval gate
Waiting for project lead
Approval required