Skip to content
PROTOTYPE — MOCK DATAFigures are generated fixtures derived from the registry. Not ACF actuals.
Menu (15)
?
RESOURCES
What's new

Every sprint from F0, generated from the plan ledger — including the findings, not only the features.

KPI dashboard documentation

The fourteen numbered deliverables, what each one answers and who it is for.

Give feedback

Every round so far, and what each one produced. This is the loop the product was actually built on.

Vu Tuan Minh (CEO)
exec · read-only
Scope
ACF and below
Settings — access rules and audit →

Clears the persona and returns you to the default reader. At fullstack this is Entra ID (A-21) and the identity stops being a cookie.

← Tele-Sales (ACF return)
INTERNAL PROCESS · KPI · LAGGING

Call Quality / QA ScoreTL-22

In ACF’s own returned KPI list — row MAP-040 of KPI mapping between user and IT, 18 Sep 2026.

—○ No data○UNMEASURED
ACTUAL VS PLAN
DEFINITION
Formula
QA points achieved / Total QA points
Unit / direction
number · higher better
Source system
Stringee
Refresh
weekly
Target
TBC
Target status
From an ACF document
Baseline in context/
TBC
OWNERSHIP — two roles, two people (R-G-02)
Metric owner — owns the target and the result
Head of Telesales
Data owner — owns the source system and pipeline
Telesales / QA

Both proposed by Ikigai and awaiting ACF confirmation (DEC-02).

Run the data-integrity checks on this series →
PRIORITY — PROPOSED BY IKIGAI (13 §A.2)band P3, the clause that produced it, and its share of attention
P3
ACF has already written a target for it in a document
Clause that fired
target taken from an ACF document (T-01) - ACF has already written a number for it
Share of internal process
1.3%
Of total attention
0.32% at the approved weighting

The band is derived, not chosen — a published rule over facts already in the registry, re-runnable with tools/assign_weights.py. It is what the strategy simulator splits a perspective’s weight by, which is why it is not cosmetic: change this band and the shortlist changes. Q-28 asks who at ACF owns the decision.

COMMENTARY — why the number is what it is

No commentary recorded for this metric. A red tile with no explanation is the failure mode the current monthly pack already has.

Commentary is attached to the metric and period, not to a slide. It survives the month — which is what makes a variance reviewable at the next meeting instead of re-argued. Prototype — read-only fixtures; at fullstack this is the COMMENT table with author identity from AD.