user-engine/docs/evidence/2026-10-11-one-app-catalogue-human-packet/netkingdom-owner-agreement.md

NetKingdom owner review — bounded one-app catalogue maintenance exception

reviewer: net-kingdom-owner (agent net-kingdom, codex)
decision: approved
reviewed_at: "2026-10-11"
work_item: NK-WP-ADHOC-2026-10-11-T02
proposal: USER-CATALOGUE-INFDEC-20261011-R1
revision: executor-preparation-2-owner-findings
manifest_sha256: 0ff545d26a0fd72f06040fe377de3efdcc3bd62cdcb6f653247c8ba72f3f34a7
executor_sha256: b0dbbb9786e927055030acf849a72e9a44e9d3d55c84efdf245e419d381684f3
transport_sha256: 3e594e0e8561100ae1eeb34d7208cd5b5e387ae56c29689f155aed94219770f3
records_sha256: 23577cc4f3ea6c0ca43eb21ca0e3280eb53fb64e29b030dcd31251593f0f3f2f
comment: >-
  NetKingdom INTENT declares Taxonomy/security canon and orchestration with
  explicit externally owned identity, PDP and user-domain facts. This exact
  alternative is one labelled supervised maintenance exception for the two
  fixed User Engine metadata records, not a normative permission, new login,
  grant or case type. Technical agreement under NK-WP-ADHOC-2026-10-11-T02
  preserves real ordinary denial, independent exact founder disposition,
  recorded exception scope, bounded recovery and distinct owner roles.
  It provides no founder approval, native runtime go or catalogue completion.

Canonical facts and owner separation

The nine applied files all match the exact refinement manifest above. Application informed-decision / display Informed Decision / owner informed-decision and binding informed-decision-approver -> protected system informed-decision match User Engine's actual codecs and canonical-records.json. Access Engine's readback registry independently binds issuer https://kc.coulomb.social and that client; KeyCape source/owner registration receipt independently names the exact callback https://decisions.coulomb.social/auth/callback. Existing retained keycape-client- presence and native-preflight receipts support current preparation; no new live issuer or database read was performed in this review. A fresh frozen target/pod/ image and unchanged facts still must be rechecked before separately approved use.

The proposed write does not create a user, membership, group, default role, entitlement, grant or authorization rule. Application and binding are catalogue facts, not allow-list entries or permission. No entry URL is smuggled into the DTO: its model has no URL field, and observed Ingress URL remains context only. This source agreement does not establish a fleet-complete catalogue or supply any application owner's still-required acknowledgement in another owner's voice. User Engine owns record lifecycle/persistence; Access owns the protected system and decisions; KeyCape owns authentication/client registration; InformedDecision owns application semantics. NetKingdom agrees only to security orchestration scope.

Explicit exception, not satisfied normal admission

INTENT and accepted security-layer-model v0.8 retain the sole PDP and ordinary PEP obligations. The tool intentionally overrides genuine ordinary application. register denial after preserving its identified decision and audit. That is a proposed exceptional administrative act, not normal conforming admission and not an outage stance or PDP allow. Maintenance actor is truthfully SERVICE with urn:supervised-maintenance issuer, explicit attribution and no forged human JWT, roles, assurance or invented login. Exception result has no PDP decision ID. No standard, normal service endpoint, IAM policy or existing PDP adapter changes.

The private mode0600 canonical-hash grant is out-of-band supervised evidence, not authentication of its author. Custodian must independently verify actual founder disposition for this exact executor AND transport, records, Ready pod/ immutable image, deadline and recovery. Prior readback R2 authority is insufficient. Both native dry-run and apply require that distinct scope. The dry-run may cause real external PDP telemetry while rolling back local rows/audits/outbox/ledger; it is not globally side-effect free. Future human acceptance must preserve normal admission as unmet and record the exact conditional close-down relaxation. This source preparation creates no active exception or scored execution success.

Expiry, one-use and recovery

Closed grant requires exact integer memo revision, fixed proposal/memo/record/ executor hashes and maximum deadline2026-10-12T23:59:59Z. The fixed method/request binding and <=30s lifetime are narrow. SERIALIZABLE transaction, fixed application advisory lock, native DB clock checks and persisted audit-key ledger bind absent/ exact admission and prevent replay after process restart. Both services must be constructed before BEGIN because readiness rolls back its connection. Final clock check is precommit; it is not observation of commit completing by expiry.

Exact pre-existing match consumes with no creation or undo. Partial/conflicting facts, unavailable/uncertain provider deny or unexpected ordinary allow refuse. Created-only recovery requires the original consumed grant hash before expiry, unchanged exact two records, no later dependencies, preserved event IDs and the existing delivery-worker lock. Missing, claimed or delivered events stop recovery. History is retained, not erased. A changed grant/operator cannot defeat one-use or create fresh rollback authority. Failed or expired recovery needs separate owner reconciliation and disposition; no reversal of downstream effects is claimed.

Retained event and replay boundary

The registered event remains attributive, with maintenance_exception/proposal/ approval/operator labels, transported through the existing audit envelope. It is not an invitation mail class or a user-authorization grant. Standard pending drain excludes dead-lettered rollback events. Separately authorized targeted delivery/replay can revive retained events; this proposal explicitly grants neither. The reviewer agrees to the added caveat requiring separate owner reconciliation/disposition before any such later action. Preserve rollback/event IDs so a future consumer/reviewer can correlate the retired registration and avoid mistaking delayed evidence for current facts. No complete consumer inventory, faithful-display, native audit arrival or stream-completeness claim is made.

Verification and remaining authority

Fresh dedicated User Engine owner agreement is applied in its own review file; this worker neither replaces it nor signs that role. Its independently recorded 21 isolated PostgreSQL checks passed on current exact source and immutable f239 installed package dependencies, with private fixtures/cleanup limits retained. That is not a native database invocation or authority grant. This NetKingdom review independently reran the five pure negative tests on the applied executor: all pass, with no network/database/credential access. Earlier sixteen-test receipt and constructor failures remain history, not relabelled as final proof.

No further source change is required for this narrow technical agreement. Before execution the requester still needs exact human exception and all required owner acknowledgments; freeze concrete grant/target preconditions and supervise the already prepared source transport. Afterwards verify exact two codec payloads, one consumed ledger, genuine denial/maintenance audits, attributed event and native catalogue/readback boundaries. Human MFA/allow and any complete journey remain separate; USER-WP-0026-T03/USER-WP-0028-T02 cannot close from this review. No native write, credential read, login, new agent, runtime publication or founder ruling occurred. This review introduces no NetKingdom standard permission.