DreamLake

Ownership foundation (unreleased)

Package A implements named namespace ownership capabilities, the shared transfer journal and inbox protocol. Namespace ownership is independent of creator attribution and project filing. Departed memo creators no longer retain rename, visibility, deletion or sharing management; independent public/share rights are evaluated separately. Source editor and existing Project ADMIN grant semantics remain unchanged.

The adapter contract and versioned fixtures are in dreamlake-server/src/ownership/contract.ts and fixtures/v1/transfer.json. The integration guide is src/ownership/README.md. Actual routes use /namespaces/:namespace/ownership, where the path namespace is a slug and request owner IDs remain opaque. The shared capabilities, preview, creation, incoming/outgoing inbox, status, accept/reject/cancel surfaces are available in the draft server, UI, CLI and SDK code. Installed/deployed availability is unverified. The production registry remains empty: real resource transfers are explicitly unsupported until B/C/D prove all adapter gates.

The journal persists separate accepted policy, actor/destination approval, dependency snapshot, idempotency request hash, revision, owner-commit marker, resource epochs and redacted audit events. The default policy makes resources private and revokes old grants. Preparing fences every manifest resource; cancellation remains fenced through abort cleanup. Failures before owner CAS abort staging; failures after it roll forward. No owner rollback follows a destination write. Database retries revalidate authority in a fresh snapshot; external effects are idempotent by operation identity.

Organization/team membership changes share an atomic Organization write parent. Removal and demotion cannot bypass last-owner/maintainer protection by racing counts. Lost approval authority invalidates pending operations and fences preparing recovery. User-issued project delegations are revoked on departure; creator history and organizational assets remain.

Organization deletion (unreleased)

Organization Settings supports terminal logical deletion, including organizations with resources and shared secrets. An owner must confirm the organization slug. Before deletion, finish or cancel active runs and resolve in-flight ownership transfers. External machines and provider accounts are not terminated by this action; stop them separately before deleting the organization.

Memos use their existing durable deletion executor to revoke live RTC rooms. If revocation fails, the organization remains available and deletion can be retried; Memos already deleted during the attempt remain deleted. The final transaction rechecks owner authority and blockers, tombstones namespaces, resources and teams, removes memberships and grants, disables sharing and service identities, and retires organization/team Vault entries and access keys. The retained Organization is the terminal ownership record; resources never move to the deleting user's personal namespace. Its private deletion receipt records approval, owner identities and collection counts without secret values. Retained bytes and encrypted secrets are quarantined, not physically erased; there is no restore endpoint or purge deadline for this organization deletion. Existing signed download URLs may remain valid until their original expiry. The organization and namespace slugs remain reserved while data is retained. Team-only deletion remains unsupported.

Public skill impact: no public skill exposes organization lifecycle mutations; this Settings/GraphQL change does not alter Memos, CLI or scene skill procedures.

Release blockers: B credential scope/reseal and final plaintext release; C project/source atomic manifests, storage and destination connections; D memo RTC/session revocation, checkpoints, history/media and storage; E migration, fleet writer gates and operational crash-claim recovery. A crashed executor never reopens leases by timeout; recovery requires proof the old executor is stopped before its exact claim is cleared. Employee-issued memo share provenance and independently authenticated organization service actors are not available in the current schema and must not be inferred from user IDs.

Public skill impact: CLI command documentation and generated native help are updated in the CLI repository. Distributed public skill synchronization and publication are deferred to E's release integration; this draft must not claim released behavior. The internal adapter/recovery contract itself does not add a public task procedure. Local validation proves synthetic journal behavior and client protocol boundaries, not production transfers or RTC eviction.