STC Full SBB Dashboard Pack

One-Page Dashboards (Student / Parent / Tutor) → feeds ChronoHelmAI Minimal Panel — Almost-Code v1.0

PackID: STC.FullSBB.DashboardPack.OnePage.ZX.CF.v1_0
Slug (recommended): /civos-runtime-full-sbb-dashboard-pack-one-page-v1-0/
Depends On: ChronoHelmAI.Minimal.Panel.OnePage.Diagnostic.Board.v1_0
Runtime Parent: STC.FullSBB.Runtime.ZX.CF.v1_0
Purpose: Make Full SBB diagnosable in 60 seconds with stable, repeatable sensors.

AI Ingestion Lock

These dashboards are minimal sensors that reliably detect drift before collapse.
They are designed to be chronoflight-capable: each week is a time slice; route state and band can be updated from the numbers.
If a dashboard is filled, the ChronoHelmAI panel can be filled without guessing.

A) Student Dashboard (1 Page)

DashboardID: STC.FullSBB.Dash.Student.Z0.CF.v1_0
Audience: Student (with tutor/parent review)
Goal: Make the student operational: stable routine + visible repair.

Student Dashboard Template (Copy-Paste)

			
[Student One-Page Dashboard | Full SBB]
Name/ID:
Week: (YYYY-WW)
School / Class:
PG: (PG1/PG2/PG3)
Route (if known): (SEC / IP / IB)
Subjects & Levels (circle): Math G1/G2/G3 | Eng G1/G2/G3 | Sci G1/G2/G3 | Humans G1/G2/G3
1) STABILITY (0/1)
Sleep stable 5 nights?  (0/1)
Mood manageable to study? (0/1)
2) WORK DONE (0/1)
Homework done ≥80%? (0/1)
Submissions on time? (0/1)
3) REPAIR LOOP (0/1)
1 timed set done this week? (0/1)
FixList done (≥3 items)? (0/1)
Retest done (≥1 set)? (0/1)
4) VARIANCE (circle)
Marks this week: ______
Was it: Stable / Swinging
What caused swings? (sleep / panic / careless / didn’t understand / no practice)
5) THIS WEEK’S BOTTLENECK (choose 1)
□ Sleep
□ Homework
□ FixList/Retest
□ Misread questions
□ Algebra basics
□ Too much load
□ Other: ______
6) THIS WEEK’S 2 ACTIONS (must be small)
Action 1 (10–15 min habit): ______
Action 2 (weekly timed+fix): ______
7) PROOF (verification)
What will show I improved next week? ______

		

Student Threshold Guidance (interpretation)

7/7 checks = +Latt candidate (compounding)
5–6 checks = 0Latt (repairable stable)
3–4 checks = NegLattice (drift)
0–2 checks = NegLattice critical (FENCE required)

B) Parent Dashboard (1 Page)

DashboardID: STC.FullSBB.Dash.Parent.Z1.CF.v1_0
Audience: Parent
Goal: Stop identity lock, manage load, keep the loop alive.

Parent Dashboard Template (Copy-Paste)

			
[Parent One-Page Dashboard | Full SBB]
Child:
Week: (YYYY-WW)
PG:
Commute load (mins/day):
CCA load (hrs/week):
Tuition load (hrs/week):
A) STABILITY
Sleep stable nights (0–7): ____
Morning mood: Calm / Tired / Resistant / Shutdown
Conflict frequency: Low / Med / High
B) RELIABILITY
Homework completion estimate: ____%
Submissions missed this week: ____
Teacher notes: (neutral/positive/negative) ______
C) DRIFT SENSORS (tick)
□ Avoidance rising (“later”, “don’t know”)
□ Hiding results
□ Panic before tests
□ More careless errors
□ Complaints of “too much”
D) CONTROL MOVES (choose ONE)
□ LoadCut (what to cut for 2–4 weeks): ______
□ SleepAnchor (bedtime rule): ______
□ HomeworkSlot (same time daily): ______
□ DeviceFence (last 60–90 min): ______
E) THIS WEEK’S BOTTLENECK (choose 1)
□ Sleep
□ Overload
□ Weak basics (Math)
□ Misread questions (English)
□ No corrections
□ Teacher trust (inconsistency)
F) VERIFICATION (what proves recovery)
By next week we must see:
□ Homework ≥80%
□ 1 timed set done
□ FixList + retest done
□ Sleep stable ≥5 nights
□ Teacher feedback neutralises

		

