flow-governance-review

name	flow-governance-review
description	Run the CLI-backed flow governance commands for QA, remediation, deterministic process-flow repair, and publish preparation. Use `node scripts/run-flow-governance-review.mjs COMMAND ...` when you need the supported `tiangong-lca qa flow` and `tiangong-lca flow ...` workflows from a skill wrapper.

Flow Governance QA

Keep local JSON or JSONL payloads as the system of record. This skill is a thin wrapper around the supported CLI governance commands.

Do not use this skill for:

• arbitrary remote CRUD outside the explicit CLI commit commands
• hidden OpenClaw orchestration
• private Python remediation helpers
• remote scope export

Runtime Model

• The canonical entrypoint is node scripts/run-flow-governance-review.mjs <command> ....
• Write outputs to an explicit directory such as /abs/path/artifacts/<case_slug>/....
• Supported commands are all CLI-backed:
  • identity-preflight -> tiangong-lca flow identity-preflight
  • build-plan -> tiangong-lca flow build-plan validate|materialize
  • qa-flows -> tiangong-lca qa flow
  • flow-get -> tiangong-lca flow get
  • flow-list -> tiangong-lca flow list
  • materialize-db-flows -> tiangong-lca flow fetch-rows
  • materialize-approved-decisions -> tiangong-lca flow materialize-decisions
  • remediate-flows -> tiangong-lca flow remediate
  • publish-version -> tiangong-lca flow publish-version
  • publish-reviewed-data -> tiangong-lca flow publish-reviewed-data
  • build-flow-alias-map -> tiangong-lca flow build-alias-map
  • scan-process-flow-refs -> tiangong-lca flow scan-process-flow-refs
  • plan-process-flow-repairs -> tiangong-lca flow plan-process-flow-repairs
  • apply-process-flow-repairs -> tiangong-lca flow apply-process-flow-repairs
  • regen-product -> tiangong-lca flow regen-product
  • validate-processes -> tiangong-lca flow validate-processes
• publish-reviewed-data is fully CLI-owned for both local preparation and commit-time process publish.
• There is no Python fallback path and no shell compatibility shim.

Authentication Gate

Before any remote read or commit, run tiangong-lca auth status --json. If it returns login-required, stop and ask the human user to run tiangong-lca auth login in a trusted terminal; never ask an AI user for a password, authorization code, token, or legacy API key. Before commit commands, require tiangong-lca auth doctor-auth --json to pass. Headless execution may use only an orchestrator-injected short-lived access token, never argv or artifacts. Use a distinct private TIANGONG_LCA_SESSION_FILE for each account/project/client and preserve the expected account in the task evidence.

Commands

• flow-get
• flow-list
• identity-preflight
• build-plan
• materialize-db-flows
• materialize-approved-decisions
• remediate-flows
• publish-version
• publish-reviewed-data
• build-flow-alias-map
• scan-process-flow-refs
• plan-process-flow-repairs
• apply-process-flow-repairs
• regen-product
• validate-processes
• qa-flows

Run them through:

node scripts/run-flow-governance-review.mjs <command> ...

For CLI-backed deterministic governance slices, prefer:

node scripts/run-flow-governance-review.mjs identity-preflight \
  --input /abs/path/flow-preflight.json \
  --out-dir /abs/path/identity

node scripts/run-flow-governance-review.mjs build-plan validate \
  --input /abs/path/flow-build-plan.json \
  --out-dir /abs/path/build-plan

node scripts/run-flow-governance-review.mjs build-plan materialize \
  --input /abs/path/flow-build-plan.json \
  --out-dir /abs/path/build-plan

node scripts/run-flow-governance-review.mjs materialize-db-flows \
  --refs-file /abs/path/flow-refs.json \
  --out-dir /abs/path/materialized \
  --fail-on-missing

node scripts/run-flow-governance-review.mjs materialize-approved-decisions \
  --decision-file /abs/path/approved-decisions.json \
  --flow-rows-file /abs/path/materialized/qa-input-rows.jsonl \
  --out-dir /abs/path/decision-artifacts

node scripts/run-flow-governance-review.mjs qa-flows \
  --rows-file /abs/path/flows.jsonl \
  --out-dir /abs/path/qa

node scripts/run-flow-governance-review.mjs remediate-flows \
  --input-file /abs/path/invalid-flows.jsonl \
  --out-dir /abs/path/remediation

node scripts/run-flow-governance-review.mjs publish-version \
  --input-file /abs/path/ready-flows.jsonl \
  --out-dir /abs/path/publish \
  --dry-run

node scripts/run-flow-governance-review.mjs publish-reviewed-data \
  --flow-rows-file /abs/path/reviewed-flows.jsonl \
  --original-flow-rows-file /abs/path/original-flows.jsonl \
  --out-dir /abs/path/publish-reviewed

node scripts/run-flow-governance-review.mjs build-flow-alias-map \
  --old-flow-file /abs/path/old-flows.jsonl \
  --new-flow-file /abs/path/new-flows.jsonl \
  --out-dir /abs/path/alias-map

