Published contract · human readable · integrity checked

Read each blueprint before your agent follows it.

These are the exact setup YAMLs served to coding agents from aiwg.io. Choose a flow, inspect every instruction, and verify that the displayed bytes match signed release and attestation evidence. Rendering alone is never proof; unsigned and policy-exempt resources are not shown as verified.

What it controls

A guarded flow, not a shell script.

The selected manifest tells an agent how to reason about installation. It does not execute by itself. Your agent must inspect the environment, explain its plan, obtain approval for mutations, preserve existing work, and verify the result.

  1. 01Inspect firstEnvironment and project state
  2. 02ExplainThe smallest safe remediation
  3. 03AskApproval before mutation
  4. 04PreserveExisting work and development mode
  5. 05VerifyStatus, doctor, and discovery

Live source

setup.aiwg.yaml

Download
application/yaml
  1. Loading the published manifest…
Rendered
Displayed or parsed only; no trust claim.
Unsigned
Complete usable signature evidence is absent.
Policy-exempt
A signed exception may permit inspection; it is not verified.
Verified
Signed manifest, exact bytes, publisher, and freshness passed locally.

Use the published flow

Give the URL to your agent.

The generated prompt points to the selected stable aiwg.io artifact. The release pipeline verifies its digest before publication, while this viewer lets people inspect the same bytes in a readable form.

Install or repair AIWG for this project by following
https://aiwg.io/setup.aiwg.yaml
Explain the plan before changing anything, preserve my existing work, and ask
me only for choices you cannot safely determine.