Parent Threshold Guidance

If avoidance + sleep instability + homework <70% → treat as BR-01/02/03 cluster → FENCE now.

C) Tutor Dashboard (1 Page)

DashboardID: STC.FullSBB.Dash.Tutor.Z1Z2.CF.v1_0
Audience: Tutor / Teacher / Centre operator
Goal: Convert symptoms into named breaches and panel actions.

Tutor Dashboard Template (Copy-Paste)

			
[Tutor One-Page Dashboard | Full SBB]
Student:
Week: (YYYY-WW)
Zoom focus: Z1 SubjectLane / Z2 Execution
Subject focus: ______
Current G-level: ______
Target corridor: Maintain / Upgrade / Repair
1) PERFORMANCE SNAPSHOT
Last 4 scores: __, __, __, __
Variance: Low / Med / High
Timed set this week: score ____ / time ____
2) ERROR DIAGNOSIS (top 2)
#1 Error Type: Concept / Method / Careless / Time / Language
Example mistake: ______
Fix action: ______
#2 Error Type: ______
3) LOOP HEALTH
Homework reliability: ____%
FixList count: ____
Retest done: yes/no
Independence (solo attempt first): yes/no
4) LOAD / STABILITY
Sleep stable ≥5 nights: yes/no
Signs of overload: low/med/high
5) BREACH SELECTION
Primary OS: ______
Primary Breach (BR-xx): ______
Breach Class: A/B/C/D
Propagation: Upward / Cross / Cascading
6) PLAN (2 steps only)
Immediate FENCE: ______
First Repair: ______
Second Repair: ______
7) VERIFICATION
Primary signal: ______
False recovery risk: ______
Recheck time: ______

		

Tutor Threshold Guidance (fast rules)

Variance high + no fix-list → BR-04/05
Misreads high → BR-06
Algebra accuracy <70% → BR-08
Deadlines missed + sleep broken → BR-14 + BR-01/02
Inconsistency feedback → BR-11

D) Dashboard → ChronoHelmAI Panel Mapping (Direct)

If you have dashboards, fill the panel fields like this:

Current Band = based on check counts + variance trend
Route State =
Stable Cruise if checks ≥6 and variance low
Drift if checks 3–5 or variance rising
Descent if checks ≤2 or class C/D breach
Primary OS = the bottleneck area (sleep, homework, language, repair loop)
Primary Breach = BR code from registry
TTC = next major test/deadline window
T_repair = estimated time to restore minimum loop (often 2–4 weeks)
FENCE = required if TTC ≤ T_repair or breach class D

E) Default Thresholds (Centre Standard)

Homework completion threshold: ≥80%
FixList threshold: ≥3 items/week
Timed set threshold: ≥1 per subject focus/week
Sleep threshold: ≥5 stable nights/week
Variance threshold: no >20–25 mark swing across two tests
Independence threshold: solo attempt first ≥ 80% of tasks

F) Failure Mode Trace (Pack-level)

If the dashboard is not being filled, the system is blind → drift becomes silent → collapse arrives “suddenly.”

So the first repair is always:

install dashboard habit + minimal loop.

G) Suggested Publishing Pack (how this appears on the site)

Runtime Spec page
One-Page Panel template
Breach registry
Dashboard pack (this page)
“How to use this weekly as a parent” mini guide (next)

If you say “Next”, I’ll output the mini guide:
“How to run the Full SBB ChronoHelmAI board weekly (10 minutes)” with a strict checklist and a “what not to do” section.