1
Assess
G Tracker
OutputG-index baseline + trend seed
TriggerFirst step of each new block
Next: route to Zone Coach for readiness gating.
Method
How IQMindware works
The core loop is simple: assess baseline, regulate readiness, train capacity, then run delayed re-checks to test whether gains carry over under changed conditions.
Skills training and self-regulation, not diagnosis or treatment.
Method spine
Assess to Regulate to Train to Re-check
Each step has a specific output and trigger so users know what to do next.
to
2
Regulate
Zone Coach
OutputFlat / Zone / Spun Out
TriggerBefore every training session
Next: choose full session, light session, or reset.
to
3
Train
Capacity Gym
OutputSession log + probe outcomes
TriggerZone state confirmed
Next: accumulate sessions, then run delayed re-check.
to
4
Re-check
G Tracker
OutputUpdated baseline versus prior marker
TriggerAfter 7 to 14 sessions
Next: adjust load based on transfer evidence.
Zone Coach decision gate
One check, three routes
Zone
Proceed: full training block.
Flat
Downshift: light or consolidation session.
Spun Out
Recover first: skip training and re-check later.
Protocols
What each tool does
The tools are designed to work as one loop, not as isolated apps.
G Tracker
Baseline and trend checks
What it tracks
Short repeatable reasoning and control markers for trend direction.
When to use
Start of block and delayed re-check windows.
Zone Coach
Readiness and re-entry routing
What it tracks
State output for safe and useful training decisions.
When to use
Before each Capacity Gym block.
Capacity Gym
Adaptive training for carryover
What it trains
Capacity control under changing task wrappers and probe conditions.
When to use
When readiness gate indicates trainable state.
Mindware Gym
Unified daily flow
What it will do
Combine assess, gate, train, and logging in one guided workflow.
When to use
Daily default workflow after launch.
Transfer checks
How carryover is tested under change
Carryover is tested with condition shifts, not inferred from repetition in one fixed task format.
Game swaps
Same cognitive demand, different game wrapper.
cross-format checkBoundary and trap probes
Rule edges test whether strategy is robust under variation.
boundary checkDelayed re-checks
Re-test after training blocks to check retention across time.
time-lag checkMission context use
Apply scripts in real tasks and log outcomes.
applied checkInspect protocol definitions at /proof#protocols and published summaries at /proof#data.
Practical cadence
Example week and routing
A simple default schedule that adapts to readiness output.
| Day | Flow | Time |
|---|---|---|
| Mon | Assess + Regulate + Train | about 25 min |
| Tue | Regulate + Train | about 20 min |
| Wed | Rest or low-load day | - |
| Thu | Regulate + Train | about 20 min |
| Fri | Regulate + Train | about 20 min |
| Weekend | Delayed re-check window if due | about 5 min |
Busy day
Run Zone Coach only and preserve continuity.
Low readiness day
Downshift or reset before training.
High-stakes day
Avoid adding new load before mission-critical tasks.
Transparency
What is published and what stays private
Protocols are public. Published summaries are aggregated. Personal logs remain user-controlled and exportable.
Publication policy
Flow: local session trail -> aggregated summary -> published proof update.
No raw personal logs are published.
Protocol publication
Open protocol details are listed in /proof#protocols.
Data summaries
Aggregated evidence summaries are published at /proof#data with caveats.
Export control
Users can export their own training trail from the tool layer.
Scope and boundaries
Scope: skills training and self-regulation workflow.
Boundary: not diagnosis or treatment.
Variability: outcomes vary across users and contexts.
Next step
Run the loop once, then re-check under change.
Start with one guided session and create your first baseline today.