disaster-control/workplans/DISCTL-WP-0004-netkingdom-identity-backup-lane.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	state_hub_workstream_id
DISCTL-WP-0004	workplan	Adopt the NetKingdom identity backup lane	infotech	disaster-control	active	claude	custodian	2026-10-23	2026-10-23	66133b9d-9728-5e63-8626-170cf4a2b315

Adopt the NetKingdom identity backup lane

Bring the NetKingdom identity backup lane on railiance01 under disaster-control governance, as requested by net-kingdom (State Hub message ef2bf2a9; founder decision e4c288d9, resolved 2026-10-23). This repo tracks and evidences the lane; implementation and restore tooling stay in net-kingdom, backup account and custody in railiance-platform.

Lane facts (non-secret):

Item	Value
Scope	LLDAP; privacyIDEA (database, token material, audit); KeyCape client registry archive
Owner	net-kingdom (profile, restore tooling); railiance-platform (backup account / custody)
Backup	Daily 03:45 UTC (+≤5 min jitter), age-encrypted, ONE off-host provider (Storage Share)
Monitoring	Hourly on-host health check; 25-hour freshness bound
RPO	24h
Activation evidence	net-kingdom NK-WP-0049-T14 (2026-10-16)
Accepted residual risk G1	Single off-host provider — accepted until 2027-01-31
Accepted residual risk G2	On-host-only freshness detection — accepted until 2027-01-31; linked to the outside-node watchdog owed by RAPP-TELEMETRY-WP-0001-T04
Restore proof	Quarterly isolated identity restore drill, net-kingdom NK-WP-0053, procedure net-kingdom/docs/identity-restore-drill.md; first due by 2027-01-31; evidence under net-kingdom/docs/evidence/<date>-identity-restore-drill/
Prior one-off proofs	NK-WP-0049-T16 (LLDAP), T31 (privacyIDEA token material), T20 (audit)

Register the lane in AssetRegister and DataRegister

id: DISCTL-WP-0004-T01
status: done
priority: high
state_hub_task_id: "99bb46df-a764-5f4a-b700-2616e40543af"

Add backup-netkingdom-identity to AssetRegister.yaml → backup_streams (T0) with the schedule, destination, freshness bound, accepted residual risks G1/G2 as gaps, and prior one-off proofs. Point the older related_streams → backup-adjacent-sso entry at the new stream. Add DataRegister.yaml data classes for the LLDAP directory, privacyIDEA database/token material/audit, and the KeyCape client registry archive.

Update BackupPolicy, RTO-RPO matrix and TestEvidence cadence

id: DISCTL-WP-0004-T02
status: done
priority: high
state_hub_task_id: "2e8d3951-d980-5a8d-b2f6-4aeb11bcf665"

Add the lane to the BackupPolicy.md 3-2-1 compliance table, the per-stream mechanisms table, the monitoring checks, and the open-gaps table (G1/G2 with their acceptance expiry). Add an RTO-RPO matrix row and list the quarterly identity drill under TestEvidence/README.md next targets.

Import the first quarterly identity restore drill evidence

id: DISCTL-WP-0004-T03
status: wait
priority: high
state_hub_task_id: "d213be64-9bcd-51be-9615-c085976a275f"

Waits on net-kingdom NK-WP-0053: when the first isolated identity restore drill runs (due by 2027-01-31), add TestEvidence/restore-drill-<date>-netkingdom-identity.md linking the canonical evidence under net-kingdom/docs/evidence/<date>-identity-restore-drill/, record measured RPO/RTO in RTO-RPO-Matrix.md, and set the register evidence.last_drill.

Review accepted residual risks G1/G2 at expiry

id: DISCTL-WP-0004-T04
status: wait
priority: medium
state_hub_task_id: "749dc02c-c377-5db5-bb33-5f9b45c50840"

By 2027-01-31, confirm whether a second off-host provider (G1) and the outside-node freshness watchdog from RAPP-TELEMETRY-WP-0001-T04 (G2) have landed. Close the gaps in the registers and BackupPolicy.md, or route a founder decision to re-accept or escalate them.