IQMindware

Train general intelligence, then prove carryover.

About IQMindware

Train general intelligence that carries over.

IQMindware is built for far transfer in real conditions. We combine cognitive capacity training, state-aware regulation, and transparent proof practices so users can test whether methods carry over beyond the training context.

Start here View proof
Skills training and self-regulation, not diagnosis or treatment.
Who we are

Built for applied cognition, not score theatre

Mission

Help people think clearly under load and recover faster after disruption.

IQMindware is a Mindware Lab product focused on transferable cognitive performance. We design tools that move from baseline assessment to state gating to structured training and delayed re-checks.

The objective is deployability in real missions: decision quality, controlled execution, and practical script use across changing contexts.

Why this exists

Carryover under change requires a different architecture.

Many cognitive products optimise repetition in one fixed format. IQMindware is designed to test whether methods hold after condition changes, not only inside one training wrapper.

That is why protocol structure, gating logic, and delayed checks are first-class design requirements rather than optional extras.

Principles

What governs the system design

1

Transfer is the standard

Methods are evaluated by carryover under changed conditions.

In practice: game swaps, boundary probes, and delayed re-checks are built in.
2

Resilience is part of intelligence

Reasoning quality must be accessible on non-ideal days.

In practice: Zone Coach routes sessions by readiness state.
3

Mechanism over hype

Protocol logic and decision rules are operationalised.

In practice: scripts, stop rules, and explicit routing replace vague motivation cues.
4

Transparency over black box

Users can inspect what is trained, tracked, and published.

In practice: protocol logic is available at /proof#protocols.
5

Applied use is the target

Value is judged by execution quality outside the app layer.

In practice: mission framing and re-entry protocols are part of the workflow.
Difference

Typical pattern vs IQMindware approach

Typical
xFixed-format repetition dominates measurement.
xLittle testing under condition changes.
xProtocol logic often not inspectable.
IQMindware
->Game swaps and boundary probes are built into sessions.
->Delayed re-check windows test retention under change.
->Protocol and evidence surfaces are public.
Published protocols Published data Method page
Method snapshot

Assess to Regulate to Train to Re-check

1
Assess
G Tracker

Create baseline and trend marker.
to
2
Regulate
Zone Coach

Route session intensity from readiness state.
to
3
Train
Capacity Gym

Run adaptive block with embedded transfer checks.
to
4
Re-check
G Tracker

Test carryover after a delayed session window.
Open full method
Evidence posture

What we say, what we do not say, and what we publish

CanWe can say
Designed to train general intelligence capacity and cognitive resilience.
Designed to test carryover under changed conditions.
We track and publish aggregated summaries with caveats.
NoWe do not claim
Diagnosis or treatment outcomes.
Outcome certainty across all users.
Clinical proof framing.
DataWhat is published
Protocol logic and updates.
Aggregated summaries and caveats.
Claims policy boundaries.
Claims policy Published data Published protocols
Scope
Claims and ethics boundary
Scope: skills training and self-regulation workflow.
Not clinical: no diagnosis or treatment service.
Variability: user outcomes vary with baseline, context, and adherence.
Testimonials: individual cases do not define universal outcomes.
Read claims policy
Data and privacy

User-controlled trail, aggregated publication only

PublishWhat is published
1Aggregated summaries with caveats and update dates.
2Protocol documentation and versioned changes.
3Claims boundary documentation.
Published summaries Protocol index
Roadmap

Live now and next

Live now
Core tool layer
1G Tracker
2Zone Coach
3Capacity Gym
Protocol and data surfaces are already public.
Coming soon
Mindware Gym integration layer
1Unified daily workflow experience
2Linked script and transfer workflow
Release timing remains subject to build status.
Ongoing
Proof cadence maintenance
1Protocol updates and change logs
2Aggregated summary updates
3Claims boundary reviews
Evidence surfaces stay inspectable and current.
Methods you can inspect and test

Start with baseline. Test from there.

Assess baseline, route by readiness, train with structure, and check carryover under changed conditions.

Start here Open tools Inspect proof posture