PROMPT — LIST CURRENT WORKFLOWS INTO WF-DRAFT

Goal

List the short operational workflows discovered in the recent C1 / DOT manage work. Group related procedures into a small number of files so the workflow list stays readable.

Target folder

Write only under:

knowledge/dev/laws-new/workflow-manage/workflow-list/WF-draft/

Do not modify runtime, registries, DOT tools, schemas, or production data.

Read first

Read these current references if available:

knowledge/dev/laws-new/newlaws/dot-manage/dot-manage-c1-lego-dryrun-lessons-addendum-2026-06-23.md
knowledge/dev/laws-new/reports/c1-lego-dryrun-plan-hardening-no-prod-write/
knowledge/dev/laws-new/reports/c1-grant-issuer-dot-gap-closure/
knowledge/dev/laws-new/reports/c1-authorize-build-step-handler-minimal-lego-patch/
knowledge/dev/laws-new/reports/c1-w7-handler-prerequisite-operator-apply/

Required grouping

Create or update these draft files only if the workflow content exists:

01-dot-lifecycle-and-anti-orphan-workflows-draft.md
02-registry-catalog-ledger-workflows-draft.md
03-c1-dryrun-w7-authorization-workflows-draft.md
04-evidence-ssot-readback-workflows-draft.md
05-operator-capability-apply-workflows-draft.md

Workflow style

Each workflow must be short and actionable:

Workflow name:
When to use:
Inputs:
Steps:
Evidence/readback:
Stop/HOLD condition:
Forbidden:
Rollback/retire:
Status: DRAFT | HOLD | READY_FOR_REVIEW

Must include if evidenced

Include workflows such as:

How to create a new DOT without orphaning it.
How to run reuse-first before creating a DOT.
How to perform DOT birth / khai sinh.
How to perform DOT governance/admission.
How to register DOT through governed registrar.
How to update catalog / CAT-006 / dot_tools.
How to update DOT manage ledger/handbook.
How to prove SSOT: VPS code vs AgentData KB vs local staging.
How to handle unsafe dot-dot-register 287/15 false-new defect.
How to avoid manual Directus POST / manual SQL bypass.
How to design/register dot-c1-grant-issue as proposer, not writer.
How to apply C1 W7 handler prerequisite through DOT-approved path.
How to perform operator exec-channel preflight.
How to re-run W7 and W1→W9 prewrite gate.
How to decide when Codex may be used.

Hard constraints

• Do not invent workflows not supported by evidence.
• Do not mark unresolved workflows as final.
• Do not create one file per tiny workflow.
• Do not promote draft files into final handbook.
• Do not normalize manual SQL/Directus bypass as valid.
• Every new DOT workflow must include: reuse-first, birth, governance, registration, catalog, ledger, rollback/retire, orphan check.

Final report

Report:

files created/updated;
workflow groups covered;
items left HOLD;
items needing owner/operator confirmation;
ready for promotion: YES/NO.