amadeus-validator

You can validate Amadeus lifecycle artifacts by running the amadeus-validator on the current workspace or a named intent directory. It inspects the aidlc structure, markdown references, and JSON registries to return pass, fail, or blocked.

An Amadeus workspace consistency check verifies the overall aidlc root structure, space directories, memory files, and knowledge indexes. It also confirms active intent pointers, state documents, and stage completion requirements against the runtime contract.

Yes, Bun is required along with the bundled validator entrypoint to inspect domain and context maps. The validator uses this environment to process Event Storming artifacts and v2 lifecycle state conventions.

You should run a lifecycle state audit after creating or updating intent artifacts. This catches missing files, broken references, or contract violations in domain maps and Event Storming sessions before the workspace is treated as valid.

Intent registry validation returns a blocked status when required stage-completion evidence, audit evidence, or state documents are missing. The validator detects these contract violations and incomplete files during the aidlc structure inspection.

Yes, you can check Event Storming artifacts and grilling trails against the runtime contract. The validator confirms these domain and lifecycle artifacts alongside context maps to ensure completed work satisfies v2 lifecycle state conventions.