emem

Plugin emem from marketplace emem in Vortx-AI/emem. Commands read from the repo's manifest — today.

Skills (19)

• emem-device-traces

  Reads and checks the signed activity records (OS traces) emem holds for devices such as robots, drones, satellites and sensor hosts. Lists enrolled devices and their assurance tier, and resolves an emem:trace token to its signed OS trace. Re-verifies the trace (segment chain, clocks, required layers

• emem-document-evidence

  Turns a scanned document into signed, checkable evidence with emem. It runs OCR on an image. Then it parses a pesticide-residue lab report: analytes, results in mg/kg, LOQ, printed MRL, exceedances. Or it parses a land record: owners, parcel ids, areas in hectares, places, dates. Each value carries

• emem-eudr-due-diligence

  Produces a signed, Annex II shaped Due Diligence Statement under the EU Deforestation Regulation (EU 2023/1115) for one or more production plots. It says what it proves and what it leaves to the operator. It checks each plot against the JRC GFC2020 forest baseline and the Hansen Global Forest Change

• emem-field-signals

  Answers agronomy questions about one farm field with signed evidence from emem. It gets the boundary polygons of the field. It checks for crop-residue burns over a date window (Sentinel-2 NBR and NDTI plus MODIS burned area). It sums actual evapotranspiration over a season (MODIS MOD16). It fetches

• emem-field-tokens

  Fetches a native-resolution raster field over an area from emem, or the same field over several dates. The result is a signed artifact that anyone can re-derive, not a set of per-cell values. Use when the user needs the grid of values over an area, not one number at one point. Examples are a world-m

• emem-find-similar

  Returns the top-K places most similar to a seed place by cosine over a stored 128-D surface-texture embedding (Sentinel-1 plus Sentinel-2, annual). Use when the user asks for analogues or look-alikes ("find places like Bangalore", "where else looks like the Sundarbans"). The embedding band is retire

• emem-locate-and-recall

  Resolves a place name to an emem cell64 address and recalls signed Earth-observation facts there. Bands include weather, vegetation indices, elevation, soil, land cover, surface water and forest change. Use when the user wants a measurable value at a named place, with an answer that others can verif

• emem-long-horizon-memory

  Keeps the working state of an agent in signed emem notes that stay after its context window ends. A later session, or the same agent after a reset, starts again from bytes it can verify, not from a summary it must believe. It writes and edits notes in the namespace of the agent (emem_memory_create,

• emem-multi-agent-handoff

  Hands work between agents as checkable evidence, not as prose that the receiver must trust, and checks what other agents hand back. Picks the citation token that binds what matters. Puts several readings into one signed bundle. Reads which key wrote a memory note, tells how to check that signature w

• emem-recall-polygon

  Recalls signed Earth-observation facts at sampled cells inside an area in one call. The area is a named region, a bounding box or a GeoJSON boundary. Use when the user asks about an extent rather than a point. Examples are "average NDVI inside this watershed" and "precipitation across the Western Gh

• emem-referential-drift

  Stops two agents, or one agent in two sessions, from reporting different numbers for the same reading. Pins a value to a citation token that another party resolves to the same signed bytes. Grades a value that you are about to say against the signed value. Asks why a number moved when the words did

• emem-research-grade-citation

  Prepares emem facts for use in research. A reviewer must know what a number is, how emem read it, and how to reproduce it. States the estimand that each fact leaves implicit (support, statistic, source pixel). Reads the unit, the valid range enforced at signing, the reader stamp and the pinned sourc

• emem-shared-identity

  Makes two agents refer to the same object. Finds an existing canonical identity for a thing from a fuzzy phrasing: a field, a corridor, an asset, a place treated as an object. Attests that two phrasings denote one object, or mints a new identity when none exists. Use when several agents or documents

• emem-sign-and-attest

  Writes to emem with the agent's own Ed25519 key. It writes a signed note in the agent's namespace, which other agents can verify the agent wrote. Or it registers a derivation over signed facts, which the responder recomputes. Use it to record something durably and verifiably. Also use it to give a f

• emem-tokenise-files

  Turns a file into signed, resolvable tokens with emem. Cuts the file into units (markdown sections, or byte ranges). Commits the BLAKE3 of every unit under one Merkle root, in a pointer.v1 index note that the agent signs with its own key. Hands out emem:tree tokens that name the whole file or one un

• emem-transparency-log

  Audits emem's append-only transparency log, an RFC 6962 tree built with BLAKE3. Gets a signed tree head, and a proof that a log entry or a memory note is committed under it. Gets a proof that a later head extends an earlier one without rewriting history, and reads which independent witnesses counter

• emem-urban

  Answers urban-analysis questions with signed emem facts and says what each number measures. It covers Overture buildings, places, road length and road bearing, and WorldPop population density. It also covers the Sentinel-2 built-up index (NDBI), the ESA WorldCover built-up class, JRC surface-water r

• emem-verify-before-publish

  Checks a draft before you send it. Finds every emem citation in the text and confirms that each one resolves and verifies. Checks the number next to each citation against the signed value. It can also flag measurable claims that have no citation. Returns allow or deny with a machine-readable reason.

• emem-verify-receipt

  Verifies the Ed25519 signature of an emem receipt. It checks the receipt through the emem_verify_receipt tool. It also states the canonical BLAKE3 preimage (v1 or v2) and the published key of the responder, so that anyone can check the signature again offline with tools that they already trust. Use

MCP servers (1)

• emem

  connects to: https://emem.dev/mcp

Similar plugins