the-custodian/docs/netkingdom-target-implementation.md

NetKingdom target implementation record

Coordinator: CUST-WP-0080. Target: security architecture. Started 16 October 2026 under the founder's explicit implementation and GPT-6.1-Sol medium subagent request. The full architecture remains the goal.

Work ownership and current status

Gate	Existing implementation owner	Current evidence state	Next deliverable
TSA-01	Secrets Engine / Access Engine; SECRETS-WP-0014	Source implementation in progress; independent signer admission and native rollout pending	Producer-compatible verifier on actual consumer paths; trust/rotation/negative fixtures
TSA-02–03	Platform / Secrets / Approval; RPF-WP-0035-T12, SECRETS-WP-0013, APPROVAL-WP-0002	Source compiler/journal exists; mediated native execution incomplete	Durable cleanup independent of business outcome; reviewed exact execution integration
TSA-04	NetKingdom / Mason / Warden / KeyCape; NK-WP-0048	Type versions acknowledged; native first-reference acceptance incomplete	Completion verification against real owner receipts and missing adapter integration
TSA-05	KeyCape / User / NetKingdom / Playwright; KEY-WP-0040, NK-WP-0050, CUST-WP-0080-T05	Native human and agent journey gates open	Actual recovery and browser consumer acceptance
TSA-06	Glas / Sand-boxer / rein / Platform / Forge; CUST-WP-0073, GLAS-WP-0012	Actual assignment isolation and complete runner authority proof open	Admitted runtime and effective-authority denial tests
TSA-07–08	Secrets / NetKingdom / Platform; NK-WP-0049 and existing lifecycle plans	Inventory, lifecycle and independent recovery incomplete	Metadata denominator, elimination candidates, scoped recovery and lifecycle receipts
TSA-09	Audit / emitting owners; Approval T04 and current Audit work	Delivered custody; current source admission/reconciliation incomplete	Source/effect/outbox/receiver readback for first protected operation
TSA-10	Forge / Repo Manager; FORGE-WP-0006, RMGR-WP-0021	Broad receive coverage delivered; other paths and response incomplete	Coverage/reliability gaps and private response acceptance
TSA-11	Reuse / provider owners	70/70 discovery verified 15 October; stale descriptive fields remain	Correct source metadata and repeat drift/hosted checks
TSA-12	Activity / Coordination / Custodian; CUST-WP-0079	Schedule accepted but unassisted activation not proven; cadence source adoption underway	Actual activation and first independent observation
TSA-13–14	NetKingdom / provider owners	Accepted reusable integration and second installation pending	Shared adapter conformance and minimal locked profiles
TSA-15	Resource / telemetry / consumer owners; CUST-WP-0071 where applicable	Optimization baseline incomplete	Comparable latency, effort, resource and scanner measurements
TSA-16	Custodian / governance and owner records	Governing records exist; target-wide evidence reconciliation open	Requirement-by-requirement closure audit under CUST-WP-0080-T04

Each entry summarizes an owner obligation; it does not copy or replace that owner's task list. The original requirement ledger and owner receipts retain their original scope and outcomes.

Delegated implementation wave

The founder requested model gpt-6.1-sol, reasoning effort medium. The coordinator dispatched these concrete child assignments using that configuration:

Handle	Owner role	Source scope	Artifact directory
/root/decision_auth	secrets-engine	Signed decision enforcement, existing SECRETS-WP-0014	docs/changes/netkingdom-target-2026-10-16/decision-auth/
/root/protected_execution	railiance-platform	Task execution journal/cleanup, RPF-WP-0035-T12	docs/changes/netkingdom-target-2026-10-16/protected-execution/
/root/browser_case	net-kingdom	First browser case verification/integration, NK-WP-0048-T06	docs/changes/netkingdom-target-2026-10-16/browser-case/

Each child reads the assigned owner's instructions and intent. Prepared changes use isolated temporary checkouts based on current owner source, with relevant pre-existing tracked changes retained. Exact patches, source hashes and tests support coordinator review before integration. A child reviews only its own owner role; independent cross-owner reviews require separate assignments.

This wave authorizes source implementation and preparation under the user goal. It grants no runtime credential scope or automatic native acceptance. Required owner checkout filesystem approval is distinct from authority to change live trust or credentials. No agent inherits another assignment's autopilot grant.

Dependency and residual handling

The current implementation demand selects necessary target dependencies for owner review and scoped promotion. APPROVAL-WP-0002's exact issuer/provenance, audit and served-PEP obligations are required; its residual label must be reconciled by its owner before implementation dispatch. This does not activate every residual security plan or the deferred exposure rotation.

Cross-owner waits attach to the existing project driver where one exists, or a derived cross_owner_wait case benefiting CUST-WP-0080. The dispatched child handles establish current execution, not a separate fleet wake service. If a child is terminal, record its deliverables and dispatch the next reachable owner task; never report a stale handle as running.

Evidence and completion rules

For each change record the original owner revision, pre-existing dirty-state digest, exact patch, focused tests, independent review, integrated revision, publication and native acceptance separately. Bind each native receipt to target, identity, scope, source/image/config revision, expected result, negative cases, cleanup and rollback. Preserve failures and unverified outcomes.

The coordinator reviews evidence against every TSA gate and the named owner requirements. It may record partial source delivery without closing a native gate. Work continues until the target's complete exit condition holds. The first wave is implementation progress, not the completion boundary.