Add one or many hypothesis nodes (with optional parent edges). Pass a list of one to create a single hypothesis. Parents may be created by the same call in any order. The whole batch is validated before anything is written, so a rejected call creates nothing.

Wire hypotheses that already exist, without recreating either. Use it to grow a graph forward: when a pipeline gains a stage, the goal must depend on the NEW last stage, or it reports itself achieved as soon as the first stage verifies while the rest sit untested. You do not need to remove the old edge — DEPENDENCY is AND and the later stage already depends on the earlier one, so adding only tightens the condition. Validated like creation: unknown nodes, a goal used as a DEPENDENCY parent, and cycles are refused before anything is written, and an edge that already exists is a no-op.

Reclaim stale leases and select the next target(s). A claimed node is reserved for you until you record its result, so ask only for what you will probe before your next call — anything you hold and do not report is work nobody can do. A batch never contains two competing answers to the same question. Returns a list; each entry may carry min_depth when the node is under conflict review.

Record one result, or many in one call, and update the belief state. Auto-captures git context_hash + git_branch when unset. Record against the hypothesis whose statement you actually tested: evidence against a goal is refused, and evidence against a premise a composition assumed corrupts a confirmation that is still true on its own. Ran several experiments this turn? Report them together with results — one call, applied in order.

Restart a live lease's clock because the experiment is still running. Use this instead of a very long TTL: the lease exists so work held by a caller that vanished comes back, and a long TTL makes that recovery as slow as the longest experiment.

Hand leased nodes back without recording a result — for work you have decided not to run, or for resuming after a context reset you cannot report on. Omit claim_ids to release everything you hold.

Manually override the status of one or many nodes. Every id is validated before anything changes, so a bad id never leaves a partial update.

Walk DEPENDENCY ancestors, flip VERIFIED → NEEDS_REVISION.

Walk REFINEMENT ancestors, flip IN_PROGRESS → VERIFIED (depth-capped).

Report all goal nodes, target metrics, progress counts, and whether the global stop holds.

List recorded conflicts — sets of assumptions that cannot all hold together, with which members are exonerated and which remain suspects.

Name the cheapest experiments that would OVERTURN what a goal currently concludes, ranked by how little evidence holds each belief up. Answers the question a reviewer actually asks — not what do you believe, but what would it take to be wrong. A belief confirmed by elimination ranks first however confident the engine is: nothing ever measured it, which makes it both the weakest link and the cheapest thing in the graph to settle. Read-only — it issues no lease and changes nothing.

Propose the single most informative next experiment: re-test a conflict suspect at depth while any remains, otherwise the closest alternative combination that no recorded conflict rules out.

Return a depth+width-bounded subgraph with credible intervals.

Render a Mermaid flowchart with depth+width bounding + elision.

Query/filter/sort nodes and return a Markdown table. Use view for the questions actually worth asking — 'frontier' (what is still open), 'settled', 'verified', 'revision' (what is under revision), 'stale' — rather than assembling a status filter by hand. stale_only=true keeps only confirmations made against a commit that is no longer checked out: they are not refuted, but nothing has re-established them since the code moved.

Return the evidence trail for a node (newest-first).

Return live (unconsumed, unexpired) claims for resuming work.

Narrate what has been settled so far, in order, and how — separating what an experiment paid for from what the engine inferred for free, and calling out beliefs that were later withdrawn. Use it to brief a human, to write a summary, or to re-orient yourself after a context reset: the other read tools show the current state, this one shows how it was arrived at. Pass since to get a diff instead — what changed between then and now, which is the answer a standup or a PR description wants.

Which belief state you are connected to, and how it was chosen. Reports the workspace id, which of the four resolution layers produced it, where the database lives and whether it exists yet. Call it when the graph is unexpectedly empty or two clients disagree about what has been established — that is almost always one project resolving to two workspaces.