Vigile
SearchContents

How it works

Four interfaces, one plan

An operation is defined once, in the engine, with its name, its description, its input and its rules. The interfaces are ways to reach it, and none of them has rules of its own.

Four ways into one service AI agents reach the service over MCP at /mcp. Programs call the HTTP API at /api, and so does the vigile command line. People open the web page, which reads through the API. All of them arrive at one engine, where every operation is defined once with its input, rules and refusals. The engine keeps the plan in one data folder, in SQLite. AI agents tools, over MCP Programs JSON, over HTTP You, and scripts the vigile command People a browser /mcp /api/<operation> / the page reads The engine: every operation, defined once its input, its rules, its refusals, and who may call it ONE SERVICE: ONE PROCESS, ONE PORT One data folder the plan, in one SQLite file
Agents speak MCP, programs speak HTTP, people type commands or look at the page. All of it arrives at the same operations of one engine.

One contract

Each operation says what it is called, what it takes, who may call it and what it does. The four ways in come from that one definition:

Way inForAn operation isRead more
MCP, at /mcpagentsa tool: set_task_status. An agent also gets the routine for a task, and a guideMCP for agents
HTTP API, at /apiprogramsan endpoint: POST /api/set-task-status. A stream says when the plan has changedThe HTTP API
Command lineyou, and scriptsa command: vigile set-task-status. Output for people, or JSONThe command line
The page, at /peopleread operations, plus update_task for the priority −/+ controlsThe web page

Input is checked in one place, the engine. So a wrong value is refused in the same words whichever way it came, and a refusal of an operation has one shape everywhere.

The command line is a client like any other: it calls the running service and never opens the data itself to change it.

A change by one shows for all

  1. An agent calls set_task_status over MCP.
  2. The engine checks the change, stores it, and the plan's revision goes up by one.
  3. Everyone listening on the stream of changes is told the new revision, and nothing else.
  4. A page with auto-refresh on reads the plan again and moves the card to its new column.

The event says only that something changed. What changed is read through the operations, by each listener as itself, so the stream can tell nobody anything they could not read anyway.

Reference