jmagly Validate a Flow graph
Use this skill when an operator needs to author or validate flow.aiwg.io/v1alpha1 FlowGraph.
Process
- Confirm the manifest uses apiVersion: flow.aiwg.io/v1alpha1 and kind: FlowGraph.
- Run aiwg composition validate MANIFEST --format json.
- When an AIWG index export is available, add --catalog INDEX.json so stable candidate IDs are proven against that captured catalog.
- Repair every error diagnostic. Do not weaken permissions, ceilings, approval boundaries, retry modes, or cycle guards merely to pass validation.
- Pass the returned normalized envelope to an adapter or runtime. Do not add provider-specific fields to the source graph.
Contract rules
- Every non-gate node resolves through the authorized candidate set.
- Every cycle has a CEL guard and finite iteration limit.
- Node permissions are a subset of both graph and declared-capability scopes.
- Approval-required side effects are never automatically retried.
- Trace policy covers declared execution metadata and bindings, never private chain-of-thought.
See schemas/flow-graph.schema.json, README.md, and docs/schema-evolution.md in the addon for the complete contract.