Skip to workspace
Flows

Analytics

Quality & usage metrics

· · primary quality signal is escape rate, not first-pass check rate

Escape rate
First-pass (sec.)
Repair rate
Evidence rate
Lock integrity
Median gate
Independent claims
0
External suite passes
0
Projects
0
Open tasks
0
Open failures
0
Pending approvals
0
Claims pending
0
Unsupported shipped
0

Quality metrics

Primary metric is escape rate — defects found after required checks had passed. Secondary metrics are instrumented for diagnosis, not vanity.

Primary · Escape rate

Not enough data

Defects found after the required checks had passed. Need more releases/external tests.

0 escaped / 0 confirmed

Do not lead with

First-pass check rate, raw check counts, raw % complete

Secondary metrics only. Lead with escape rate. High first-pass can mean weak tests.

Validation model

Plan checks passed
Predefined checks passed
Independently checked
Externally validated

Secondary (instrumented)

First-pass rate
Supporting only
Repair rate
Repairs / gates
Evidence attach rate
Notes per check
Median gate time
Time-to-green proxy
Lock integrity
No silent check drift
Releases
0
Recorded releases
Independent claims
0
Tier 3+ grants
External suite passes
0
Full fixed suite
Checks passed
0
Recorded results
Checks failed
0
Recorded results
Repairs
0
Repair prompt uses
Gates completed
0
Verify gates closed

Record events

Escaped defect = found after Flows checks passed. Also record check/repair/evidence to fill secondary metrics.

Behavioral failure focus

  • A Visual-only functionality
  • B Persistence failure
  • C Authentication / authorization
  • D Integration failure
  • E State transition failure
  • F Render / event-loop failure
  • G Data-integrity failure
  • H Regression
  • I Security failure
  • J Accessibility failure

Evidence bands

Strong 0 · Thin 0 · No run 0

Generation tokens (est.)

0 local generation(s) · char÷4 heuristic

Active agents

4

Governance roster — not live tool sessions

Per project

No projects in this workspace.

Multi-tenant server metrics sync when an org is bootstrapped (Settings → Org). Local metrics always instrument; server mirrors via quality events.