Safe archive workspaces

ITHZ turns project archives into verifiable working memory

A local-first toolkit for people who need safer archive workspaces, inspectable native tooling and AI agents that remember project decisions without hiding them in a black box.

Download free preview Explore the product

.ithz A compact zone for files, metadata, hashes and memory records.

Drive Use archive content from Explorer or Total Commander without giving up verification.

MCP Give agents focused project memory instead of repeated full scans.

Native Inspect the engine, CLI and safety gates behind the product.

Product layers plus the research story

ITHZ is for projects where files, context and decisions keep drifting apart. MCP gives agents a deterministic memory zone, Drive handles archives as workspaces, Native keeps the engine inspectable, and the Theory/Experiment/SIM track explains why the system exists and where it may become practical.

Windows first

ITHZ Drive

A Windows shell product for people who want archive safety without leaving their normal file workflow: Explorer/Total Commander actions, open/unmount-as-drive, verify, extract and create-zone.

Explorer/TC menu Open as drive Safe verify

Engine layer

ITHZ Native

The inspectable C++ CLI underneath Drive. It gives technical users AVX2/scalar builds, deterministic verify modes and direct access to pack, inspect, list, extract and update workflows.

C++20 AVX2/scalar CLI/SDK path

Agent memory

ITHZ MCP

A project-owned memory zone for AI agents. Instead of opaque chat memory, it stores decisions, gates, risks, workflow profiles and context packs that can be inspected and versioned.

Context packs Audit trail Memory zones

V017 evidence

Experiment

A public-safe research page for the current ITHKOR Kernel status: finite diagnostics, visible guardrails, first QPU support points and careful claim boundaries.

Kernel notes Phase gates Cautious claims

Theory layer

ITHKOR Theory

A public theory page for Special ITHKOR: the bounded hypothesis behind finite information geometry, QPU-facing observables and project-owned memory.

ITHKOR Kernel model Sandbox evidence

Practical research

ITHKOR-SIM

A practical simulation branch that tests whether finite information diagnostics can allocate compute, checkpoints and compression better than simple controls.

Adaptive budget Toy evidence No physics claim

Free preview

Choose the layer you want to try

Drive is the Windows entry point, MCP is project memory for agents, and Native is the CLI/engine layer for technical inspection.

Drive, MCP, Native Three separate alpha preview packages Open downloads

Public story

What is different

Archives become a workspace, not a blind blob

Traditional ZIP-like tools are good at packing files. ITHZ Drive focuses on the working loop around the archive: open, inspect, verify, extract, create a zone and later unmount cleanly.

Agent memory is explicit and auditable

Generic chat history and RAG indexes are often hidden or hard to reproduce. ITHZ MCP stores decisions, gates, risks, workflow profiles and context packs in a project-owned memory zone.

Large projects get a bounded path

The MCP package now includes large-repo install mode, generated-output pruning and compact intake so codec, media or build-heavy projects do not become a full-scan trap.

The engine can be inspected separately

ITHZ Native exposes AVX2/scalar CLI builds, safe/full-no-write verification, inspect/list/extract workflows and documented limits for technical users.

The research direction is simple to state and hard to prove: find structure that survives the order in which a process is read

Why try it now

The previews are early, but they already show the shape of the product: local files, visible checks, explicit memory and a clean path from personal use to team workflows.

For archive-heavy work

Try Drive when you want a file container that still behaves like a workspace and keeps verification close to everyday actions.

For agent-assisted projects

Try MCP when your agent keeps rereading the same repo and losing durable decisions between sessions.

For technical evaluation

Try Native when you want to inspect the CLI, verify modes and engine behavior directly before trusting the product layer.