Generated from
cat-harness/processes/kg/kg-separation-authorise.bpmnbygen-processes-viz.ts— do not edit here. All processes · cat-harness processes
Authorise the extraction
Process_KgSeparationAuthorise · strict · 2 step(s)
Reports what would move, with sizes and what breaks, and asks the administrator to authorise the extraction; the gateway after the ask reads the answer. Called by kg-separation and sub-kg-lifecycle (bpmn-authoring: a question is a gateway, never a task).
How it connects
- Called by: A knowledge graph leaves for its own repositories, A sub-KG is staged in place, then leaves for its own repository
- Calls: Ask the person
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
Steps
Every one of the 2 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Report what moves — sizes, what breaksTask_Propose | Authoring agent | shared step GT_ReportWhatMovesdeletion-requires-confirmation | The agent reports and waits: what would move, how large, what in the parent breaks, and the rollback. deletion-requires-confirmation is not a courtesy to waive: an agent never removes or relocates a durable artefact on its own initiative. |
Ask to authorise the extractionTask_Authorise | Administrator | calls Ask the persondeletion-requires-confirmation | A repository cut changes the substrate every other process binds to; that is a person’s decision. Declining leaves the graph declared, detangled, isolated and split in place. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Authorised?GW_Authorised | Reads the administrator’s answer to the ask before it. | authorised → Authorised declined → Declined |