They run on our own server and work with what the firm already produces — the group chats, the inbox, the Asana boards, and now a direct line. Three tempos, one goal: what was decided, what is about to be missed, and what you need recorded right now.
Keeps the ledger of every date that can hurt us and escalates each one as it approaches. Nothing with a deadline goes unnoticed.
Reads the week's chats and email, finds the decisions, and reconciles them against Asana. Nothing said in chat or email is lost.
Text Claw directly: status updates become Asana comments in seconds, facts get remembered firm-wide, tasks get created on your word. Your phone is now an input to the record.
Every permission in the system comes from one question: who typed the words this program is reading? The answer decides what each program is physically allowed to do — not policy, not promises, but what its credentials can and cannot reach.
Vendor chats, counterparty email — the Weekly's diet. Some of it could one day be hostile, so the reader is caged:
Your DM to Claw. The message is its own approval — you typed it — so this channel may act live:
Proposal batches you've reviewed, and the Sentinel's own ledger writes. The only full-write path, and it runs on trusted input only:
Everything mechanical — parsing, sorting, routing — is done by code that gives the same answer every time. Judgment is saved for the end, where a person approves it.
Alex exports the week's chats — every group, voice notes and videos transcribed — and the mail program collects the week's email from senders already on the firm's roster. Email from anyone not on that list is never read at all.
Before any email's content is read, its provenance is scored — sender verified cryptographically, sorted into a trust tier. A stranger's prose can never talk itself into a higher tier, because the sorting happens before the prose is opened:
Each message routes to its project — FTL Self-Storage, 770 Lake Road, 5990 SW 135 Terr, the pipeline — by a strict ladder. Higher rungs are more certain and always win:
Every decision, commitment and blocker found in the week is compared to what Asana currently says:
One dated rollup comment per task per week — each task reads like a project journal.
The Weekly can't create tasks. It writes a proposal; a person approves or rejects each one.
"Asana says due the 8th; on the 22nd the vendor said it slipped; nothing was updated." The single most valuable thing it produces.
Claims get graded, not just collected. A vendor asserting something no one inside the firm confirmed is quarantined as an unverified claim. A statement only counts as corroborated when the system can point to a specific verified message from a principal saying the same thing — and that check is done by code that cannot be argued with.
A partner digest to WhatsApp — decisions first, readable in two minutes. Proposal
batches for approval. Field notes for context that fits no task. Task comments in Asana.
Every automated word is marked NanoClaw-auto —
machine writing is never mistaken for a partner's.
One ledger of key dates across all projects, checked every morning. Each date sits in a tier based on how close it is after accounting for lead time — an insurance renewal that takes 60 days to negotiate starts escalating 60 days early, not 14.
Quiet dates cost nothing. From Watch onward they appear in the morning digest to the partners' chat, with the owner @-mentioned as urgency rises. One message a day, worst first, never a flood.
The newest program, and the fastest. You already message people about the business all day — now one of those threads writes things down properly. Because everything in your DM was typed by you, this is the one channel allowed to act live.
Status updates land in seconds, not Sunday. The DM routes your sentence with the same machinery the Weekly uses — project names, addresses, permit numbers — finds the right task, and comments. If it isn't sure, it asks you, because you're right there. It never posts to a guessed task.
"Remember that…" becomes firm memory, not chat memory. Gate codes, lockbox combos, which house has gas — stored in one shared ledger that both your Claw and Andres's Claw answer from. New values supersede old ones, and the full history is kept, so a changed code can always be traced.
Tasks are created on your word — and only top-level. It always shows you the draft first and waits for your yes. It never creates subtasks: subtasks vanish from board views, and this workspace has lost real obligations that way. Everything it makes stays visible.
Each brother writes as himself. Alex's DM posts under Alex's Asana
account, Andres's under his — attribution comes free, and every automated line still
carries the NanoClaw-auto marker.
Additive only. It can add to the record; only humans subtract from it — and date moves stay under the Sentinel's no-silent-snooze watch.
Asana stays the single source of truth. Everything else is a way in or a way out — and each program also watches the others' health, so a broken program can't fail silently. Silence is never assumed to be good news.
All from real runs, this month.
A USVI entity's annual report is due every June 30 — miss it and the entity can be administratively dissolved. The renewal notice goes to a relative's mailbox, not ours, and last year's task lived on no board at all. It's in the ledger now, permanently, with lead time that fires before the notice would even arrive.
Three separate monthly payment applications go to the owner's rep on FTL. Each month the program verifies each one actually went out — by finding the real document in sent mail. When nothing went out, silence is the alarm.
Live runs have flagged due dates that slipped in conversation but never moved in Asana — and corrected the program's own earlier false alarms when fuller data arrived. An honest system reports its own mistakes.
Completing an Asana task silently hides any open subtasks beneath it. A sweep found 22 — including post-closing warranty items on a sold home and a permit response still owed to the city. It's also why the DM refuses to create subtasks at all.
Someone typing a fake "message from Alex" inside their own chat message, spoofed email authentication, lookalike domains one letter off a real vendor's — each is caught by checks that run before any content is believed, and reported naming the real author.
Every new capability is validated against a full year of real data before it may act, then run in shadow mode. A recent audit fixed two dozen defects — most of them failures that would have looked exactly like success, which is precisely why the audits exist.
The Sentinel proves itself every day. The Weekly proves itself every week. The DM proves itself every time you use it. And each one watches the others — a broken program cannot fail silently.