Which builders and AI coding tools can use the spec?

Any developer, development team or practitioner can build from it, and so can AI coding tools in general. The build package is written to be vendor-neutral: a structured JSON file with a published schema, the same content as readable Markdown, and an AGENTS.md instructions file for coding assistants. Tools that can connect to an MCP server can also read the specification item by item while they work.

Mochlion doesn't tie you to one AI vendor, and it doesn't certify any particular tool.

What does a human builder use?

The Build Specification as PDF, Word or Markdown, with every requirement numbered by trace ID, testable, and traced to the answer or decision behind it. Many teams read it like any other specification and plan their work from it.

What does an AI coding tool use?

The build package:

• build-package.json and its schema: everything in structured form, so a tool can read requirements, acceptance criteria, the data model, access rules, errors, security, and a build sequence without guessing at layout.
• BUILD_PACKAGE.md: the same content in one readable file, for tools that work best from text.
• tools/AGENTS.md: project instructions for any coding assistant: the boundaries, how to work, the build sequence, a checklist for each step, and the acceptance tests to automate.
• Optional set-up files for one widely used coding assistant, including a small safety guard you can read and change before turning it on.

None of the optional files is the source of truth. If they ever disagree with the package, the package wins.

Can a tool ask questions while it builds?

Yes, through the MCP server or the token API. The package tells the builder to ask instead of guessing. A tool can ask about a specific trace ID, the question goes to the experts the item came from, and the tool reads the answer back. See what agents can do.

Does it work with low-code platforms or a particular language?

The specification says what the software must do, not which language, framework or platform to use. Those choices are left to the builder on purpose, so it can be built with whatever your builder uses. How well a given tool follows it varies, as with any specification.

What if my builder doesn't use AI at all?

That's fine. The human-readable specification stands on its own, and the structured package is there if they want it later.

To see the files, look at the sample specification.