Docs preview
The product contract will be readable before the product asks for trust.
Mintchemy documentation will explain not only how to click through the product, but how AI help, the Critique, access, and agent tools behave.
Documentation map
A structured field guide for PMs, administrators, collaborators, and agent builders.
Start here
BuiltDocuments, Steps, and Templates
How a Document moves through ordered Steps, and how a Template sets the Steps it starts with.
AI boundary
BuiltAI help and Proposals
Why anything an AI writes stays apart from the Document until a person accepts or rejects it.
Critique
BuiltCritique and Findings
Who reviews a Document, how each Finding is graded and tied to the text it is about, and how it is resolved or dismissed with a reason.
Import
BuiltMarkdown import
Import Markdown files. Mintchemy maps each heading to a Step, and you accept, reject or re-point every mapping before anything is written.
Collaboration
BuiltGrants and Access levels
How access stays explicit per Folder and Document, and carries down a Folder to everything inside it.
Agents
In developmentMCP access
A local, read-only MCP server that reads only the Documents you can read. Proposal creation and a hosted connection come next.
Next
PlannedScorecard, Stages, and connected context
Dimensions that cite their Findings, Stages a person sets, and links from a Document to the evidence and Decisions behind it. A return from Test to Develop is recorded as a second occurrence.
How the Critique grades a Finding
- Blocker
- The spec cannot be built as written. It must be resolved or dismissed with a reason before the Document can be marked ready.
- Major
- It can be built, but a specific bad outcome is likely.
- Minor
- A real gap with a bounded cost.
- Nit
- Clarity only. Nothing that ships depends on it.
- Dismissing a Finding
- Records why: not true, out of scope, already decided, accepted risk, or real, but not a blocker.
Documentation promises
- Status is explicit
- Each guide carries one tag, Built, In development, or Planned, and never blends them.
- Rules are inspectable
- Access, AI authority, and the Critique are written as contracts.
- Examples stay realistic
- Guides use concrete product work rather than generic placeholder prose.