Propose inactive application parent creation with explicit entitlements
App2104 currently validates registration proposals but has no durable parent-creation transaction. This draft adds a Database-only candidate that atomically creates disabled application/environment/origin parents under a separately enrolled personal principal and explicit creation entitlement. It creates no management permissions implicitly. The existing proof/configuration SQL composes through pinned mechanical parent/authority bindings.
All seven files are under proposals/application-registration-2104; no migration, workflow, public route, runtime grant, credential verifier, connection string or activation changes. Personal-workspace policy remains proposed and unadopted. Creation entitlement expiry is qualified; post-create permissions support explicit revocation only, not time leases. Real authentication remains a trusted-server precondition.
Validation: the current f507a776 successor passed 20 focused tests on disposable PostgreSQL 15 and 17 with verified normal cleanup. Earlier unchanged-runner signal, timeout and exited-worker cleanup controls passed on PG15; those fault controls were not rerun for this two-annotation SQL change. Tests include actual observed lock waits, current-authorization replay, rollback, foreign binding denial, disabled receipts and PUBLIC/helper denial. Credential-label tests are stub-only; no live authentication/provider/database behavior was exercised.
DRAFT / UNMERGED / UNAPPLIED. The reviewed source-only successor is published; merge, apply and runtime activation remain gated. No claim of least-privilege runtime readiness, production persistence, approved retention or customer pilot authorization.
Current source successor f507a77696f20429f977df9885d6c8c11a5f304b reserves P2101 for only changed same-key fingerprints and stale entitlement revision on a new request. Authority-denied 42501, lock/replay/expiry behavior and disabled receipts remain unchanged. Structured SQLSTATE tests verify all five registration tables remain unchanged after conflicts. API compatibility and disposable joined qualification are tracked separately in https://github.com/recoupable/api/pull/1273; no public registration availability is claimed.
Runner follow-up: explicit minimal subprocess environments with owned HOME/TMPDIR, UTF8 qualification, and fail-closed checked group enumeration only after a permission-denied signal probe. The actual failed intermediate cleanup and its safe stop/preserved directory are retained in the review packet.
Summary by cubic
Adds a draft Database-only transaction that atomically creates disabled application, environment, and origin parents under a separately enrolled personal principal with an explicit creation entitlement, without granting management permissions or issuing credentials implicitly. Existing proof/configuration SQL composes through pinned source-hash bindings; no migration, workflow, public route, runtime grant, credential verifier, or deployment changes.
- Defines a structured conflict outcome: SQLSTATE
P2101is reserved for exactly two definite failures — an existing retry key with a different fingerprint, and a new request whose expected entitlement revision differs from current authority.42501remains authority-denied and other errors stayP0001; tests assertRETURNED_SQLSTATEinside subtransactions. - Adds 18 disposable PostgreSQL 15/17 tests covering lock waits, rollback, replay, revocation, denial, and environment isolation.
- Fixes owned worker-group cleanup to fall back to checked group enumeration only after a
killpg(group,0)PermissionError. - Keeps personal-workspace policy and pilot authorization unadopted.