Record verified security source integrations and remaining contract seams

docs/netkingdom-target-implementation.md

@@ -49,10 +49,11 @@ support coordinator review before integration. A child reviews only its own
 owner role; independent cross-owner reviews require separate assignments.
 
 The table records assignment history, not perpetual liveness. All eight owners
-delivered initial source packages. Secrets and Access are preparing native
-package/trust/caller admission. Platform is extending exact effect readback and
-recovery evidence in disposable OpenBao. Approval delivered the focused source
-closure and a separate exact-confirmation repair.
+delivered initial source packages. Secrets and Access are implementing the trusted
+service task path and preparing native package/trust/caller admission. Platform
+delivered exact effect readback and process-loss cleanup recovery in disposable
+OpenBao; the trusted successor adds absolute execution budgets. Approval delivered the shared claim adapter and is reviewing
+its authenticated consumer integration.
 Exact revisions and publication caveats are in the
 [source wave receipt](changes/netkingdom-target-2026-10-16/source-wave-status.json);
 independent tests and retained failures are in the
@@ -94,8 +95,8 @@ Secrets handoff now binds the signed decision, approval, exact grant and caller;
 Platform reserves durably, journals consumption and independently confirms it
 before effects. Actual Access and Approval servers passed this path with explicit
 synthetic identity/key/policy admission. Denied confirmation leaves uncertainty
-and permits no native effect. Six successful native calls still do not establish
-the complete expected-state readback; that remains the next Platform proof.
+and permits no native effect. Six successful native calls alone do not establish
+complete expected-state readback; the following source slice adds that proof.
 Both Secrets and Approval now compare the existing canonical native digest,
 refusing Python's boolean/integer equality ambiguity. The original counterexample
 and intermediate test failures remain recorded.
@@ -105,6 +106,63 @@ 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.
 
+## Subsequent source integration, 16 October
+
+Platform `d870596` binds canonical before/after metadata snapshots through the
+existing descriptor commitments, checks each baseline before its target write,
+and verifies complete readback before recording success. Independent native
+fixture/mediator/readback suites passed 32 tests. This is sequential observation:
+there is no atomic native CAS or concurrent-writer exclusion. Partial application
+remains unknown, and cleanup confirmation stays separate. Its whole-stack
+positive proof is pinned to Access `ec21518e`; later Access source deliberately
+removes the generic task path used by that old synthetic fixture.
+
+Access `919ce25` fixes explicit caller-audience rendering and source revision
+pinning, records the existing workload identity, and adds an offline native
+receipt verifier using the installed Secrets verifier. Root review reproduced
+boolean/integer and integer/float source-record equality mistakes; R2 checks exact
+JSON types and hashes the same bounded bytes it verified. Nine receipt tests and
+two runtime-twin tests passed independently. Missing managed package declaration,
+signer custody and native image/trust admission remain explicit.
+
+Secrets `5a2099f` records the exact native CLI preparation, verified canonical
+release bundle, configuration and trust inputs. The initial serving denominator
+is 11 authorization sites across 10 handlers; native effect acceptance is zero.
+Root verified unchanged runtime AST except documentation. The empty-key template
+is intentionally unusable until independently admitted owner inputs exist.
+
+Approval `3485415` supplies a producer-owned Go fact adapter and authoritative
+claim vectors. Root passed its Go suite, two producer-vector tests and 14,114
+actual Python canonical-byte/digest comparisons. This is shared validation code,
+not another evaluator or credential transport. Access B1 R2 `4f6946b` connects the
+actual HTTP caller join, preserves the submitted context and withholds accidental
+ALLOW until the trusted source path exists. All three affected Go packages passed
+independently; a malformed nested-duplicate test was corrected and rerun. These
+two commits' publication/reconciliation state is recorded in the source receipt.
+
+The trusted Access v2 successor, refreshed strict Secrets handoff and signer-custody
+proposal remain separate review packages. Access's actual Approval API fixture and signed ALLOW/refusal evidence
+are source proofs; the complete new consumer-to-Platform path and native issuer,
+key, workload, grant, recovery and independent audit acceptance remain necessary.
+Recovery review rejected broad 404 absence and unauthenticated stored accessor
+claims. Revised Platform `b9eaa20` passed 53 independent tests and adds authenticated
+private accessor custody and separately admitted cleanup after executor loss,
+without restoring business or consumption authority. Lost issuance before accessor
+persistence remains unresolved. Actual custody/key isolation and recovery grants
+remain unadmitted.
+
+Whole-stack successor work exposed a temporal contradiction: the first v2 source
+allowed 15 seconds while native token lifetime requires at least 30 seconds plus
+cleanup reserve. Owner temporal revision now binds expiry to the exact operation
+deadline within declared hard limits and all original/fresh/caller authority;
+it is pending independent integration. Retained registry enrichment also needs
+exact approval-free digest correspondence. Empty-registry proof cannot close that
+gate. Immediate consumption also exposed a precision mismatch: Approval receipts
+use whole seconds while the new decision start has fractional precision. A
+positive proof that waits across that boundary does not establish immediate-path
+acceptance; the producer owners are resolving it without weakening verification.
+All sixteen target acceptance gates remain open.
+
 ## Dependency and residual handling
 
 The current implementation demand selects necessary target dependencies for