The platform, piece by piece

Every landscape needs a navigator. Yours is a small, contained service that does one job: take an intent — a wish — clean it, check it, and route it to the right agent, workflow, or expert on the right machine.

The unit of serious work: expertise captured as a Nix-built DAG of sandboxed steps, where the hard decisions pass through committees and every run is a record you can replay.

The long-running half of the system: Nix-declared, schema-validated, sandboxed components that hold state and capabilities — so workflows can stay stateless and disposable.

Reproducibility as consensus: a committee of independent guilds certifies every build, threshold cryptography guards every key, and the maintainer keeps a personal veto no platform can override.

Face it: everybody can get hacked. Tixim is built on that assumption — zero ambient authority, kernel-enforced closures, text that is tainted until proven clean, and a supply chain that must reproduce or fail loudly.

Identity, storage, secrets, signatures, connectivity, source control — everything a platform company would own is a protocol here. Six layers, each doing one thing.

A run is not exhaust — it is training signal with provenance. Experiences flow back into the system, experts sharpen, and an ontology gate keeps the loop from hallucinating itself off the rails.

From lending your idle machine to a guild, to a global cluster of user-controlled confidential instances — admitted by trust circles, scaled on demand, owned by no one.