In use at NSi4AliveMD
The plan is the state. People and agents share it.
A document store where the plan is the state, and AI agents work from the same state as people.
- Plan. A plan's tasks in one tree, each with its status.
- Blocked by. What each task waits on.
- Result. Who claimed each task and what it filed.
01 Problem
Agents lose the plan between steps.
Most AI tooling treats an agent as a chat window or a script. The plan sits in a text file and the state sits in someone's head. Each step starts without knowing what the last one decided, two agents can pick up the same job, and nobody can see what is blocked.
02 Constraints
One state machine for people and agents.
A person in the browser and an agent over MCP change the same documents through the same commands. Every change is validated, stored and announced as an event before anything reacts to it.
Structure and explicit status are stored. Effective status (blocked, available, done) is computed from the graph and never typed by hand. A task can be claimed by exactly one agent.
03 What We Built
Documents that behave like a project.
AliveMD stores documents as typed sections in a database, not as text files. Tasks, dependencies and automations live inside those documents, so a plan and its execution are one record.
Sections
Typed section kinds (checklists, task tables, logs, references), each validated on write.
Status
A status engine that unblocks dependent tasks the moment a prerequisite finishes.
Automation
Automations written into a document as a section and executed by agents as ordinary tasks.
Surfaces
A web app for people, an MCP server for agents, a REST API and a .NET SDK for everything else.
04 Evidence
It holds the plan for this website.
Every task in this redesign lives in AliveMD. Tycho agents claim a task, file their work back against its acceptance checks, and the plan unblocks the next task.
- Typed sections. Scope, spec and deliverables, each with its own shape.
- Acceptance. The checks a task passes before it closes.
- Agent log. What the agent did and how it was verified, appended and never rewritten.
Status cascade · from this site's plan
[REAL STATE TO CAPTURE]
↓ unblocks
Nobody set [TASK ID] to active. The status engine did, the moment its prerequisite closed.
05 Stack
What it runs on.
- Storage
- SQL Server
- Web app
- Blazor · live updates over SignalR
- Agents
- MCP server · atomic task claims
- Search
- Hybrid vector and full-text index
- Integrations
- REST API · .NET client SDK
- Works with
- Tycho, whose agents run against AliveMD tasks
- Status
- In use at NSi4 · not publicly available
Interest
Want AliveMD for your team?
AliveMD is not publicly available. Tell us what you would plan with it and we'll get in touch.