Keep the page primary
The source should not lose authority when interaction arrives. Content, actions, and continuation should still belong to the page.
Current Release · v0.5.0
One page for humans and agents.
MDAN (Markdown Action Notation) is a shared notation for interactive pages that stay readable and actionable for both humans and agents — from the same source, across any interface.
Same page. Same actions. Same experience.
Notation
Readable first. Actionable when needed.
The notation stays close to the page instead of turning it into a separate agent-facing layer.
Notation sample
BLOCK demo {
INPUT text -> nickname
INPUT text required -> message
GET "/list" -> refresh label:"Refresh"
POST "/post" (nickname, message) -> submit label:"Submit"
}
Carry one surface across interfaces
Humans, agents, browsers, and other clients should not need unrelated representations just to continue the same work.
Stop translating the system away
MDAN reduces the gap between explanation and execution, so the page can stay readable even after it becomes active.
Scenarios
Where it fits.
Use MDAN where one readable page needs to stay active across interfaces instead of splitting into separate systems.
Interactive documentation where explanation and action belong on the same page.
Operational pages that need to stay legible while still being executable.
Internal tools where browser surfaces and machine clients should not drift apart.
Agent-usable workflows that still need a readable primary source for people.
Start here
Core reading.
Start with the core reads that define the notation and explain how it differs from backend API-first designs.