How a process gets on the record.And climbs.

Six rungs from first sighting to running itself. Every confirmed process carries three things: a description, a living document, and a workflow that can run.

Discovered Confirmed Documented Standardized Automated Monitored

Every process in the record sits on one of these rungs.

Ask for an Extract.

A certified briefing on any process in your record. Every claim traced to an observed moment. Ask for it by name.

Customer refunds at Harbor Point

One process, one keeper, nine steps. Prepared for whoever has to answer for it.

14sessions
1keeper
9steps
the observed path
  1. open the order in the sales system 14 of 14 runs
  2. check what the customer paid 14 of 14
  3. match the refund to the order 14 of 14
  4. flag refunds over $200 11 of 14
  5. email the customer an update 9 of 14
  6. approve and send the refund 14 of 14 · 61% of handle time
  7. note it on the account 14 of 14
  8. double-check the totals 14 of 14
  9. file the paperwork 12 of 14
findings
  1. Every recorded run this quarter was Marcus. No second person has been seen completing this process.
  2. Steps 6 to 8 take 61% of the time and follow a fixed rule. They are the natural first automation.
evidence · 14 sessions · 3 people across variants · last 90 days drawn from get_process_detail · get_process_variations

things people pull Extracts for

  • before automating anything
  • when a keeper resigns
  • for the auditor
  • for the buyer's diligence list
see it on your own record →

No evidence, no answer.

Every claim in every answer is one tap from the moment it came from. Tap one.

you · who handles refunds when beth is out?

Priya has covered customer refunds in Beth's absence six times since June. Each run followed the same approval steps. Median handle time was 14 minutes.

jun 12 · priya · sales system + payment portal22 min
jul 3 · priya · sales system + payment portal18 min
jul 18, jul 29, aug 6, aug 21 · priya4 sessions
approval steps v3 followed in 6 of 6 sessionscorroborated
steps unchanged since may 20 · refund policy updatecorroborated
handle time across 6 sessions: 11, 12, 14, 14, 18, 22 minmedian 14
underlined claims open their evidence
you · why did we lose the henderson account?

The record has no evidence on this. No answer.

myvue refuses rather than guesses

We count in the open.

The count is the product, so the counting rules belong to you. These are them.

§1distinctness

A process is work with clear steps that repeats the same way each time. Seen fewer than three times, it is not a process yet.

§2confirmation

Nothing enters the count until you confirm it. Merge, split, and archive are your controls, not ours.

§3freshness

A process unconfirmed and unobserved for 28 days is aging and stops counting. At 42 days it is stale. Confirm it and it returns, at no penalty.

§4exclusions

One-off tasks, personal activity, and blocked apps never enter the count.

§5disputes

Contest any entry. The evidence behind every counted process is inspectable in the product.

how grades are earned →

Nothing runs hidden.Everyone sees what myvue sees.

Every person sees their own day and controls their own block list. Blocked apps never leave their machine, and deleting records is held by the account admin.

the agent tray

observing
since 8:41 am · this machine

blocked apps

  • 1Passwordnever seen
  • Signalnever seen
  • personal browser profilenever seen

what myvue saw today

  • 9:14 · work order intake · erp · 22 min
  • 10:02 · quote preparation · spreadsheet · 9 min
  • 11:37 · email triage · outlook · 14 min

what is stored

Each screen is read in the moment, turned into notes about the work, and thrown away. Screen video is never stored, so there is nothing to leak later.

These are buttons in the product, not paragraphs in a policy.

See the record itself.