Your crew logs the day where the work happens -- by voice, by photo -- and the office acts on that exact record, never a re-keyed copy. One shared graph carries it write-once, anchored to an immutable ledger.
Why it matters
The Projected Operations Surface is the daily operating picture -- daily logs, manpower, weather, incidents, field sensors -- assembled for the seat in front of it. The superintendent sees a capture surface. The PM and the office see the same entries, live, on the same record. No double entry, no end-of-week reconciliation, no arguing about what happened on site.
It runs on Cascade, the platform inheritance engine. The field log is written once -- one tenant-scoped record in the shared graph, not a copy per app -- and the community-api resolver walks the cascade closure tree to project the right operating surface to every seat: super, PM, office. An agent assembles the draft from voice notes and site photos.
The work, split
The superintendent talks; the agent listens. From a voice note and a handful of site photos it drafts the structured daily log -- weather, crew count, trades on site, work performed, incidents flagged by severity -- and files it to the shared record. That is the calm 80 percent, captured before the truck leaves the gate.
When that record drives money or risk -- a change order, a draw, a delay claim -- you step forward and approve. The surface raises friction to match the stakes, confirms a second party signed off, and writes your call to the ledger. The result is a number no one at the table can dispute.
How it works
Bring a real project. We will project the operations surface for your role -- field, PM, or office -- on one shared record you can trace from the gate to the ledger.