Mission control
The integrator preserves one objective and recruits only the cognitive transformations the work actually needs.
Collaborative Dynamics · MIND 2.1.1
MIND gives an AI harness distinct cognitive Faculties, local semantic capability reminders, Capability Promotion, and the two-part TestForge verification gate—then reunifies the work into one accountable result.
Codex-first plugin · local runtime · deterministic release ZIP · MIT License · Nova not required
Install
The release contains the MIND plugin, prompt-submit hook, local reminder runtime, twenty-capability reminder map, sixteen Faculties, Capability Promotion, both TestForge roles, an offline verifier, and the optional Core wheel.
Get augment-of-mind-v2.1.1.zip from the latest GitHub release.
Ask Codex to install and enable MIND by Collaborative Dynamics. Review the proposed local file and plugin changes before approving them.
Open /hooks, inspect the exact installed MIND hook bytes, and decide whether to trust them. Then start a new task so the host discovers the plugin.
What MIND adds
The integrator preserves one objective and recruits only the cognitive transformations the work actually needs.
A local semantic reminder layer keeps installed abilities within reach without pretending proximity is selection or authority.
Software Verification builds the readiness case; Verification Reviewer independently attacks it.
Use $augment-of-mind to help me decide whether to run a two-week pilot. Separate evidence from assumptions, identify the smallest reversible test that could change the decision, and return one recommendation.
Arm's Reach
MIND can compile a local semantic neighborhood of potentially relevant capabilities from the active reminder estate. The prompt hook handles bounded pre-turn recall when possible; the direct local query path remains available for explicit contextual association.
A reminder is not a ranking, recommendation, activation, installation check, health check, permission, or authority grant. Nova or another host agent still decides what actually belongs in the work.
One integrator, sixteen Faculties, Capability Promotion, Software Verification, and Verification Reviewer. The profile is structurally checked; broader behavioral qualification and fresh-host delivery remain separate claims.
How capability reminders work · Inspect the local Core runtime
The Faculty map
Call the integrator when several transformations must contribute. Call one Faculty directly when one bounded transformation clearly owns the job.
Govern and persist
Understand and evaluate
Create, express, and act
Release integrity
The release builder refuses dirty tracked source, builds the Core wheel twice under a fixed source date, requires byte identity, creates the allowlisted customer archive, extracts it safely, compares the staged and extracted trees, and runs the offline release verifier.
2.1.1
One integrator, sixteen Faculties, Capability Promotion, both TestForge roles, local reminder assets, prompt hook, and direct local association runtime.
0.2.0
Local Python runtime and optional wheel with SQLite state, authored semantic representations, bounded receipts, and no required hosted service.
Recovery
Keep the exact request, host, operating system, package version, and full error. Distinguish installation, discovery, hook trust, database state, reminder delivery, and model behavior before changing anything.
Confirm the intended marketplace or extracted package, enable MIND, and start a new task.
Record the exact discovered handles. A file on disk does not prove host discovery.
Inspect the trusted hook bytes, Python environment, database path, and local runtime. MIND can still use capabilities the host exposes.
Privacy
No analytics, trackers, credentials, or required hosted MIND service. Local state stays at the database and receipt paths selected by the operator.
Data and privacy detailsSecurity
MIND cannot enlarge a sandbox, approval policy, account scope, or tool grant. External actions retain their own authorization boundary.
Security policyTerms
MIND is MIT-licensed software without warranty. Users remain responsible for consequential judgment and separately authorizing external action.
Terms of useRelease
The deterministic customer archive includes its exact file manifest, offline verifier, optional Core wheel, build receipt, and SHA-256 checksum.