11 — Information-Piece Content Resume

Content work resumed in-macro using the new candidate universe as a Process-axis surface, joined to the Topic axis (v_information_piece_topic_process_map from the prior IP phase). No source IU edited. Companion docs produced (this file + the two below are the deliverable narrative; see also docs 12.1/12.2 in this dir if present).

1. Process candidate map for knowledge_graph / dot:kg

The KG topic cluster (16 topic IUs → one doc dieu39-knowledge-graph-law.md; bridge IU 10649925) converges with the DB process axis (18 dot:kg DOT pairs). The NEW host candidate layer is orthogonal to KG: it covers operational/infra processes (backup, guards, health, publish, approval-lifecycle) that the KG topic does not describe. Editorial finding: the host candidate layer fills a content gap — there is currently no Topic IU describing "platform operations processes" (backup/DR, health monitoring, permission guards). This is a new Topic seed: TOPIC-PLATFORM-OPERATIONS.

2. Workflow discovery operator narrative

A plain-language narrative for operators: "The scanner sweeps cron, systemd, dot/bin, scripts, docker and KB nightly (04:10). Anything it can't map to a known DOT lands in the orphan queue. This phase grouped those orphans into 17 candidate processes. Six are real new processes (backup, permission-guard, reconciliation, health-monitoring, content-publish, approval-lifecycle) waiting for an owner to bless them. The rest are either OS housekeeping, duplicate backup files, or DOT implementations we already know about." → seed doc for /process-discovery help panel.

3. Content backlog updated (process-candidate evidence)

New backlog items D11–D16: one explainer per new process candidate (Backup&DR, Permission Guard, Reconciliation, Health Monitoring, Content Publish, Approval Lifecycle), each citing its member entrypoints from v_ax_process_candidate_substrate. D17: "Registries-Pivot process map for UI users" (below).

4. RP process map explanation (for future UI users)

"AX-PROCESS now has two layers: official (canon processes — currently 0, owner-gated) and candidate (17 evidence-backed clusters the scanner found). A candidate badge means 'we found this running but no human has ratified it as an official process yet.' Owner-gated badge = waiting for a decision; not-a-process = OS/infra/noise we've explicitly set aside." → seed for the RP AX-PROCESS legend/tooltip.

Content advanced: 1 new Topic seed, 1 operator narrative, 6+1 backlog explainers, 1 RP legend — all from candidate evidence, zero source-IU edits.