makermap
A command layer for building software with agents. Products, plans, decisions and time in one operational picture - and every capability is also an MCP tool, so an agent works the same surface you do while you stay the one who decides.
What is different here
- Every capability is a toolNot a subset chosen for an integration. The screens and the tools call the same services, so a capability cannot exist on one side and be missing on the other.
- No refusal is a bare noEvery refusal carries a code to branch on, a message a person can read, and a hint naming the next call that would succeed.
- AI proposes, a person decidesAgents frame decisions and post advisories with their confidence and evidence. Exactly one act ends a decision, and no token grants it to an agent.
- Nothing is confiscatedArchiving keeps everything. A plan limit refuses the next create and takes nothing away. A lapsed subscription falls back to free with every row intact.
- No number without an explanationHealth, forecasts, runway, entitlement usage - all computed on read and all able to say what produced them. A number you can edit is a number that will be edited to look good.
About this guide
26 written pages, plus three reference sections that are generated from the server's own metadata - all 288 tools with the scopes and arguments they actually declare, the scope registry, and every refusal code the product can produce. Those three cannot drift: a build where they disagree with the source does not pass.
The REST API documents itself separately, as live OpenAPI served by the API host at /docs - a document generated by the running server, so it cannot be behind the code at all.