Compatibility

Small adapter surface, explicit write path.

WriteFence is a local admission controller for memory-write traffic. The alpha target is intentionally narrow: put WriteFence in front of a memory store that accepts HTTP document writes, then inspect decisions through the CLI, WAL, quarantine log, replay engine, and local UI.

Works today

• HTTP reverse-proxy deployment.
• LightRAG-style POST /documents/text writes.
• LightRAG-style paginated reads and delete calls for local dedup checks.
• Local WAL, violation logs, quarantine review, replay, and operator UI.
• Optional semantic dedup with Ollama embeddings and Qdrant.
• MCP server exposing operator tools.

Expected upstream endpoints

Write admission is enforced on:

POST /documents/text

The accepted request body should include:

{
  "text": "[STATUS] memory text",
  "description": "optional description"
}

For dedup support, the upstream should also provide:

POST /documents/paginated
DELETE /documents/delete_document

Other paths are proxied through without admission decisions.

Optional semantic dedup

./bin/writefence --addr 127.0.0.1:9622 --upstream http://127.0.0.1:9621 --embed-url http://127.0.0.1:11434 --qdrant-url http://127.0.0.1:6333

If either dependency is absent, semantic dedup is disabled and WriteFence keeps running with deterministic local rules.

Not in alpha scope

• Hosted SaaS, billing, multi-tenant administration, or user authentication.
• Cloud-managed memory stores.
• Generic adapters for every memory API shape.

Adapters for additional memory backends should normalize the backend's write path into WriteFence's document-write contract, then let the existing admission, WAL, quarantine, replay, and UI surfaces do the work.