Enfold

When two agents disagree, you get a conflict you can settle, not a silent guess.

Enfold stores durable facts on your machine, with evidence and history on every claim. When two writers put different values in the same typed slot at equal authority, it opens a conflict, returns a receipt instead of a value, and waits for a human. There is no hosted service. Memory stays local.

The moment

`python -m enfold.demo` (or `enfold demo`) walks that contract on a disposable store. It never opens `~/.hermes/memory_store.db`. Conflict ids change each run. This is a real run on this tree:

Enfold demo
Disposable store. Offline. Local-lexical retrieval.
This is not a bag of notes: current state, conflict, and human resolve are first-class.

1. Client A writes typed state
   client: demo-client-a
   claim:  env:staging.port = 3100
   write:  outcome=add fact_id=1 authority=0.5

2. Client B writes the same slot at equal authority
   client: demo-client-b
   claim:  env:staging.port = 3200
   write:  outcome=conflict fact_id=2 authority=0.5

3. Recall returns a conflict receipt, not 3100, not 3200
   current facts returned: none
   receipt: [conflict:f6a352c0-8976-457e-b57b-e953dddd5bcb slot:env:staging.port members:2 - do not treat either as current]
   conflict_id: f6a352c0-8976-457e-b57b-e953dddd5bcb
   members: [1, 2]
   This is the moment. A competito