Generated from
cat-harness/processes/kg/kg-separation-move.bpmnbygen-processes-viz.ts— do not edit here. All processes · cat-harness processes
Move the graph into its repositories
Process_KgSeparationMove · strict · 8 step(s)
Creates the repositories, drains the open PRs until the source settles, seeds them, re-points the declaration and verifies a fresh clone, then has the parent consume the result additively, makes the first release and checks every identifier dereferences. Nothing is seeded on an unknown readiness, and a fresh clone that could not run is not a pass. Called by kg-separation and sub-kg-lifecycle (bpmn-authoring: split by phase).
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: none
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
Steps
Every one of the 8 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Create the repositoriesTask_Create | Administrator | kg-separation | The owner creates the content and tools repositories and their Pages. Nothing is committed to them before this. |
Drain: land, close or re-target the open PRsTask_Drain | Authoring agent | shared step GT_Drainkg-separation | Work the PRs seed:ready named until the source settles: land or close the heavy movers and the next layer’s PRs, bring the layer’s open PRs to five or fewer, and finish any move in flight. Fix a red rehearsal or a discovery miss where it is. Nothing is seeded from here; it goes back to the gateway, which re-asks. |
Seed both repositoriesTask_Seed | Authoring agent | kg-separation | Seed main, then bring the content and the tools in as reviewed pull requests with their history, so neither repository’s first commit is unreviewable. The seed includes every publisher the declaration promises (sub-kg-lifecycle stage 10): a qa directory with storage needs .github/workflows/publish-qa.yml, the caller of the tools layer’s layer-qa-publish.yml, and test/results/ ignored. Without it the declared store is never written, and once the layer stops committing its results no reader finds them. |
Re-point: livesAt, seam, mount or subscriptionTask_Repoint | Platform authoring agent | sub-kg-lifecycleupstream-version-adoption | In the new repository livesAt goes (absent means it sits at the root of repository) and platform.ts points at where the platform now is. The host consumes it as a remote mount (a source.remote instance in its root index.config.json) if it imports its code, or a subscription if it only reads its content, pinned to a commit while staging. Additive: the host keeps its copy. |
Verify on a fresh cloneTask_FreshClone | Build pipeline | sub-kg-lifecycle | bun run cat sub-kg:verify-clone --repo <owner>/<name> --ref <branch> (Tool sub-kg-verify-clone): clone into an empty scratch directory with submodules and any sibling it needs, install, and run its own gates. Green, red or unknown, and unknown is never green. Nothing in a seed runs standalone until the seam is re-pointed, so a missing module shows here. |
Parent consumes, additivelyTask_Consume | Platform authoring agent | upstream-version-adoption | The parent pins the pair (a commit while staging, a version once released) — a code dependency as a source.remote instance in its root index.config.json (remote-mount skill), never a submodule — repoints its imports, and keeps its own copy until it is green with the dependency declared. Where cat-harness.sdlc is switched on, this step is the opt-in process upstream-version-adoption (Process_UpstreamAdoption, sdlc/processes/upstream-version-adoption.bpmn); it is not called from here, because a layer without that sub-graph does not have it (owner card Q-OPTIN-CALLS A, 2026-11-12). |
First releaseTask_Release | Publication manager | — | Tag each repository, publish /v<major>/. From here the two are versioned independently; a tools release lists the content majors it supports. |
Every identifier dereferencesTask_Verify | Build pipeline | — | After the release is live, every published identifier resolves to the file it names. Where cat-harness.sdlc is switched on, this step is the opt-in process publish-verification (Process_PublishVerification, sdlc/processes/publish-verification.bpmn); it is not called from here, because a layer without that sub-graph does not have it (owner card Q-OPTIN-CALLS A, 2026-11-12). |
Decisions
Every one of the 2 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Ready to seed?GW_SeedReady | Asked AT SEED TIME, because the tree has moved since 8 · Rehearse. A seed is a snapshot with no history, so every open PR over the layer when it is taken is orphaned into the monorepo. Computed by decisions/seed-readiness-gate.dmn (hit policy FIRST) from seed:ready --layer <name>: an open heavy-mover PR over the layer or the next one, any open PR on the next layer, more than five over the layer, any that moves a file in it, a red sibling-layout rehearsal, or a direct dependent that discovery cannot find among sibling clones answers not yet. A criterion that could not be decided answers unknown and stops; it never hides a finding already certain, which is why the not yet rows come first. The rehearsal runs only on request (--rehearse), so without it the answer is never settled. | not yet → Drain: land, close or re-target the open PRs unknown → UNKNOWN: do not seed settled → Seed both repositories |
Green from a fresh clone?GW_Fresh | Green goes to the owner. Red is fixed in the new repository, not in the staged copy, and goes back to the re-point. A clone that could not run is not a pass: stop. | red → Re-point: livesAt, seam, mount or subscription could not run → UNKNOWN: stop. Not clean green → Parent consumes, additively |