writfold

A local knowledge engine for agents

Keep the context.
Know what supports it.

Your next session should inherit more than a summary. Writfold is being built to keep the evidence, history and approval behind your knowledge attached — and open to inspection.

Explore the workflow Read the project guide

In development Local-first · Linux x86_64 / WSL2 target

No installable Rust product yet. This is the direction, not a release announcement.

Knowledge with a record.

More than an answer to remember.

Three goals guide the implementation. The end-to-end workflows are still planned.

Keep the evidence.

Retain the source, exact revision and bytes behind a claim. A reference should lead back to what was actually read, not just where it once lived.

Evidence, not automatic truth

Review what changes.

Propose knowledge before admitting it. Keep approval and publication explicit, with an inspectable history of what changed and who authorized it.

Follow the intended workflow

Carry context forward.

Ask for a bounded view of a named context, with supporting evidence, contradictions and gaps. Keep work and personal authority separate.

Understand context boundaries

Start with one source

From a useful note to inspectable context.

This is the intended local workflow, not an executable quickstart. Production commands and a tested demo will accompany a qualified release.

  1. Choose a named context.

    Decide which project's knowledge and authorization policy you are working within.

  2. Capture the source.

    Retain exact evidence and its identity. Acquisition records what was obtained; it does not approve a claim.

  3. Propose, then approve.

    Connect a proposed claim to evidence. Assess support and contrary evidence separately, then obtain the approval required by that context.

  4. Publish and retrieve.

    Publish the authorized change with recoverable history. Retrieve a bounded context that keeps its evidence and unresolved gaps visible.

Scribes · planned integration model

Connect a tool with a small script.

A scribe is intended to help Writfold find and read a source: a repository, a document service or your team's tools. Writfold will manage acquisition and retain the returned evidence as an immutable record called a writ.

  1. SourceYour tools & documents
  2. ScribeAcquire evidence
  3. WritRetain exact evidence
  4. ProposalReview under policy

Scribes acquire evidence; approval stays with your knowledge policy.

The production scribe host, SDK and catalog workflow are not released. Generated scripts are not automatically trusted. No storage-backend integration is claimed by this site.

Read about scribes

Work in progress

A real foundation. Not a finished product.

Writfold is the Rust successor to kctx. The reference history is preserved; historical Python behavior is not a claim that the Rust product is complete.

Implemented foundations

Domain, wire & runtime boundaries

The workspace includes checked nominal identities, bounded typed JSON, canonical signed operations, protocol admission, filesystem primitives and byte-preserving source syntax.

The development writfold-ref host supports conformance work. It is not the production CLI.

Still being qualified

Semantics & complete workflows

Broader Rust semantic proofs, operational protocols, storage, publication and recovery, scribes, production CLI and release packaging remain open.

There is no production install command or downloadable release advertised here.

Evidence has a scope.

Selected foundations have source-bound development evidence. Those results do not qualify the new Omnigraph backend or complete Rust workflows. The implementation and detailed records are currently private; no public release assurance package is available yet.

Read the status and assurance boundaries

Go a little deeper

Understand the direction. Follow the progress.

A public guide to the model and architecture taking shape. Installation, quickstart and recovery instructions will accompany a qualified release.

Project guideThe model, active platform and development direction Evidence & contextWhat a source supports, and what it cannot authorize Scribes & writsThe planned acquisition and immutable evidence model Architecture directionRust, the Omnigraph companion and reading views Status & assuranceImplemented foundations, remaining work and claim boundaries

The updated architecture targets Omnigraph as the primary local storage companion, with Markdown and Obsidian reading views. These integrations are planned, not shipped.