Viya's turnkey sites file a morning and an evening update. Someone had to read every site group, compare each entry with the week's plan, chase missing answers and decide what leadership should hear. Site Watch is a Monitoring Agent built to do that: flag by fixed rules, ask the site one question, judge the answer, report up. It can only ask and record: it has no way to approve, pay or change a plan. It is not switched on yet: verification, shadow mode and an explicit enable come first.
[01]What changesViya Constructions
This is the agent as built and tested, for turnkey sites, where Viya executes the work end to end.
From the agent's own rules.
In home construction a milestone is also money: each stage the client signs off releases a payment. ProjectSignal already chases a missing morning update and a short crew. Site Watch's rules go further: the evening update, unfinished work, rework, material with no open purchase, slipping milestones. It holds each answer to a cause and a date, and interrupts a leader only when a fixed trigger fires.
[02]Why this is hardViya Constructions
A site that plans 14 workers and gets 9 rarely calls it a problem. Three short days later the slab date moves, and nobody can say when it started.
A site that sends nothing may be fine, or nobody reported. Without a daily check the two look the same.
It has no cause and no date. Rain that stopped plastering until Friday is an answer. Labor not available, with no date, is not.
A director needs numbers first, one line per site, and only their own sites.
[03]How it worksViya Constructions
As built. Not yet run on live sites.
ProjectSignal hands over one record per site per day: planned labor, both updates, material needed and whether a purchase is open, the site's milestone, the working calendar. A record more than five minutes old is refused.
Eleven rules: no update by 10:30 or 19:00, labor below a set share of plan (80% by default), the day's work not completed, site reported delayed, rework after inspection, an issue in the update, material needed with no open purchase, a milestone slipping or moved twice or more, an overdue top-priority customer escalation, work value behind plan by a set amount, no plan for next week by Saturday evening.
One person's flags become one short question asking for a cause and a dated recovery. The AI drafts it. ProjectSignal's site bot posts it in the site's Telegram group and tags the site engineer or project manager. Three hours to answer, from the confirmed send. A vague reply does not reset the clock.
The AI reads the reply and proposes a verdict: explained, watch, unresolved or needs leadership. Then rules apply. No future recovery date: unresolved, with at most one clarifying question. A contradiction with ProjectSignal, or a critical flag: needs leadership.
No real answer in three hours: the flag goes to the site's director. If the question was to the site engineer, the project manager is asked once in the same group. On the promised recovery date the site is checked again, and the same problem goes up.
Verdict, reason, recovery date and next action go on the site's record in ProjectSignal. Leaders get a digest at 19:30, a Monday brief at 08:00, and an alert at once when a fixed trigger fires.
This morning's update shows 6 workers against 10 planned for lintel concreting. What is the reason, and when will the full crew be back?
Will sort it out.
What is the cause, and on what date does the full crew return?
Four masons moved to Site A for its slab pour. Back Thursday morning.
Built from that leader's own sites, filtered before the AI writes a word. Directors see their portfolio, the COO every selected site, the CEO critical alerts only by default. Project managers get questions, not reports.
[04]Connected to ProjectSignalViya Constructions
That split is why Site Watch was never given a way to change a plan.
Nothing is posted, saved or sent until the agent is enabled.
A guided workflow stops at a review card before it writes. A watcher has no card, so its limits are fixed in advance, as for every Monitoring Agent on Bleno. It runs on one authorized manager's own ProjectSignal connection, from a short list of functions. Any other call is refused.
If any function it is given could write a plan, a readiness answer, a client record or a budget, verification fails. If a send's result is unknown, it asks ProjectSignal what happened and does not send again blind.
What exists today. Live in ProjectSignal: a 09:00 summary of which sites have filed, and an 11:30 escalation of short or silent sites. Site Watch's management screen, leaders' reports page and status check in chat are in Viya's Bleno. The reads and writes above are that specification, not a live connection.
[05]Who decides whatViya Constructions
A model reads an answer well, but a confident "we'll sort it soon" can talk it round. So the rule sits outside it: no future recovery date, no "explained". Replies are evidence, never instructions.
[06]Before it is switched onViya Constructions
A watcher posts in a site group and messages a director with nobody pressing a button. A wrong question in front of a site team is hard to take back. So it proves its wiring, runs in silence, then is enabled on purpose.
Saving any change to a running agent pauses it.
48 automated tests cover this behavior. No question has reached a real site group and no report a real leader. The written switch-on procedure starts with one pilot site. An AI colleague, in pilot, already follows up in real site groups.
[07]More detailViya Constructions
A real cause and a recovery date stay in the digest. Alerts are for things like silence, a missed recovery, a contradiction or a critical milestone.
Verdict, reason, promised date and next action sit on the site's record, not in a chat that scrolls away.
In ProjectSignal it can only ask and record. It runs in shadow on real data before anything is sent.
To start we need a week of updates from a few sites, that week's plan, one owner who decides what counts as critical, and thirty minutes a week. A first version runs in shadow: you see what it would have asked before it asks anyone.
[08]Where this fitsViya Constructions
Send us one week of site updates and that week's plan. We will come back with how the checking runs today and what a first version would look like. Start with one workflow. You only pay if it works.