TAHOMA × REVASCENT
00Cover
1 / 12
Weekly briefing · July 7, 2026
Two workflows in.
Sixteen to go.
Where the Revascent automation stands today, what the last few weeks actually bought, and the path to scaling it across the division and beyond.
Today's order
How we'll run this.
- 01What we've heard
- 02The Remit reality: working, and why it looked broken
- 03What the first two workflows bought us
- 04Under the hood: the architecture, and how we define doneTechnical
- 05The plan, and the two live workflows
- 06NJShine is retiring: where we point next
- 07What gates scale, and where this goes
Questions welcome throughout. We hold the floor at the end.
01 · What we've heard
Everything you've raised, in one place.
- 1Remit looks broken. The live view goes dark, so a run that finished looks like it failed.
- 288 charges are behind, held up in intake.
- 3Face sheets land in the wrong folders, holding up cash flow, and your Cape staff fix it by hand.
- 4The logic came as a recording, not on paper, so it feels like we would be guessing.
- 5Failures every day, code changes every day, the same treadmill as the developers before us. The process is not effective.
- 6NJShine is retiring anyway. Is this worth it over reverting to Power Automate?
All of it is fair. We take each one head-on, and close with a straight answer to every one.
02 · The Remit reality
It ran every time. The window into it went dark.
What the team saw
waiting for execution to start streaming…
Three mornings last week, Remit was flagged as down. The live view was black.
What actually happened
✓
Remit completed
unposted moved to the folder
Three times, already complete. The remits posted. The work was done.
The automation did its job. The live view is the bug, and it is the single biggest reason this feels broken. It is also a fast fix.
03 · What the first two workflows bought
The first two were the expensive part.
- We learned an environment nobody had documented, logic that lived only in people's heads.
- We built the architecture that makes the rest cheap: local, cached, self-correcting.
- We mapped exactly what gates scale, so the surprises that cost us the last month do not repeat.
The next sixteen are faster because these two were hard.
04 · Under the hood Technical
We don't ask the AI to re-solve your workflow every time.
- Most computer-use automation keeps a model in the loop for every click: observe, reason, act, repeat. Slow, costly, and it drifts.
- Ours compiles a known workflow into a typed map of states and steps. It reads the screen locally, matches a known state, runs a verified step. The AI is called only when something genuinely new appears.
observe→
match state→
run verified step→
check result→
escalate only on novelty
This is a moat for exactly your kind of work: high-volume, known, repeated. It gets faster and cheaper over time, where general-purpose computer use stays expensive and brittle.
04 · Under the hood Technical
"It ran" is not our bar.
- Completed with the AI barely involved, low escalation.
- No duplicate actions, ever.
- Every step leaves an auditable record. You can see exactly what happened and why.
- Recoveries are rare and safe, never a guess on a live portal.
When we call a workflow green, this is what we mean. It is a stricter bar than most vendors hold, and it is the bar that lets you trust the next sixteen.
The fair question
Is this just constant firefighting?
- The setup before us fixed every failure by hand, forever, because it had no way to learn. Firefighting was the model, with no end to it.
- Ours is built to get off that treadmill. Every run teaches the system, so the failure surface shrinks instead of repeating. The changes happening now lay that foundation, they do not patch the same leak.
- The daily fixes are a transition with a finish line, not how this runs. The dates they end are on the next slide.
That is the difference that matters. The old way fought fires forever. This one is built to stop needing to.
05 · The plan · in our control
Owners and dates.
Jul 10
Version pinning + VM stabilization
One targeted fix, no full redeploy. Fewer knock-on errors, steadier uptime.
Jul 14
Live view + failure reporting
You see runs happening in real time, and when something breaks we see it first.
Fixes the Remit false alarmsJul 17
Local screen-reading
Replaces the vision model. Faster, more consistent runs, lower cost.
Next wk
Session reuse
About 30% more throughput from your current login, no action needed from you.
NJShine + Remit · honest status
The two live workflows, honestly.
Remit
Completing every cycle. The live view is the fix, landing Jul 14, and that closes the "looks broken" gap. This one goes green.
NJShine
Two separate problems here. Files stuck in intake, the 88 behind: the retry fix goes live today and clears them. Face sheets sent to the wrong folder: a different issue, driven by the ALS logic we only recently learned exists, and gone once that logic is written down. Retiring Jul 25 regardless, so we drain the backlog and hand off clean.
One goes green. One is winding down on the health system's clock, not ours.
06 · The question going forward
NJShine is retiring July 25. So where do we point next?
- It is sunsetting on the health system's timeline. We will not spend three weeks propping up a system that is going away, and if reverting it for the interim is simplest for your team, that is fine.
- The real decision is where the durable automation goes next, and that is a call to make together.
Option A · carry it forward
Take the logic into whatever replaces NJShine, if that is where you want us.
Option B · skip to the next
Move straight to the next workflow in the backlog, and prove the model on one with a future.
Our steer: put the energy on a workflow that lasts. Which one is the highest-value next win for you? That is where we point.
07 · What unblocks scale
Exactly what stands between here and the rest.
- ◑The two live workflows hold the definition of done. On track for the dates shown.Us · in flight
- ☐The workflow logic written down and approved by you before we build. We capture it whatever way is easiest, a recording, a diagram, or a working session, and turn it into a spec you sign off. No guessing.Together
- ☐A second login provisioned, so we can run at full volume.Revascent
The middle one is the fix for the folder errors and the gaps: logic on paper, approved, before a line is automated.
07 · Where this goes
The path from here.
Live now
2
workflows, this division
Next
1
the workflow we pick together
Then
16
the rest of the backlog
On our side
An expanded team behind it: senior engineering leadership and added build capacity, so scale is resourced from the start.
From Revascent
1. Provision a second login. 2. Send the written logic spec.
Recap · your concerns, our answers
Every concern, with a straight answer.
1Remit looks broken
It completed every time. The live view is the bug, fixed Jul 14.
288 charges behind
Files stuck in intake. The retry fix goes live today, clears them, and stops the stalling.
3Wrong folders, staff corrections
A separate problem: folder promotion runs on the ALS logic. Written down and approved, those errors stop.
4Logic felt like guesswork
We write it down and you sign off before we build. No guessing.
5Firefighting, like before
The old setup had no exit. Ours shrinks failures over time, and the daily fixes end on a date. Not the same treadmill.
6Worth it vs Power Automate
NJShine is retiring anyway. Point the energy at a workflow with a future, run as a service.
Where this goes
We're driving this.
- ✓Remit works; the visibility fix lands Jul 14.
- ✓NJShine's backlog clears as the retry fix ships today; it retires Jul 25 regardless.
- ✓Platform fixes have owners and dates: 7/10, 7/14, 7/17.
- →Together we pick the next durable workflow, and the logic gets written down first.
The old one is winding down. Let's decide where the next win is.