vortx-ai/emem/emem-verify-before-publish

emem-verify-before-publish

Network use. The commands in this skill send JSON to https://emem.dev and receive JSON from it. https://emem.dev is the service that the MCP server of the plugin connects to. The commands do not execute what they download. This skill ships no scripts. The commands read no environment variable, key or credential. They read only local files that an earlier step saved from https://emem.dev.

The citations in a draft were correct when you wrote them. This call checks that they still resolve. It checks that the number next to each citation is the signed number. If you ask, it also checks that each measurable claim has a citation.

Step 1: send the draft

Put the draft in texts. This field is an array of strings. Call emem_guard_verdict with this body:

{"texts": ["Bengaluru air temperature is 35 degC (emem:fact:defi.zb493.zezo.zcb35:nflpddk7zsncywguwjzk5koksseqfyx4jnngkuryrnd4aykqlpfq)."],
 "claim_gating": true}

Without MCP, send the same body to POST https://emem.dev/v1/guard/verdict. Read action, reason, citations_found, checked, advisory, and the state of each entry of citations[] in the answer.

For a chat transcript, send messages (a list of role and content objects) in place of texts. For a payload from another framework, such as an OpenAI moderation body or a CloudEvent, name its shape. The tool description in emem_tools lists the shapes.

Step 2: read the verdict

The guard reads a body without texts or messages as empty. It returns allow with citations_found: 0. That is a clean verdict over nothing. Thus, if citations_found is 0 and your draft has citations, the request is wrong.

Recorded runs

The cited fact signs 28.0 degC. On 6 November 2026 at 23:59 UTC:

A run on 28 September 2026 gave the same first two results. On 7 November 2026 at 02:10 UTC, all three rows gave the same results again.

Step 3: act on a deny

Branch on the fix value. Do not branch on the prose.

GEO_ZONE and POLICY_MODULE come from the configuration of the operator, not from the evidence. The codes and fixes are in crates/emem-guard/src/policy.rs.

For correct_value, write the signed value in the sentence. Do not remove the citation. The citation is correct, and the prose is wrong.

A citation with state not_held_here never causes a deny. The responder cannot tell it from a token that another node minted. Resolve it on the node that minted it.

What the guard does not check

The guard does not check that the cited band is the quantity that the sentence names. On 6 November 2026, this draft got allow: "Bengaluru rainfall is 28.0 mm", with the temperature token from step 1. The value agreed, and nothing compared "rainfall" with weather.temperature_2m.

Thus you must check the band yourself. Resolve the token with emem_memory_token_resolve. Its band must be the quantity that the sentence names, and its cell must be the place.

Claim gating finds fewer claims than a reader does. A sentence is a claim only when it has an anchor and a number. The number needs a unit, or it must be a named index value such as NDVI 0.45. The anchor is an ISO date, coordinates, a year, or a word such as "in", "at" or "near" before a capitalised word (crates/emem-guard/src/claim.rs). Results on 7 November 2026, with claim_gating: true and no citation:

Also, one citation that resolves turns off claim gating for the whole request (crates/emem-guard/src/policy.rs). A draft that cites one fact and then makes ten claims without a citation gets allow. Thus an allow does not prove that each claim has a citation.

The hosted route is advisory. To enforce the verdict, run your own node. GET https://emem.dev/v1/guard/selfhost returns the procedure. The same procedure is in crates/emem-guard/SKILL.md in the repository.

Three different checks

A draft can pass the first two checks and fail the third. This is the most frequent failure: a correct, signed number next to a claim that it does not support.

Where this step goes

Run it after you compute a result and before you send the sentence about it. In a pipeline, make it the last stage before output. Treat a deny as a stop.

Pitfalls