The compiler reads the vendor schema, the documents, the event catalogue and the sandbox behaviour. It writes the contracts, generates the conformance tests, certifies the evidence, and signs one skill.

Each vendor draws the line between an acknowledgement and an outcome somewhere else. You never write that logic.

Compile a vendor
$ provely skill generate stripe
$ provely skill generate --openapi ./vendor.yaml

Which stages does the compiler run?

  1. Ingest Read the OpenAPI or GraphQL schema, the reference documents, the event catalogue and the SDK types.
  2. Classify Mark every operation that changes the world. Infer the lifecycle of each resource.
  3. Plan the evidence Find the readback, the event and the independent system that prove the outcome.
  4. Synthesise Write the completion contracts. Add the negative postconditions that catch duplicates.
  5. Test Generate the conformance cases. Run them against the vendor sandbox.
  6. Certify and sign Certify the evidence. Sign the skill and publish it.

How is a skill certified?

Every skill gets one level: Provisional, Generated draft, Verified or Official. An undocumented semantic keeps the level low and is marked REQUIRES_REVIEW. One known false VERIFIED rejects the skill.

A skill states its certification level and its last conformance run on its own page. Read the integrations.