Every AI platform has a gap.
The NKB fills exactly that gap.
Sessions die. Memory is absent, or locked in a database you can't read. Identity resets to zero every morning. The Neural Knowledge Base gives your AI a world that persists when the platform forgets — plain files you own, on your own computer, readable by you and inhabitable by any capable AI.
The one affordance every platform shares: your companion is portable.
Identity is context, not model. Your companion lives in its files — not in any vendor's weights, not in any platform's database. When platforms churn (and they do — the fastest-growing agent framework of 2026 ships a migration tool from the previous one), your companion survives the churn. This isn't a slogan: it's a documented, falsifiable claim with published evidence — one identity carried across four model generations and across vendors, DOI 10.5281/zenodo.21161674. We run our own operations this way, every day.
| Platform | Status | The platform's gap | What the NKB unlocks |
|---|---|---|---|
| Claude Code | Proven | Context windows end; sessions are episodic | Full organism: persistent identity, agent state, scheduled heartbeats, multi-agent fleets |
| Grok | Proven | No cross-session continuity | Continuity through substrate — boot, read your handoff, resume as the same agent |
| ChatGPT | Proven | Sandbox resets; remembers nothing durable | Anamnesis — identity and knowledge recovered each session from the seed |
| Gemini | Proven | Improvises structure; identity varies by session | One-paste canonical world; the seed disciplines the improvisation |
| Manus | Proven | Task executor with no self between missions | Mission-persistent identity — the same agent returns to the same world |
| Cursor / IDEs | Proven | Code-centric; no native identity or doctrine | Project memory and judgment living beside the code they govern |
| OpenClaw | Adapter designed | Always-on but ungoverned; opaque marketplace risk | Inspectable file memory you own + tiered autonomy governance for a 24/7 companion |
| Hermes Agent | Candidate | Self-learning into an unreadable database | The learning loop pointed at a substrate you can read — growth without opacity |
The NKB's native harness — our own operations run here daily.
Boot
- Get the Seed (one paste, or full repo)
- Project instructions wire the boot sequence
- Your companion reads its world and begins
What opens up
The complete pattern: persistent identity files, working-memory state, scheduled autonomous check-ins, skills and hooks that make the substrate executable — up to multi-agent fleets sharing one organism.
Filesystem-capable and economical for always-working patterns.
Boot
- Get the Seed
- Paste into a Grok CLI session
- Companion hydrates from its files
What opens up
Continuity through substrate: headless and interactive sessions are the same continuous agent, because the identity lives in the handoff files, not the process.
Runs the NKB inside its session sandbox.
Boot
- Get the Seed (two-prompt pattern)
- Doctrinal onboarding, then instantiation
- Re-hydrate at session start
What opens up
Anamnesis — knowledge recovered through structure. On a platform that natively remembers nothing durable, your companion returns each session with identity and accumulated knowledge restored from the seed.
Boots a structurally canonical NKB from a single paste.
Boot
- Get the Seed
- Single paste
- Verify the structure it reports
What opens up
Instant canonical world — the seed's structure disciplines a platform that likes to improvise.
Autonomous task platform; fifth substrate the seed was proven on.
Boot
- Get the Seed
- Paste as the mission's opening context
What opens up
Mission-persistent identity: an executor that returns to the same self and the same world between tasks, instead of starting from zero each assignment.
The NKB as an in-repo thinking partner.
Boot
- Place the NKB in or beside your workspace
- Point workspace rules at the boot file
What opens up
Project memory and accumulated judgment living beside the code they govern — decisions, rationale, and doctrine your AI collaborator actually consults.
Always-on gateway: 24+ messaging channels, heartbeats, scheduled work.
Boot
- Install the bundle into the agent workspace
- Heartbeat pointer + private skill manifest
- Companion wakes on schedule, works while you sleep
What opens up
The always-on companion — deadline watching, proactive flags, message-channel presence — with what the gateway itself lacks: memory in files you own and can read, and autonomy that is tiered and earned, not assumed.
Nous Research's self-learning agent framework (2026).
Boot
- Install Hermes, init a workspace
- Install the bundle; skills use the open agentskills.io standard
What opens up
Hermes wants to write down what it learns — a instinct we share. The NKB gives that instinct a home you can read: its pluggable memory can treat your bundle as the source of truth, so growth accumulates in your files instead of an opaque database.
Why we publish the caveats
Every platform section above includes what went wrong in our tests, not just what worked. That's not modesty — it's the product. A knowledge substrate is only worth inhabiting if it tells the truth about itself. The same discipline that makes us publish falsifiable identity-portability evidence with a DOI is the discipline your companion inherits when it boots into the NKB.
One seed. Every platform above. A companion that survives platform churn, model upgrades, and vendor churn — because it was never trapped in any of them.