node scripts/run-flow-governance-review.mjs scan-process-flow-refs \
  --processes-file /abs/path/processes.jsonl \
  --scope-flow-file /abs/path/flows.jsonl \
  --out-dir /abs/path/scan

node scripts/run-flow-governance-review.mjs plan-process-flow-repairs \
  --processes-file /abs/path/processes.jsonl \
  --scope-flow-file /abs/path/flows.jsonl \
  --scan-findings /abs/path/scan/scan-findings.json \
  --out-dir /abs/path/repair-plan

node scripts/run-flow-governance-review.mjs apply-process-flow-repairs \
  --processes-file /abs/path/processes.jsonl \
  --scope-flow-file /abs/path/flows.jsonl \
  --scan-findings /abs/path/scan/scan-findings.json \
  --out-dir /abs/path/repair-apply

node scripts/run-flow-governance-review.mjs regen-product \
  --processes-file /abs/path/processes.jsonl \
  --scope-flow-file /abs/path/flows.jsonl \
  --out-dir /abs/path/regen \
  --apply

node scripts/run-flow-governance-review.mjs validate-processes \
  --original-processes-file /abs/path/before.jsonl \
  --patched-processes-file /abs/path/after.jsonl \
  --scope-flow-file /abs/path/flows.jsonl \
  --out-dir /abs/path/validate

Not Supported

The following legacy commands were intentionally removed with the Python runtime:

• openclaw-entry
• openclaw-full-run
• run-governance
• flow-dedup-candidates
• export-openclaw-*
• apply-openclaw-*
• validate-openclaw-*

If you need one of those workflows, add it first as a native tiangong-lca qa ... or tiangong-lca flow ... command instead of rebuilding it inside this skill.

Preferred Usage

Use the supported commands as composable slices:

1. identity-preflight before creating a new flow. Stop on block_duplicate or manual_review.
2. Author unit_of_analysis in the flow build plan before generation. For flow-only plans this may be a declared-unit dataset decision, but it must still record target kind, reference flow identity, reference unit, reference amount, flow property, and scaling evidence status. The skill makes the semantic decision; the CLI only checks that the artifact is present and complete.
3. build-plan validate and build-plan materialize before producing a canonical flowDataSet.
4. materialize-db-flows when the task must bind to real DB rows.
5. qa-flows.
6. materialize-approved-decisions after merge decisions are approved.
7. remediate-flows.
8. Keep flow names, synonyms, comments, and classification text source-language only for import/publish gates.
9. build-flow-alias-map when version cleanup produced old/new scopes.
10. scan-process-flow-refs.
11. plan-process-flow-repairs.
12. apply-process-flow-repairs.
13. validate-processes.
14. publish-version or publish-reviewed-data.

Standard Outputs

• identity-decision.json, identity-candidates.jsonl, and identity-candidate-sources.json from identity-preflight
• build-plan-gate-report.json and materialized-flow.json from build-plan
• flow-alias-map.json when alias building is applicable
• scan-findings.json and repair-summary.json when process snapshots are provided
• publish-report.json from publish-reviewed-data
• prepared-flow-rows.json and flow-version-map.json from publish-reviewed-data
• skipped-unchanged-flow-rows.json from publish-reviewed-data when --original-flow-rows-file is provided
• resolved-flow-rows.jsonl, qa-input-rows.jsonl, and fetch-summary.json from materialize-db-flows
• flow-dedup-canonical-map.json, flow-dedup-rewrite-plan.json, manual-semantic-merge-seed.current.json, and blocked-clusters.json from materialize-approved-decisions

Example Output Layout

Write generated machine outputs to an explicit directory outside the skill source tree. Typical bundles include:

• /abs/path/artifacts/<case_slug>/flow-processing/datasets/: shared flow pool, invalid-input scope, resolved flow pool, reusable process_pool.jsonl
• /abs/path/artifacts/<case_slug>/flow-processing/validation/: grouped validation failures that still matter for remediation planning
• /abs/path/artifacts/<case_slug>/flow-processing/naming/remaining-after-aggressive/: post-aggressive completeness summaries and zero-process residuals
• /abs/path/artifacts/<case_slug>/flow-processing/naming/zero-process-completion-pack/: reference review materials retained for follow-up
• /abs/path/artifacts/<case_slug>/flow-processing/remediation/: deterministic remediation and publish preparation artifacts
• /abs/path/artifacts/<case_slug>/flow-remediation-batch-smoketest/: historical smoke-test evidence for remediation-helper startup checks

Load References On Demand

• references/workflow.md: command matrix, outputs, removed surface, and recommended sequencing.
• references/env.md: canonical CLI env expectations for read, review, and publish commands.
• references/real-db-first-runbook.md: real-DB-first execution guardrails, refs-file shape, and blocked-case handling.
• references/decision-schema.md: approved decision file schema, merge examples, and downstream artifact meanings.