user-engine/docs/evidence/2026-10-11-one-app-catalogue-human-packet/conditional-close-down-entry.md

Conditional single-control close-down entry — not active

Stable reference USER-CATALOGUE-INFDEC-20261011-R1; proposed only. If the founder accepts this exact memo, append one entry to Custodian's existing security-close-down checklist without removing or relabelling prior controls. Record the actual founder disposition, packet/executor/transport/grant hashes and native outcome before marking an executed relaxation.

Control: ordinary authenticated operator/PDP admission for User Engine application.register. Conditional exception: exactly one supervised registration of informed-decision Application and its exact browser-client/protected-system binding; genuine denial remains unmet and audited, followed by explicit maintenance attribution. No human/JWT roles, IAM grant, runtime endpoint, token/config change, future registrations or targeted event replay are authorized.

Authority deadline: 2026-10-12T23:59:59Z, with native precommit clock checks and durable consumed-grant closure. Existing catalogue facts are not automatically erased at expiry. Recovery may be blocked by expiry, changed rows/dependencies or claimed/delivered/missing events; owner reconciliation then needs separate disposition. Removing the private artifact is cleanup, not authentication/revocation proof.

Restoration owners: User Engine for the authenticated management surface/lifecycle, Access Engine for ordinary PDP admission; Custodian tracks the checklist and founder closes it. Criterion: before customer production, a supported management path authenticates genuine operators and performs ordinary authorization, demonstrated allow/deny/attribution and fail-closed unavailable behavior; retire the one-time tool from operational use, retain consumed ledger/audits/events and reconcile any retained registration/rollback event. This draft does not claim that restoration already exists, create another workplan, or promote agent autonomy.