Make AI yours.
Keep your intelligence.
One owner-controlled source archive. Many compatible AI tools. Your original words, files, images, and projects stay recoverable even when you switch devices or providers.
Learn to own the system
Follow an eight-stage course, from importing the first photograph to a verified portable backup.
Bring your original files
Uses the existing Creator Vault storage, not an imitation. Images and file bytes live in IndexedDB on this device.
Explore the complete mind and agent atlas
126-billion virtual Omni addresses, the original 20-name pantheon, Jesus and Buddha source lenses, Leonardo da Vinci, the Turtle worker pipeline, and the existing NT-1 source catalogs. The source files remain unchanged.
Consent before context
Manual source packets work today. Live cross-provider and cross-device sync need separate approved integrations. Each route shows its real status.
Build your own AI system
Use your own files and your own rules. These lessons teach practical personal-intelligence workflows; training a neural model is an optional advanced subject.
Files & images
Add documents, original images, media, code, and exports. Everything stays in the existing Tabor Creator Vault in this browser profile until you choose to export or share it.
Import into the shared Creator Vault
Import keeps the original binary bytes. For ZIP and conversation-specific import, use the full Creator Vault.Saved source inventory
Memory matrix
Make explicit records that point back to your source IDs. Original facts, interpretation, working notes and creative fiction stay distinguishable.
Knowledge records
Ask my archive
Search the actual local index and assemble a reviewed packet for an AI. This is source retrieval, not a claim that a live model is running in the page.
Approved AI handoff
No sources selected.
Packet export never uploads data automatically. Images remain local; upload an authorized original separately if the receiving tool needs pixels.Connect AI
One knowledge source can serve different AI applications, but each provider requires its own supported connection and explicit permission. The app will never show “connected” without a successful test.
Local MCP bridge for laptop AI clients
The included mcp-server.cjs is read-only and runs locally through standard input/output. Select a folder of your originals on the laptop and explicitly configure an MCP-capable client. Browser IndexedDB does not automatically synchronize to this folder; export or copy owner-selected originals first.
NATHAN_VAULT_DIR="/absolute/path/to/your/authorized/files" node mcp-server.cjsGet local MCP server source
node import-backup.cjs /path/to/my-backup.zip /path/to/my-approved-mcp-folderThe importer verifies ZIP and SHA-256 before copying originals; it never uploads them. Run once for each backup part, then point NATHAN_VAULT_DIR at the approved folder.
Other services can accept the portable JSON handoff under Ask my archive. No keys or passwords belong in exported packets.
Raw NATHAN OS module crosswalk
01 · Zero-Bias Core → tested validation and typed source rules, not kernel memory purging.
02 · Immutable Vault → original-byte IndexedDB and SHA-256 ZIP preservation, plus versioned future cloud design.
03 · Multi-AI Gateway → portable handoff and optional local MCP, not universal account synchronization.
04 · Terminal → this installable, phone-and-laptop PWA shell.
The Nathan Tabor method
An educational operating approach: use AI as computation around independent, owner-held knowledge, with original-language preservation, cumulative projects, and portable recovery.
How it was built
This app extends the existing ONE and TABOR 1-2-3 FACTORY ecosystem. The shared Creator Vault, original-byte backup engine and tabor123.project.v1 portable contract existed before this new learning interface.
Source conventions distinguish user-authored methodology, stored originals, software implementations, external facts, and creative interpretations.
Read implementation dossierBackups & audit
Export the real original bytes and memory configuration. A successful download is not a verified restore; test recovery before deleting any source.
Original files + memory records
Creates ZIP parts with complete stored file bytes, SHA-256 checksums and the saved memory/lesson state. Existing Vault records are not removed.
Backups are local downloads; save an off-device copy manually. Large libraries generate multiple parts.
Portable knowledge JSON
Export only memory records and lesson progress, without original media bytes; useful for small migrations.