haft_entity
Proactively establish one minimum non-binding EntityOfConcern when current Work supplies a concrete operator-named or agent-inferred durable receiving use; known absence alone is insufficient
How to use it
Project documentation lists haft_entity for the Haft MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
FULL HAFT LISTINGOther tools in Haft (11)
Runner-neutral WorkCommission authority and lifecycle records
Decision contracts: invariants, claims, evidence, baseline lifecycle
Expert raw MemoryChangeSet validation/admission through a nested request envelope; ordinary agents use haftentity, and validation never admits automatically
Task-local SWE MethodRun cards: pull gates before non-trivial work, close with evidence or waivers
Non-binding facts, observations, caveats, and rationale with typed anchors, validation, and optional freshness
Read setup status, prepare a non-binding initial profile review, or prepare an explicitly requested predecessor-pinned scope relation change; a missing relation never gates TargetSystemSpec lifecycle; haft init automatically admits only a complete supported singleton as origin=detectordefault and in
Frame problems, declare comparison dimensions with indicator roles
Project search/status, code graph, source-native FPF query/lookup/inspect, and typed-memory resolve/neighborhood/recall
Lifecycle management for every artifact kind
Explore variants with diversity check, compare under parity
Typed SpecSection lifecycle projection over project SQL editions; FPF source compatibility is assessed separately; manual CLI gates approve, rebaseline, or reopen baselines