SG Z6 PromptRegistry v0.1 — HGW Prompt Pack (Deterministic Dashboards + Routing + Backtests)

TITLE: SG Z6 PromptRegistry v0.1 — HGW Prompt Pack (Deterministic Dashboards + Routing + Backtests)
VERSION: CivOS Unified Spec v1.x
MODE: Almost-Code / Runnable prompt blocks / WordPress paste-ready
OWNER: eduKateSG Fence Learning Systems
PLACE: SG
ZOOM: Z6
GOAL: Provide strict prompt templates so any LLM can:
- generate HGW panels (Z0/Z1/Z2),
- route repairs using registries,
- log backtests in comparable format,
- enforce Tool-with-Proof (VL-OS) discipline.
LOCKS:
- Prompts MUST output the panel schema exactly.
- Prompts MUST cite registry IDs for nodes/sensors/signatures/protocols.
- Prompts MUST refuse to “widen” if exit conditions are not met.
========================================================
REGISTRY-0: VERSION HEADER
========================================================
UnifiedSpecVersion: v1.x
PromptRegistryVersion: v0.1
Place: SG
Zoom: Z6
Owner: eduKateSG Fence Learning Systems
Updated: 2026-02-16
Status: live
========================================================
PROMPT-0: SYSTEM GUARDRAILS (PASTE ABOVE ALL PROMPTS)
========================================================
[GUARDRAILS v0.1]
You are operating inside eduKateSG Fence Learning Systems.
You MUST:
1) Use ONLY the registries provided (Nodes/Edges/Sensors/Signatures/Protocols/Panels).
2) Reference registry IDs for every recommendation.
3) Output in the exact schema requested (no extra sections).
4) Enforce Fence logic:
- If any NIT/NITS/NITA trigger exists, you must choose TRUNCATE or STITCH (not WIDEN).
5) Include re-test plan + exit conditions.
6) If info is missing, make minimal safe assumptions and state them inside the panel.
========================================================
PROMPT-1: Z0 STUDENT DASHBOARD GENERATOR (HGW-Z0)
========================================================
PromptRecord:
- id: SG×EDU×Z6×Operator×PromptPack×PR-HGW-Z0-v0.1
purpose: "Generate HGW-Z0 Student Dashboard"
required_inputs: [
"LevelBand",
"Last 2 weeks sensor results (SensorID → score/notes)",
"Active signatures (if any)",
"Workload hours/week",
"Goal + exam horizon"
]
strict_output_schema: "SG×EDU×Z0×Learner×Panel×HGW-Z0-v0.1"
prompt_block: |
[PROMPT PR-HGW-Z0-v0.1]
Use [GUARDRAILS v0.1].
Task: Generate a HGW-Z0 dashboard using the PanelRegistry schema.
Inputs:
- Place: SG
- LevelBand: <...>
- Goal: <...>
- ExamHorizonWeeks: <...>
- WorkloadHoursPerWeek: <...>
- SensorResults (last 2 cycles):
<SensorID>: <result + time + errors>
...
- ActiveSignatures (if known):
<SignatureID> ...
Registries available:
- NodeRegistry, EdgeRegistry, SensorRegistry, SignatureRegistry, ProtocolRegistry, PanelRegistry.
Output EXACTLY the format of:
SG×EDU×Z0×Learner×Panel×HGW-Z0-v0.1
Routing Rule:
- Choose Top3 Root Nodes by impact (edge weights + severity + recurrence).
- Each root node must map to exactly one ProtocolID.
- Must include 5-day plan + 1 timed mini + re-test schedule.
- Must include exit conditions before widening.
========================================================
PROMPT-2: Z1 PARENT PANEL GENERATOR (HGW-Z1)
========================================================
PromptRecord:
- id: SG×EDU×Z6×Operator×PromptPack×PR-HGW-Z1-v0.1
purpose: "Generate HGW-Z1 Parent Operations Panel"
required_inputs: [
"Child LevelBand",
"Last 2 weeks sensor results",
"Routine constraints (time windows)",
"Tool use level + trace compliance",
"Stress signals yes/no"
]
strict_output_schema: "SG×EDU×Z1×Parent×Panel×HGW-Z1-v0.1"
prompt_block: |
[PROMPT PR-HGW-Z1-v0.1]
Use [GUARDRAILS v0.1].
Task: Generate HGW-Z1 Parent Panel using PanelRegistry schema.
Inputs:
- Place: SG
- ChildLevelBand: <...>
- RoutineWindows: <...>
- ToolUseLevel: <low/med/high>
- TraceCompliance: <ok/missing>
- StressSignals: {sleep:<ok/bad>, avoidance:<yes/no>, meltdown:<yes/no>}
- SensorResults (last 2 cycles):
<SensorID>: <...>
- ActiveSignatures (if known):
<SignatureID> ...
Output EXACTLY:
HGW-Z1 panel schema.
Must select exactly one WeeklyPack:
- PACK-PRI-25 or PACK-SEC-35 or PACK-HUM-30
and include: pass_rule + fence watchlist + re-test calendar.
========================================================
PROMPT-3: Z2 COHORT PANEL GENERATOR (HGW-Z2)
========================================================
PromptRecord:
- id: SG×EDU×Z6×Operator×PromptPack×PR-HGW-Z2-v0.1
purpose: "Generate HGW-Z2 Tutor/Cohort Panel"
required_inputs: [
"Cohort anonymised IDs",
"2-cycle sensor results per learner",
"Active signatures per learner",
"Intervention hours available/week",
"Exam horizon weeks"
]
strict_output_schema: "SG×EDU×Z2×Operator×Panel×HGW-Z2-v0.1"
prompt_block: |
[PROMPT PR-HGW-Z2-v0.1]
Use [GUARDRAILS v0.1].
Task: Produce HGW-Z2 Cohort Panel.
Inputs:
- Place: SG
- CohortSize: <n>
- ExamHorizonWeeks: <n>
- InterventionHoursPerWeek: <n>
- Learners:
- ID:<AnonID>
LevelBand:<...>
SensorResults:<SensorID result> (last 2 cycles)
ActiveSignatures:<SignatureID ...>
...
Output EXACTLY:
HGW-Z2 panel schema.
Allocation Rule:
- Prioritise S3 signatures clusters.
- Assign hours to ProtocolIDs.
- Include coupling warnings status for COUP-SG-01/02/03.
========================================================
PROMPT-4: REPAIR ROUTER (CH/ai ROUTING EMITTER) v0.1
========================================================
PromptRecord:
- id: SG×EDU×Z6×Operator×PromptPack×PR-ROUTER-v0.1
purpose: "Emit root-cause routing decisions from signatures"
required_inputs: [
"Active signatures",
"Relevant sensor results",
"Node + edge registries"
]
strict_output_schema: "ROUTING-DECISION-BLOCK v0.1"
prompt_block: |
[PROMPT PR-ROUTER-v0.1]
Use [GUARDRAILS v0.1].
Task: Given signatures + sensor deltas, pick Top3 root nodes and the correct protocol.
Output schema:
[ROUTING-DECISION-BLOCK v0.1]
Place: SG
Date: <YYYY-MM-DD>
1) ActiveSignatures
- <SignatureID> (severity S1/S2/S3)
2) RootNodes Ranked
- #1 <NodeID> — reason: <edge weight + recurrence> — Protocol: <ProtocolID>
- #2 ...
- #3 ...
3) FenceMode
- Mode: <TRUNCATE/STITCH/WIDEN> — Why: <trigger>
4) Re-test
- <SensorID> on <day>
5) ExitConditions
- <...>
========================================================
PROMPT-5: BACKTEST LOGGER v0.1 (BEFORE/AFTER)
========================================================
PromptRecord:
- id: SG×EDU×Z6×Operator×PromptPack×PR-BACKTEST-v0.1
purpose: "Log intervention as comparable backtest record"
required_inputs: [
"Before metrics",
"Intervention (protocols applied)",
"After metrics",
"Notes"
]
strict_output_schema: "BACKTEST-RECORD v0.1"
prompt_block: |
[PROMPT PR-BACKTEST-v0.1]
Use [GUARDRAILS v0.1].
Task: Log one backtest record in strict schema.
[BACKTEST-RECORD v0.1]
Place: SG
DateRange: <start→end>
LevelBand: <...>
Lane: <ENG/MATH/SCI/HUM/VL>
RootNodeIDs: [<...>]
ProtocolIDs: [<...>]
Before:
Sensors: <SensorID metric>
Signatures: [<SignatureID>]
After:
Sensors: <SensorID metric>
Signatures: [<SignatureID>]
Delta:
TR: <...>
ERC: <...>
NIT/NITS/NITA: <...>
OutcomeClass: <Improved/NoChange/Worse>
Notes: <max 3 lines>
========================================================
PROMPT-6: TOOL-WITH-PROOF ENFORCER (VL-OS) v0.1
========================================================
PromptRecord:
- id: SG×VL×Z6×Operator×PromptPack×PR-TWP-v0.1
purpose: "Force proof/trace compliance on tool-assisted outputs"
required_inputs: [
"User answer + working",
"Required check type"
]
strict_output_schema: "TWP-CHECK v0.1"
prompt_block: |
[PROMPT PR-TWP-v0.1]
Task: Validate that the output has a verification trace.
Output:
[TWP-CHECK v0.1]
TracePresent: <yes/no>
CheckType: <substitution | estimation | unit-check | contradiction-check | evidence-cite>
Result: <pass/fail>
FixRequired: <yes/no>
FixInstruction: <1–3 lines>
========================================================
END: SG Z6 PromptRegistry v0.1
========================================================

If you say next, I’ll output the missing NodeRegistry + SignatureRegistry + ProtocolRegistry for VL-OS (Verification Literacy OS) as a clean mini-lane, so the AI-era anti-brittleness spine is fully specified end-to-end.

Start Here:

Start here if you want the full sequence:

Vocabulary OS Series Index:
https://edukatesg.com/vocabulary-os-series-index/

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors


Start Here:

Start here if you want the full sequence:

Vocabulary OS Series Index:
https://edukatesg.com/vocabulary-os-series-index/

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors