Code Rooms
# Runtime Requirements
KOGNIT1V is designed to run inside an agent environment that can read local
files, execute local validation commands, and load Codex skills.
## Minimum
- Codex or compatible agent runtime with local skill support.
- Node.js capable of running `scripts/validate-kognit1v.mjs`.
- The skills in `skills/` copied or plugin-loaded into the agent environment.
## Recommended
- m1nd MCP for structural repository investigation.
- Git CLI for local repository hygiene.
- A worker-agent mechanism for bounded implementation lanes.
- Provider API keys only in the user's local environment, never in this repo.
## Optional External Systems
KOGNIT1V can work inside any local project when the agent runtime has file and
command access. Private product repos are intentionally not bundled here. This
repo packages the cognitive layer: skills, contracts, proof discipline, and
handoff formats.
See [`TOOLCHAIN.md`](TOOLCHAIN.md) for the exact boundary between bundled files,
host-provided tools, optional runtimes, and excluded private systems.
## Install Semantics
Installing KOGNIT1V has layers:
| Layer | What installs | Command |
| --- | --- | --- |
| Repo validation | contracts, examples, proof scan | `npm run validate` |
| Safe install proof | temporary Codex home install smoke | `npm run smoke:install` |
| Skill bundle | KOGNIT1V and support skills into Codex | `npm run bootstrap -- --install-skills` |
| Toolchain doctor | host capability report | `npm run doctor:tools` |
| m1nd optional runtime | clone/check/install m1nd CLI/MCP | `npm run bootstrap -- --with-m1nd --install-m1nd` |
| Project repos | any checkout the user authorizes | bring your own checkout; KOGNIT1V operates through skills |
The default install does not install m1nd automatically. That is deliberate:
m1nd is a runtime dependency with its own release, build, and MCP integration
surface. KOGNIT1V can detect it and help install it only when explicitly asked.
## Environment
Use `.env.example` as names-only documentation. Live `.env` files stay local and
ignored by git.
## First Agent Command
```bash
npm run validate
```
The result is the repo's first proof that the package is structurally safe to
load.
