Halo Family commits 1 files 8 Markdown only

Pre-push review: T2444 staged removal design

Critically integrate the independent recommendation; preserve approved defaults and separate offline implementation from bounded native cloud enablement.

At a glance

  • Owner: one exact graph save and framework history delivery; no automatic owner-share deletion.
  • Participant: exact Shared CKShare departure, including accepted read-only participants.
  • Public identity checkpoints plus current root/zone/share/account/role checks replace undocumented plain lookup assumptions.
  • Known-host retirement and fresh plain construction are concrete gates, with ten native cases in one bounded campaign.

Verdict

Ready for design approval

Critic and independent technical/architecture peers clear the revised documents. Approved requirement text is retained verbatim. This is a documentation-only publication; O1–O5/C0–C3 are planned and unexecuted. No destructive implementation, store/cloud operation, signing or deployment is authorized or performed.

Review findings

3 raised · 3 fixed · 0 skipped

Jump to findings →

Commits

Three-level explanation

Verify one chosen external file before removing one family. The owner removes its graph; a participant leaves its share. Cloud status can remain pending, and recovery creates a new private family.

The proposed cloud workflow temporarily delays sync and restarts the app, requiring technical design approval and native acceptance.

The offline foundation adds actual-byte verification, family/draft admission, one graph save, durable outcomes and complete fresh-ID remapping. Public checkpoint metadata identifies targets; exact network checks supply current available authority.

Owner graph commit and participant share submission have separate witnesses. Restart never carries old eligibility forward.

Import exclusion is a composed fresh-process/plain-container/participating-host ownership design. It is not a queue or optimistic-lock guarantee. C1 tests queued work, all entry points and legacy retirement; C2 tests known history delivery; C3 tests membership/callback-loss cleanup.

Unknown originals stay closed without replay. Bundle URLs do not identify executing Mac code after replacement; every other identified host must exit.

Important changes — detailed

Separate owner rows from participant membership

specs/delete-everything/design.md

Why it matters. Avoids a second destructive owner-share step and prevents participant graph deletion.

What to look at. Owner deletion and participant departure

Takeaway. Operation evidence should follow the actual primitive, not a generic deletion label.
Rationale. Apple Shared Records and Core Data history/sharing contracts, approved selected-family scope.

Use explicit identity and current authority

specs/delete-everything/design.md

Why it matters. Public cached identity alone is not permission, and plain-container lookup is not assumed.

What to look at. Identity checkpoints and current authority

Takeaway. Separate preparation identity from current authenticated authority.
Rationale. Record mapping omits unexported rows; share lookup is cached/known only; zone/share/current role must corroborate scope.

Bound verification instead of blanket proof demands

specs/delete-everything/design.md

Why it matters. Offline foundation can progress while native construction/delivery is measured with exact failure exits.

What to look at. O1–O5 / C0–C3

Takeaway. Name the test, deadline and fallback for each load-bearing assumption.
Rationale. Approved local snapshot/pending outcomes do not require a distributed lock or universal tombstone acknowledgment.

Do not trust updated bundle files as process version

specs/delete-everything/decision_log.md

Why it matters. An old Mac process can survive an in-place update and ignore new admission leases.

What to look at. D29

Takeaway. Installed-package identity and executing-process retirement are different facts.
Rationale. Independent technical peer and public NSRunningApplication property contracts.

Key decisions

Keep local 3.2 while narrowing unsupported extra promises

Normal mirrored compare-and-save remains unavailable. Fresh plain construction and participating-host ownership are an inference backed by required C1 acceptance. Global freshness, permanent server permission locks and universal tombstone proof are outside approved scope.

Review findings

SeverityAreaFindingResolution
majorProcess retirementOn-disk version could misclassify an older executing process.Refuse every other identified host until observed exit; test in-place replacement.
minorAuthority/rerun clarityCompatibility, full authority conjunction and allowed rerun needed explicit predicates.Define installation epoch/protocol, exact store/root/zone/share/account/role checks and fresh-fixture or verified-not-started-only reruns.
minorHistorical precedenceOld unresolved mapping/workflow assessment could conceal the current concrete plan.ADR-3 states precedence, historical review headers are dated, canonical current evidence is updated.

Per-file diffs

8 files: 8 docs. Click to expand.

CHANGELOG.md Modified +5 / -0
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 7c10839..3fa1e7a 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -34,6 +34,11 @@  ### Changed +- Reconcile selected-family removal with one owner graph save/framework delivery,+  read-only participant Leave and public identity checkpoints; define bounded+  offline/native verification and concrete process-retirement criteria while+  preserving approved defaults and excluding destructive implementation.+ - Reconcile input/action implementation specs and current evidence with 281 passing   domain tests, qualified native corrections and the earlier physical Release;   retain actual failed runs and separate device/system acceptance.
docs/halo_family_design_pack/10-initial-implementation-results.md Modified +33 / -0
diff --git a/docs/halo_family_design_pack/10-initial-implementation-results.md b/docs/halo_family_design_pack/10-initial-implementation-results.mdindex 40bdeff..9505d1d 100644--- a/docs/halo_family_design_pack/10-initial-implementation-results.md+++ b/docs/halo_family_design_pack/10-initial-implementation-results.md@@ -69,6 +69,39 @@ manual assistive technology and live account/CloudKit/native extension acceptanc remain separate. No private audio/data read, model download, reset, native Contacts write, account/signing change or further physical install occurs. +## T2444 removal design reconciliation — 2026-10-13++The independent read-only recommendation is integrated into the existing removal+requirements/design/review/decision log. Approved normative requirements and D1–D9+are retained byte-for-byte; technical interpretation is separate. Critic and two+independent peer reviews clear the revised technical design for approval. External+Codex/Kiro tools are unavailable; the documented peer fallback is explicit.++Owner removal proposes one exact graph save with retained history and normal+framework delivery, without an automatic owner-share delete. Accepted read-only+participants can Leave the exact CKShare in Shared after readable verified export.+Public mirrored-operation identity checkpoints plus exact current root/zone/share/+account/environment/role checks replace undocumented non-mirroring lookup reliance.+Fresh plain entry owns a stable process-lifetime library lease. Every other identified+Mac Halo host must actually exit; newer bundle files do not identify its loaded code.++The proposed plan separates O1–O5 offline implementation from C0 packaging,+C1 import/process exclusion, C2 history delivery and C3 participant departure.+Ten named native cases, a 60-minute campaign and five-minute observation deadlines+provide bounded acceptance with specific failure exits. Global cloud freshness,+permanent permission locks and universal tombstone acknowledgment are not additional+prerequisites. The unchanged-local-dataset guarantee and honest closed/pending+outcomes remain intact. No planned test is reported as executed.++Next authority is revised technical design/offline implementation, including the+fresh-process/both-store sync-delay workflow. Disposable cloud identities and exact+fixture operations, signing/environment binding and any installation/account/schema+work need separate explicit scope. Current `cd98717b` backend remains unestablished;+no configuration, namespace or data migration occurs. This update changes Markdown+only; no destructive implementation, store opening, test/build, CloudKit operation+or device deployment is performed. [Design](../../specs/delete-everything/design.md)+and [review](../../specs/delete-everything/review.md) own the decisions and source links.+ ## Intermediate input/refinement evidence retained  All following counts describe their own source snapshots and are not final broad
docs/halo_family_design_pack/README.md Modified +6 / -3
diff --git a/docs/halo_family_design_pack/README.md b/docs/halo_family_design_pack/README.mdindex 754e2b5..83064d6 100644--- a/docs/halo_family_design_pack/README.md+++ b/docs/halo_family_design_pack/README.md@@ -74,9 +74,12 @@ schema deletion is performed. - [Delete Everything requirements](../../specs/delete-everything/requirements.md)   and [critic/peer review](../../specs/delete-everything/review.md). Requirements and   external-only/local-snapshot/fresh-private-restore/closed-pending defaults are-  approved. The [design](../../specs/delete-everything/design.md) remains unapproved;-  both cloud branches are blocked on a supported import-versus-first-action boundary.-  No live deletion or implementation is authorised. See the [decision log](../../specs/delete-everything/decision_log.md).+  approved. The revised [design](../../specs/delete-everything/design.md) is reviewed+  and ready for technical approval, with an independent offline foundation and+  bounded native cloud gates C0–C3. Owner removal uses one graph save/framework+  delivery; accepted read-only participants can Leave the exact Shared CKShare.+  Both cloud actions remain disabled until their gates pass. No deletion+  implementation or live test is authorised. See the [decision log](../../specs/delete-everything/decision_log.md). - [Friendly onboarding discussion](13-friendly-onboarding-discussion.md). Confirmed   directions are separated from proposed Setup/Join steps; no onboarding source is   implemented by this draft.
specs/delete-everything/decision_log.md Modified +61 / -0
diff --git a/specs/delete-everything/decision_log.md b/specs/delete-everything/decision_log.mdindex 3651095..86931c3 100644--- a/specs/delete-everything/decision_log.md+++ b/specs/delete-everything/decision_log.md@@ -123,3 +123,64 @@ signature was modified. Only environment fields were retained in private technic evidence, without profile device IDs, certificates, account records or family data. No build/test, device operation, CloudKit call, store opening, signing/permission change or deletion experiment accompanies this investigation.++## ADR-3: Bounded offline foundation and separate native enablement++**Status:** Proposed technical design, 2026-10-13; requirements/defaults remain+approved. The independent recommendation is critically reconciled against current+source/public SDK contracts. No destructive code or live test is authorized.++**Decision:** Use one explicit owned-graph Core Data save and framework history+delivery; participant departure is one exact Shared CKShare operation. Build and+verify the offline foundation first after design/implementation approval. The+cloud candidate uses a fresh plain process and app-owned importer ownership, with+public identity checkpoints and current CloudKit authority. C0–C3 are concrete+native enabling gates, separately authorized and bounded; their failure cannot+block independently useful offline design work.++**Precedence:** ADR-3/D22–D28 supersede ADR-2's unestablished plain-session+mapping/workflow assessment with the public checkpoint, current permission provider+and bounded acceptance plan. ADR-2's ordinary-session/no-await and hot-replacement+rejections remain. D21's non-mirroring-subclass lookup question is no longer a+dependency; this design never calls it. Native construction/resume acceptance and+explicit environment binding remain real prerequisites.++**Alternatives rejected:** A final re-fetch in normal mirroring does not preserve+3.2 against new rows. Hot toggling/detaching and a non-mirrored subclass mapping+assumption remain unsupported. A new sync engine, per-family store migration or+default-zone purge is disproportionate. Requiring global freshness, no subsequent+remote revocation or universal tombstone delivery contradicts the approved local+snapshot/pending-state scope.++**Contract assessment:** TN3164 recommends app-owned synchronization and warns about retained containers;+Halo uses supported plain-container extension loading, and TN3163 describes the+importer/exporter.+Extending that construction to a genuinely new exclusive plain host is an inference,+not an Apple compare-and-delete guarantee. Native C1 must validate the actual+process/entry/queued-work behavior before cloud enablement. A failed case triggers+a specific Apple question, not an indefinite demand to prove every system service+incapable of writing SQLite. Ordinary platform acceptance does not become a claim+that a finite test establishes a universal theorem.++**Cost/approval:** Maintenance delays both-store sync and requires fresh process+entry/resumption. Approve this technical workflow and offline implementation+separately; do not re-ask D1–D9. A cloud campaign additionally needs exact disposable+container/environment/accounts/devices/fixture-operation scope. Binding the current+app's previously unknown backend needs separate signing/configuration authority;+no data/cache migration is inferred.++| ID | Technical decision | Scope/status and rationale |+| --- | --- | --- |+| D22 | Owner graph save plus framework mirroring; no automatic CKShare delete. | Proposed design. Exact row scope avoids zone-wide side effects and a second unknown destructive operation. Surviving share/uncertain delivery stays explicit; any cleanup is separate. Supersedes the automatic owner-share step in the design, preserving its history here. |+| D23 | Read-only accepted participants may Leave exact Shared CKShare. | Public contract. Graph write authority is irrelevant to departure; unreadable/unverified export still blocks. Membership callback is separate from graph history/local cache cleanup. |+| D24 | Capture public identity checkpoints in normal mirroring; validate network association/authority in maintenance. | Proposed design. Avoid undocumented non-mirroring lookups. Root/share association is mandatory for Leave/Shared access; missing non-root owner row IDs limit observation and retain pending, rather than forcing IDs or blocking a locally valid graph save. |+| D25 | Preserve local snapshot match; do not require global cloud locks or universal tombstone proof. | Clarification of approved scope. Current available role/account is checked; server submission resolves later permission races. Honest pending/unknown is permitted by D9, not a reason to require impossible completion proof before enablement. |+| D26 | One-family share invariant and target provenance, without global zone enumeration. | Required for selected-family Leave. Source has one `cloud.share([family], to: nil)` creation site. Audit all future mutation/import/restore paths, reject multi-root/legacy ambiguity and verify distinct fixture shares natively. Owner row deletion does not require sole-zone proof. |+| D27 | Stable process-lifetime library mirroring owner plus per-family/lifetime operation leases. | Proposed design. All host entry points participate; never release ownership merely by replacing a retained container. Compatibility/legacy retirement is tested before enabling affected installations; no PID-age takeover or process kills. |+| D28 | Replace blanket proof demands with O1–O5 / C0–C3 and bounded failure exits. | Proposed verification plan. Each safety prerequisite has a named test/contract; 60-minute native campaign with ten scenarios maximum and five-minute observation deadlines. Failed gates stay unavailable with exact evidence; no automatic destructive retry. |+| D29 | Require every other identified Mac Halo host to exit, regardless of on-disk version. | Peer-corrected activation rule. NSRunningApplication exposes bundle/executable URLs, not the loaded build version; an in-place update can leave old code running. Use identity to locate other hosts and observed termination to establish exit. Installed component/epoch checks remain separate; no process is killed. |++Current signed-artifact reference is `cd98717b`, not the historical `131ef78`+inspection in D20. Canonical evidence/install receipt report absent actual runtime/+entitlement environment declarations; this reconciliation performed no signature+inspection or backend access. D20's explicit-binding gate remains intact.
specs/delete-everything/design.md Modified +241 / -182
diff --git a/specs/delete-everything/design.md b/specs/delete-everything/design.mdindex cf624e7..c677797 100644--- a/specs/delete-everything/design.md+++ b/specs/delete-everything/design.md@@ -1,7 +1,7 @@ # Selected-family removal — design for approval  Status: requirements D1–D9 are approved. This design requires critic/peer review-and explicit design approval before implementation. No live operation is included. Both cloud-owner deletion and participant departure have a blocking transaction-feasibility dependency described below; it remains disabled until that dependency is resolved and reviewed.+and explicit design approval before implementation. No live operation is included. Device-only implementation is planned first. Cloud-owner deletion and participant Leave remain disabled until the bounded construction, scope and native acceptance gates below pass. No destructive implementation or experiment is authorized by this document.  ## Architecture and integration @@ -37,6 +37,8 @@ context executor. CloudKit mirroring remains host-owned. | Host editor sheets / inline capture drafts | Yes | Route binding/draft creation and mutation through a shared family lease plus synchronized FamilyDraftRegistry; save/discard before eligibility. Eligible/Intent denies affected draft changes across all windows. | | Persistent history / remote-store changes | Yes, no importer fence | Invalidate eligibility; retain unresolved operation author/token anchors for commit reconciliation. Mirroring remains outside local leases. | | Account invalidation / stack loading | Yes | Recover admission ledger before exposing stores; preserve other-account files and deny stale scope. |+| `PersistenceStack.production/open`, host scenes/background entries, `ShareInvitations.retry` | Yes | Resolve mode and acquire the stable library mirroring-owner lease before any host stack; hold it through the process lifetime, including account changes. |+| `FamilySharing.createOrFetch/persist/accept`, permission refresh and store replacement | Yes | Publish/invalidate bounded public root/share identity checkpoints; Share changes are not inferred from graph history. Keep one FamilySpace per newly created share. | | `FamilySharing` / native sharing callbacks | Yes | Verify existing share/role; retain original qualified identity through async completion; no stop-sharing shortcut around export. |  ## Export and confirmation contract@@ -187,150 +189,179 @@ no entire defaults suite, account directory or store is deleted.  ## Owner deletion and participant departure -**Owner/device library:** Under exclusive admission, use one fresh context to-revalidate inventory/provenance and explicitly delete all owned rows plus the root.-Reuse transactional permission checks and history/merge delivery; do not rely on-FamilySpace's Nullify rules or batch deletion without context/history merging.-Capture backing record IDs before graph deletion for scoped cloud observation.-Save once with a coordinator capability restricted to this operation/family.-Device-only graph completion has no cloud phase.--For a cloud owner, allow Core Data to mirror those exact row deletions. Remove the-selected family's verified sole CKShare through the matching Private database-only after local commit; never delete a default or multi-family zone. If that share also-covers another FamilySpace or its ownership is unresolved, confirmation is blocked.-Failure/callback loss records pending/unknown rather than retrying deletion. Native-proof of metadata/mirroring behavior precedes enabling this branch (4.1, 4.3, D11).--**Participant:** Verify the selected FamilySpace's existing CKShare and current-participant/Shared database. Stop participation by deleting that share record in-Shared via the cloud driver, preserving the owner's graph. Persist local read/write-denial for this family at intent; framework leave/import cleanup owns mirrored row-removal. Never call `FamilyRepository` graph deletion on participant records. Local-cache removal alone is not departure. A share covering multiple families blocks-selected-family leave rather than expanding scope (4.2, 4.4).--Cloud adapters preserve container/database/account/environment and exact record-IDs. Owner observation uses `CKFetchRecordsOperation` for pre-commit mapped IDs in-Private; only per-record `unknownItem` under the unchanged authenticated scope is-observed absence. Unmapped IDs, partial failures, permission/account changes or-late local target rows keep outcome pending/unknown. Absence and a store-wide export-event do not prove that all deletion tombstones were delivered; without supported-per-target delivery evidence, label owner cloud removal pending rather than complete.-Participant departure is confirmed only by per-item success deleting the recorded-CKShare in Shared, or a successfully scoped reconciliation proving that exact share-is no longer accessible as this participant. Permission/network errors alone are-unknown. Never replay an unknown delete to obtain confirmation (3.5, 4.3, 5.1).--### Signed environment gate--Before enabling either cloud branch, an explicitly approved environment setting-must supply both the signed `com.apple.developer.icloud-container-environment`-value and a `HaloCloudEnvironment` runtime declaration. Map only Development and-Production to the existing lowercase namespace values; host and extension consumers-must use the same declared value before account-directory selection. Do not infer-it from DEBUG, optimization, APNs or a profile allowing both environments (D20).--Verify the final package after any archive/export/re-sign step, rather than only-its source entitlement file or pre-export build. Compare the actual signed host-and applicable extension entitlements, their Info.plist declarations and the-profile's permitted environment; record source/package hashes. Missing/mismatched-values block removal. Rechecking final packaging matters because Xcode distribution-can apply different entitlements. This check proves artifact binding, not account-identity or native CloudKit acceptance; the driver must still verify the current-account/container/database and reject stale operation scope.--The retained signed `131ef78` package has neither that entitlement nor the runtime-declaration, while its profile permits both environments. It does not satisfy-this gate. The checked primary docs do not establish a fallback that can settle-its effective backend. Preserve all existing cache directories; choosing or-changing the backend is outside this design preparation and needs separate authority.--### Blocking cloud transaction gate--Keep both cloud branches disabled. In a normally mirrored session, the checked-public API contract has no per-family import pause/drain or multi-operation-compare-and-delete primitive. Events/history observe work, rather than acquiring-exclusion. No-await, pinned query generations and optimistic conflicts cannot-exclude new rows; coordinator queue execution supplies no documented importer-fence. Do not hot-toggle store options, release/recreate a live container, detach-stores, use private mirroring requests or rely on airplane mode/raw SQLite (D18).--| Public option | Verified boundary and remaining constraint |-| --- | --- |-| Continue normal mirroring and recheck the inventory | No supported exclusion through the first action is established; remain disabled under 3.2. Event completion/idle observation is insufficient. |-| Start a fresh non-mirroring host session | Plain-container construction is supported and used by Halo extensions, but the current plain host loses Shared-family permissions and lacks the required public record/share mapping route. It is only a conditional exclusion candidate, not an established removal flow or live-container pause/drain API. |-| Framework purge of a verified sole-family share zone | Apple's `purgeObjectsAndRecordsInZone` coordinates zone and local graph removal/departure, but takes no expected inventory generation/fingerprint. It does not supply 3.2's conditional boundary. Default/multi-family zones remain forbidden (D19). |--The fresh-session candidate must be selected before `PersistenceStack.open` creates-any `.host` mirroring stack, and apply to both existing account-qualified stores-for that process lifetime. Exclusion must also cover every prior or other host-process using the same account/App Group stores, including another macOS host-instance; `hostTask`/`hostGeneration` are only per-process caches. This cross-process-importer-ownership contract is unestablished. Normal UI windows, background host entry points and-App Intents cannot construct a second mirrored stack. Extensions stay on their-existing plain-container path, with all participating writes behind family-admission. Keep persistent history and cloud metadata intact. Do not enter this-mode from an already mirroring process or programmatically terminate the app.--Only a genuine new process, not foregrounding, reopening a window or an assumed-relaunch, can establish never-created mirroring ownership. The guard must precede-`PersistenceStack.production`, `ShareInvitations.retry` and all background/scene-entry points; a replaced container can remain alive through retained objects.--A fresh launch requires a new review/export under 3.4; it cannot resume old-eligibility or submit deletion during startup. The parent must explicitly confirm-after current data/file/draft/access checks. Verify current ownership/membership-through the exact authenticated CloudKit scope without starting a Core Data-importer, and do not weaken permission checks for plain-container loading. This-route is unresolved: public object-to-record/share mapping and relevant permission-methods are declared on `NSPersistentCloudKitContainer`; no supported equivalent-for this plain session has been established. Missing mapping cannot prove owner,-participant or sole-family zone identity. Do not synthesize CKRecord IDs or treat-an unverified retained mapping as current authority.--The class name alone does not settle the question: Apple also supports-`NSPersistentCloudKitContainer` managing non-cloud stores. Whether a fresh instance-with both descriptions explicitly nonmirrored can read retained, correctly scoped-record/share mappings without creating an importer is a narrow unresolved public--contract question (D21), not a suggested helper or probe. Its non-cloud-`canUpdateRecord`/`canDeleteRecord` YES result is not proof of Shared participant-permission; the SDK allows YES for stores not backed by a CKDatabase. Equivalent-current authority and unrelated-family access remain required even if mapping is-available. Do not enable this alternative from the class declaration alone.--`AccessPermissions.refreshAccess` currently publishes no Shared-family permissions-for a plain host, and `revalidateSharedAccess` exits early. The candidate therefore-cannot meet unrelated-family availability as written. A supported equivalent-mapping/access contract preserving 1.3/5.5 is a blocking prerequisite, not a generic-future test. Do not add a permission bypass or mirror-enabled helper to conceal it.--This candidate suspends new host mirroring for the whole library and needs a-user-mediated fresh launch; restoring normal mirroring needs a later fresh session.-Its workflow cost is a conditional future UX choice after mapping/access and-entry/resume feasibility are resolved; no such acceptance is requested now and-D1–D9 remain settled. This candidate is not adopted or implemented. Prefer the-existing architecture and keep the cloud action unavailable rather than introduce-an unverified lifecycle mode. An SDK declaration does not prove process isolation.--If this option is chosen, verify entry-point coverage and bounded host/extension-races first, then separately authorised native CloudKit-backed-store history,-export/resume, departure/cleanup and late-import acceptance. Row deletion in the-plain session and direct CKShare departure submission are separate from resuming-mirroring. Resume must distinguish automatic delivery of known committed history-from application replay of an unknown operation, retain unresolved history anchors-and enforce closed-scope reads/writes before exposing a normal stack. Its ordering-against imports, conflicts and share cleanup is still unverified. A framework purge that requires a cloud-backed container cannot inherit-the plain session's exclusion; its combined boundary remains unestablished.-Remote/offline changes are still outside the verified local snapshot, and resumed-imports/deletion conflicts retain closed pending/unknown under 3.5/4.3. Local or-mocked tests do not establish cloud deletion safety.--Do not introduce per-family stores, zone migration or a bespoke sync engine just-to bypass this gate. If the fresh-session cost is rejected, the normal-session-branch needs an authoritative supported API/confinement contract before enablement;-requesting that contract does not authorise a destructive probe. Device-only-operations continue to fence participating local writers and draft setters.+**Device library / owned Private family:** Under exclusive family admission, use+one fresh context to revalidate inventory/provenance and explicitly delete the+owned rows plus root. Save once with the opaque operation author and restricted+family capability. Nullify rules, root-only deletion and global orphan sweeps do+not satisfy 4.1. The same-store history witness reconciles local commit; covered+ancillary cleanup has separate outcomes. Device-only removal has no cloud phase.++**Cloud owner:** Perform that one graph save under the validated non-mirroring+session below. Keep persistent history and CloudKit metadata intact. Resume ordinary+host mirroring in a later fresh process so the framework exports the committed+history. Do not directly delete backing graph records or automatically delete the+owner's CKShare. An empty surviving share is reported as retained; if it prevents+export or truthful graph status, keep cloud delivery pending. A separate stop-sharing+or zone-purge action requires its own scope, review and export; it is outside this+operation (D22). Owner row deletion does not require a sole-family-zone proof.++**Participant:** Require readable export access and accepted membership in the+exact existing Shared CKShare; graph write permission is not required. A read-only+participant can Leave. Record closed admission and exact share-delete intent, then+submit that CKShare once to the participant's Shared database. Never delete its+mirrored FamilySpace/owned rows manually: write-capable participants could thereby+delete the owner's data. Per-item success witnesses membership ended, not local+cleanup. Callback loss stays unknown. Graph history is not a leave witness because+share changes do not generate those transactions (D23).++A participant Leave target share must represent only the selected family. `FamilySharing` creates a+new share with `[family]` and `to: nil`; retain that one-family-per-share rule at+all share/restore/import boundaries and validate reachable same-family provenance.+Resolve public mappings for every locally known root and reject a second root with+the same share. Native acceptance verifies separate families produce separate+shares and covers legacy ambiguous/multi-family fixtures. Local enumeration alone+is not global proof: existing shares without verifiable association/protocol+provenance stay unavailable for Leave. Do not require global cloud enumeration+or an atomic reservation against every remote client (1.1, D26).++### Identity checkpoints and current authority++Use normal mirrored operation to obtain public `recordIDs(for:)` and+`fetchShares(matching:)` results. Publish bounded identity-only checkpoints containing+namespace, store UUID, permanent root object URI, canonical FamilyAccessID, exact+record/zone owner IDs and associated share ID. Known target row IDs may be included+for observation. Store no CKRecord/CKShare archive or graph payload. Missing IDs+remain explicit; never synthesize IDs from UUIDs or private mirroring metadata.++Checkpoints are preparation inputs, not eligibility or permission capabilities.+A maintenance process loads ordinary `NSPersistentContainer` stores and validates+local root identity/store UUID and checkpoint coverage before use. Invalidate on+account/store replacement, migration, sharing callbacks, changed associations or+missing intervening history. Share metadata can change without graph history, so+history/fingerprints alone never make a checkpoint current.++For shared authority, fetch exact checkpoint targets from Private for the shared+owner, or Shared for a participant. Require all of: local FamilySpace entity,+canonical UUID, permanent root URI and store UUID match; fetched root/zone IDs+match; fetched `zone.share.recordID` equals the checkpoint share ID; fetched CKShare+ID/zone matches; account/container/environment/database remains unchanged; and+`currentUserParticipant` is the owner for owner action, or accepted with read-only/+read-write access for Leave. Missing/conflicting evidence invalidates only that+scope. Root/share ID equality alone is insufficient. Fetch/verify each unrelated+Shared family's current permission independently.++A conflicting association, missing root/share, unknown provenance or wrong database+returns to normal sync for a new checkpoint; do not open a mirrored helper in+maintenance or depend on lookup methods in a non-mirroring CloudKit-container+subclass. This uses public record/zone/share identity, without a private metadata+or schema-field guess (D24).++Owned Private graph removal uses verified account/store provenance and its local+inventory. Missing non-root row record IDs limit cloud observation, rather than forcing+fabricated IDs or blocking the local save. A known shared owner must still have+current owner authority; ambiguous target ownership blocks confirmation. The+maintenance permission provider independently preserves normal readable/writable+rules for unrelated Shared families; absent authority closes only its unresolved+scope. It plugs into `StoreAccess`/`AccessPermissions`, never their bypass.++Recheck account/scope after network awaits and before intent. This checks current+available authority, not a distributed permission lock. The server remains final+authority for Leave; later revocation or network failure produces the corresponding+failed/unknown outcome without reopening the original (1.3, 3.2, D25).++### Import exclusion and host ownership++Normal mirrored confirmation stays unavailable: a final fetch/no-await, pinned+query generation, optimistic row conflict or coordinator queue cannot exclude a+new imported row through the first action (3.2). The selected construction is a+genuine fresh process with plain stores, not a hot pause/detach/replacement.++Before loading any store, every participating normal host and maintenance host+acquires the same stable App Group library mirroring-owner lock nonblockingly.+Keep that file's identity stable; never unlink/replace it. Retain ownership for the+whole persistence-bearing process lifetime, including account changes. A second+host reports the busy library and cannot construct mirroring. App Intents, scenes,+background entries, invitation retry and lazy services share this mode resolver.+Extensions stay plain and acquire family admission at their actual write boundary.+No process is killed and no recovery waits for ownership while holding a family or+store lock. Process ID/age files are not lock ownership evidence (D27).++Enable maintenance for an installation only after its installed host and every+bundled store-writing extension declare the supported admission/ownership protocol,+the host is a genuinely fresh process holding the library lease, and no known+running Halo host exists apart from the fresh candidate. On macOS, public+running-application bundle identity locates other Halo hosts; every identified+other host must exit normally, confirmed by termination state/notification. Its+on-disk bundle version does not identify the executable image already running,+including after an in-place update. Do not infer retirement from a termination+request returning or from newer files at the same URL. On iOS, C1 must exercise the app-update/extension-+retirement condition for that installed package before activation. Record the+compatible installation epoch (host/extension bundle IDs, declared protocol and+distinct build IDs), invalidate on downgrade/incompatible package change and rerun+checks on entry. Reused marketing version/build numbers are not process evidence. A marker does not fence a known legacy process.+This covers participating Halo clients, not arbitrary App Group writers. Failure+withholds that installation's cloud mode; O1–O4 remain independent. Hold the library+lease until exit so retained objects cannot outlive released importer ownership.++Plain-container loading, host-only mirroring and process lifetime are the supported+construction basis. No separate hypothetical global system-service drain API is+required before offline work. The composed construction's remaining platform+behavior is a named acceptance risk: C1 tests a previous importer exiting with+queued work, remote updates and every host wake-up entry while maintenance is open.+Any unexplained local imported transaction fails the gate and keeps cloud removal+disabled; escalate that reproducible case to Apple with exact configuration and+history, rather than repeating an unbounded search for a universal proof (D28).+This is an inference from documented architecture plus required native acceptance,+not an Apple-guaranteed compare-and-delete API.++Maintenance pauses sync for both stores, while unrelated local families retain+normal verified permissions. A fresh review/export is mandatory; no old Eligible+state or startup submission is reused. A later genuine fresh process resumes+mirroring. This launch/sync-delay workflow is part of the proposed technical design+requiring approval; it does not reopen D1–D9.++### Outcomes and safe resume++Load durable admission/outcomes before exposing any normal stack/catalog. Reconcile+known graph commit by same-store author, deletion IDs/root and retained history+anchor, never by row count or author alone. Framework delivery of that already+committed history is distinct from application replay; missing witness remains+closed/unknown. C2 verifies the plain-save/fresh-mirrored-start path without metadata+reset and with owner/co-parent/unrelated-family checks. Unknown graph or share+operations are never resubmitted automatically.++For participant Leave, only the exact successful delete result proves that request's+membership outcome. Read-only reconciliation can establish access unavailable;+if it cannot distinguish this request from another revocation, say access unavailable+and original request unknown. Framework resumption handles revoked rows; retained+local rows remain inaccessible. C3 verifies read-only Leave, callback loss and cleanup.++Late imported original-family rows remain closed/unresolved, without automatic+re-deletion or alteration of the external archive (3.5). Fresh-ID Private restore+remains independent. Scoped mapped-record absence can be displayed as observation;+store-wide export activity is not selected-family delivery proof. Universal tombstone+acknowledgment is not an enablement prerequisite: D9 permits pending/unknown cloud+status. Local graph, membership, cloud observation and ancillary cleanup stay+separate; no erased-offline-copy claim is made (D25).++### Signed environment binding++One explicitly approved setting drives the actual signed+`com.apple.developer.icloud-container-environment` and runtime `HaloCloudEnvironment`.+Map only Development/Production before namespace selection, consistently in host+and applicable extensions. Compare final distributed host/extension signatures,+Info declarations and profile permissions after archive/export/re-sign. DEBUG,+optimization and APNs do not identify the backend. Unknown/mismatched binding+withholds cloud confirmation; it does not authorize guessing, renaming or migrating+an existing account cache (D20).++The current retained physical package is `cd98717b`, installed 2026-10-12 20:57 UTC.+Canonical evidence and its install receipt record absent actual environment/runtime+declarations. The effective backend is unestablished; no fresh signature inspection+or backend access is claimed here. A separate configuration/signing approval must+name the intended environment and preserve existing data/identity. Disposable+cloud validation uses an explicitly authorized isolated environment and fixture+accounts, never this unknown live backend.  ## Interfaces and errors @@ -341,7 +372,10 @@ operations continue to fence participating local writers and draft setters. | `FamilyRemovalCoordinator.prepare/confirm/reconcile` | At most one operation per family; final preconditions immediately precede side effects; reconcile observes recorded outcomes and never replays unknown destruction. | | `FamilyOperationAccess.withWriteLease/checkReadable` | Shared cross-process admission checked at actual save/read boundary; other families remain admitted. | | `FamilyDraftRegistry` | Affected dirty drafts/generation across host windows; cannot declare confirmation eligible while unresolved. |-| `RemovalCloudDriver.leave/observe/revokeShare` | Explicit qualified targets and per-item outcome; mocked in automated domain tests. |+| `RemovalCloudDriver.leave/observe` | Explicit qualified targets and per-item outcome; mocked in automated domain tests. |+| `RemovalHostSessionPolicy.resolveAndAcquire` | Host persistence placement; runs before every production entry, holds stable library lease until process exit and checks the compatible installed protocol/epoch. |+| `RemovalIdentityCheckpoint.capture/validate` | Host persistence beside sharing; records public bounded identity metadata, invalidates associations and checks the full scope/authority conjunction before use. |+| `MaintenancePermissionProvider.refresh` | Host persistence beside AccessPermissions; supplies normal qualified readable/writable sets without non-cloud permission shortcuts or globally emptying Shared access. |  Pre-commit verification/cancellation leaves all source data unchanged and requires fresh review. Post-intent cancellation cannot promise rollback; outcome shows which@@ -349,40 +383,65 @@ steps are known. Account/permission/selection changes deny old-scope work. An in or unreadable ledger fails closed for its identifiable family and reports recovery needed; it cannot trigger a store reset or delete unrelated scopes. -## Testing strategy and enabling gates+## Bounded implementation and verification plan -| Requirements | Synthetic verification |-| --- | --- |-| 1.1–1.4, 4.1, 4.5 | Private/Shared same UUID, multiple families/default-zone mock, every model entity, cross-family corrupt links/orphans; only exact target rows removed, unrelated graph unchanged. |-| 2.1–2.5 | Chosen-file readback, corrupted/replaced ZIP, missing/truncated payload, bounded supplement, scratch-restore comparison, provider cancellation/revoked grant, 128 MB iOS/512 MB macOS limits; zero source writes on failure. |-| 3.1–3.4 | Pause verifier/driver deterministically; saved edit, new draft, local import, scope/account/role change and backgrounding invalidate confirmation and require re-export; final-action races respect the supported transaction gate; both cloud branches stay disabled while their fences are unresolved. |-| 3.5, 4.3–4.4, 5.1 | Partial cloud results, late imports, lost callback and generic export events remain pending/unknown; no false selected-family completion or implicit replay. |-| 4.2, 5.4 | Participant fake driver preserves owner graph; fresh-copy recovery remaps all graph/history/colour IDs, sharing stays absent, Contacts requires manual relink, original remains closed. |-| 5.2, 5.5–5.6 | Separate synthetic host/intent processes race save versus eligibility/commit; ledger-write/SQLite/callback crash points, startup denial before catalog exposure, stale reads rejected, other scopes remain usable. |--Use generated bounded graph examples in Swift Testing for ID remapping/round-trip,-family-only deletion invariants and reconciliation idempotence; fixed seeds retain-reproduction. UI tests use bounded synthetic stores for the exact review/export/-confirmation/outcome flow, large text and revoked-access states. Mock CloudKit-proves domain behavior only. Separately authorised disposable native two-account-acceptance is required before enabling cloud deletion/departure; there is no live-CloudKit fixture operation during design work.--Risk: document-provider scope/readback behavior differs by provider | Verify:-focused native Files/provider cancellation/relaunch tests before eligibility is-shipped | If wrong: block confirmation for that provider, preserve source.--Risk: Core Data/share metadata cleanup and late imports can outlive callbacks |-Verify: disposable owner/participant offline, callback-loss and relaunch acceptance-before cloud branch enablement | If wrong: retain closed pending state and keep-cloud branch disabled; no default-zone purge or silent retry fallback.--## Research references--- [Apple: synchronization scheduling](https://developer.apple.com/documentation/technotes/tn3163-understanding-the-synchronization-of-nspersistentcloudkitcontainer) and [debugging synchronization](https://developer.apple.com/documentation/technotes/tn3164-debugging-the-synchronization-of-nspersistentcloudkitcontainer): scheduled import/export, observational events and retained-container hazards.-- [Apple: coordinator queue execution](https://developer.apple.com/documentation/coredata/nspersistentstorecoordinator/performandwait(_:)-d3kq): queue/reentrancy contract, without multi-operation importer exclusion.-- [Apple: CloudKit environment](https://developer.apple.com/documentation/cloudkit/ckcontainer), [environment entitlement](https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.icloud-container-environment) and [checking distribution entitlements](https://developer.apple.com/library/archive/qa/qa1798/_index.html): actual signed binding and final-package inspection.-- [Apple: sharing Core Data objects](https://developer.apple.com/documentation/coredata/sharing-core-data-objects-between-icloud-users): framework sharing/participant cleanup and zone-wide purge boundaries.-- [Apple: CloudKit sharing management](https://developer.apple.com/documentation/cloudkit/shared-records) and [sharing Tech Talk](https://developer.apple.com/videos/play/tech-talks/10874/): owner/participant database distinction and departure without deleting the owner's records.-- [Apple: container export event](https://developer.apple.com/documentation/coredata/nspersistentcloudkitcontainer/eventtype/export): store export activity, not selected-family erasure evidence.-- Installed Xcode 27 `CKShare.h`, `NSPersistentStoreCoordinator.h` and `NSPersistentCloudKitContainer_Sharing.h`/`NSPersistentCloudKitContainer.h`; repository `BackupRepository`, `BackupHistory`, `PortableGraph`, `StoreAccess`, `LocalContactLinks` and model deletion rules.+This is a plan for approval, not authority to implement deletion or run fixtures.+Approve the technical design (including maintenance restart/sync delay) and the+offline implementation stage separately from cloud fixtures and environment binding.+No approved product default needs another decision.++| Stage / gate | Exact work and pass condition | Scope / failure outcome |+| --- | --- | --- |+| O1: export and scope | Add chosen-document readback/scratch round-trip, versioned supplement/complete identity map, budget/corruption/replacement tests. Same-UUID Private/Shared and multi-family fixtures preserve unrelated bytes. | Offline temporary SQLite/generated ZIP only. Failure leaves source unchanged and removal ineligible. |+| O2: local admission/commit | Add family/owner leases, draft setter admission, durable states and one explicit graph save. Deterministic barriers race editor, asset, restore and extension writes before comparison/commit; unrelated writes continue. | Offline separate helper processes. No code may rely on importer fencing for this stage. |+| O3: crash and recovery | Pause/terminate only owned synthetic helpers before/after intent/save/witness/cleanup. Same-store history witnesses committed IDs; missing witnesses do not replay. Re-select external file; fresh-ID restore remaps graph/history/colours/inactive links. | Offline both stores. No hidden payload, original reopening, native Contact mutation or unknown replay. |+| O4: identity/authority | Fake public mappings include unexported IDs, store replacement, share changes without graph history and multi-family shares. Read-only accepted participant may Leave; wrong account/database/zone and revoked access deny. | Offline injected CloudKit driver. Proves decisions, not Apple's native behavior. |+| O5: entry/process ownership | Audit every constructor/scene/background/invitation/host-Intent entry; simultaneous host starts, crashed owner and extension/version-skew fixtures test nonblocking leases. Package protocol/epoch and public running-host identity checks refuse entry until every other known host exits, including an old process whose on-disk bundle was replaced. | Offline synthetic store paths. Unregistered/legacy ownership uncertainty prevents maintenance enablement; no process kills or system setting changes. |+| C0: packaging | Verify final signed fixture package declarations, entitlement/profile permission, selected namespace and exact authorized container/account identities before opening fixture stores. | Separate signing/configuration approval. Missing binding aborts all cloud checks. |+| C1: no-import maintenance | In disposable two-account fixtures, queue normal import/export, end the owned prior host, launch plain maintenance, issue remote edits, and trigger every background/invitation/Intent entry. Local inventory/history must stay unchanged except admitted unrelated local writes. Include simultaneous Mac host and upgrade/retirement cases. | Separately authorized native cloud scope. Any unexpected imported transaction fails this construction; retain evidence and seek Apple clarification for that concrete failure. |+| C2: owner delivery | Save generated owned graph deletion through plain stack; retain history/metadata; end process; resume mirrored host. Verify mapped fixture records and co-parent graph, empty-share behavior, unrelated family and no application resubmission. Test late remote edits/conflicts and interrupted resume. | Native disposable records only. Success establishes exercised lifecycle; unresolved delivery remains pending. Failure blocks owner enablement, independently of participant Leave. |+| C3: participant Leave | Delete exact fixture CKShare in Shared for read-only and read-write participants; verify owner graph and unrelated shares unchanged. Exercise lost callback, offline owner, revoked membership and fresh normal cleanup. | Native disposable shares only. Callback loss stays unknown; retained local rows stay closed. Failure blocks Leave independently. |++The planned native case list is fixed: C1 queued-work restart, C1 all-entry wake-ups,+C1 competing/legacy host retirement, C2 owner history delivery/empty share,+C2 late owner edits/conflicts, C2 interrupted resumption, C3 read-only Leave,+C3 read-write Leave, C3 callback loss with offline owner, C3 revoked membership.+These are ten planned cases, not executed results.++Run O1–O5 as focused Swift Testing suites with deterministic generated fixtures and+one isolated source/output owner; use bounded generated graph round-trip/identity+properties rather than an added testing framework. Run required lint/platform gates+only after implementation. No execution count is claimed for these planned tests.++C1–C3 form one bounded acceptance campaign: one serial owner, one fixture ledger,+maximum ten native scenarios and one 60-minute slot. Each awaited cloud observation+has a five-minute deadline; expiration records pending/incomplete, never passes or+resubmits destruction. A demonstrated invariant violation is a failure; an+observation deadline is incomplete acceptance, and neither enables the branch. One focused rerun is permitted only after an identified+fixture/environment defect, preserving the first result. Use a fresh fixture and+operation, or a reconciled verified not-started state with renewed export/review;+an unknown destructive original is never resubmitted by that rerun. Otherwise stop with the+specific failed gate and do not broaden or repeat the campaign. Never delete a+default zone, reset a store, promote/delete schema or operate outside the exact+approved fixture ledger.++Separate cloud authorization must name the disposable container/environment,+preconfigured test accounts and devices, signed fixture identity, allowed generated+record/share create/update/delete operations and cleanup targets. It must explicitly+cover owner graph save/resumption and participant share departure. Installation,+account changes or schema work require their own authority if needed; none is implied.++### Verification risks with defined exits++- Risk: queued service work still mutates local stores after prior host exit | Verify: C1 before either cloud action | If wrong: disable maintenance cloud actions and submit the captured reproducible case to Apple.+- Risk: plain-save history is not exported as expected, or empty owner share blocks delivery | Verify: C2 | If wrong: keep owner action unavailable; no automatic share cleanup or replacement sync engine.+- Risk: legacy share association/version retirement cannot be established | Verify: O4/O5 and C1/C3 | If wrong: withhold only the affected cloud action/scope and require a new supported checkpoint or compatible installation.++## Primary contracts++- [TN3163: synchronization](https://developer.apple.com/documentation/technotes/tn3163-understanding-the-synchronization-of-nspersistentcloudkitcontainer)+- [TN3164: host/extension and retained-container lifecycle](https://developer.apple.com/documentation/technotes/tn3164-debugging-the-synchronization-of-nspersistentcloudkitcontainer)+- [Shared Records: participant departure](https://developer.apple.com/documentation/cloudkit/shared-records)+- [Core Data sharing sample: history/export and zone-wide purge](https://developer.apple.com/documentation/coredata/sharing-core-data-objects-between-icloud-users)+- [Public record IDs](https://developer.apple.com/documentation/coredata/nspersistentcloudkitcontainer/recordidsformanagedobjectids:), [known share lookup](https://developer.apple.com/documentation/coredata/nspersistentcloudkitcontainer/fetchsharesmatchingobjectids:error:), [fetched zone share association](https://developer.apple.com/documentation/cloudkit/ckrecordzone/share)+- [Signed CloudKit environment](https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.icloud-container-environment), [final distribution entitlements](https://developer.apple.com/library/archive/qa/qa1798/_index.html)
specs/delete-everything/requirements.md Modified +11 / -0
diff --git a/specs/delete-everything/requirements.md b/specs/delete-everything/requirements.mdindex f8ffaa4..727d620 100644--- a/specs/delete-everything/requirements.md+++ b/specs/delete-everything/requirements.md@@ -92,3 +92,14 @@ specify selected-document verification, unchanged-local-dataset checks, complete owned-graph removal, participant departure, affected-process admission and honest cloud evidence. The existing exporter establishes neither a multi-device snapshot nor remote erasure. Design approval remains separate from requirements approval.++## Technical interpretation — defaults unchanged++The approved clauses and D1–D9 are unchanged. Requirement 3.2 covers changes to the+locally available dataset and current available authority through the first action;+it does not promise a globally fresh snapshot or a distributed lock against later+server revocation. Requirement 4.2 permits an accepted read-only participant to+Leave after a readable verified export; graph write permission is not required.+Owner graph removal does not imply automatic CKShare deletion. Requirements 4.3+and 5.1 permit honest pending/unknown cloud status without universal per-target+tombstone acknowledgment. These clarifications do not authorize implementation.
specs/delete-everything/review.md Modified +85 / -4
diff --git a/specs/delete-everything/review.md b/specs/delete-everything/review.mdindex e15921c..4760368 100644--- a/specs/delete-everything/review.md+++ b/specs/delete-everything/review.md@@ -1,6 +1,6 @@ # Delete Everything — requirements review -**Status: requirements and defaults approved; reviewed design has a blocking technical dependency.**+**Status: requirements/defaults approved; staged technical design is ready for review/approval, with cloud enablement subject to concrete native gates.** No deletion implementation or live operation is authorised. Read the [requirements](requirements.md), [design](design.md) and [decision log](decision_log.md). @@ -131,7 +131,7 @@ Earlier `READ_TIMEOUT` responses and the **02:02 UTC** ten-second client timeout remain historical evidence. Backfill is now verified; this runner made no service restart, configuration change, build, deployment or family-data operation. -## Current design review — 2026-10-12+## Design review checkpoint — 2026-10-12  The critic ran first, followed by two independent peer perspectives: technical correctness and product/access/recovery. PERSONAL_PROJECTS=1 requests external@@ -156,7 +156,7 @@ unresolved and blocking. Final validator synthesis remains recorded separately below. This is a coherent design discussion with a technical blocker, not approved implementation or native feasibility proof. -## Explanation self-validation+## Explanation self-validation — 2026-10-12  Beginner: a parent selects one family, verifies one external file, then explicitly removes or leaves it. Unknown cloud outcomes keep the original closed; a selected@@ -176,7 +176,7 @@ require a revised public-API design, synthetic race/deadlock proof and independe native acceptance. The explanation identifies this as a load-bearing unresolved technical dependency, not an unapproved product default. -## Validator synthesis+## Validator synthesis — 2026-10-12  The independent technical and product peers rechecked the current document, including the nonblocking ownership rule. The validator finds no material@@ -249,3 +249,84 @@ Final validator recheck clears the updated text for continued technical discussi only, with no material divergence or remaining wording finding. Mapping/access, import exclusion and safe resume remain unresolved; signed artifact binding does not prove native acceptance. No additional product question is needed now.++## Independent recommendation reconciliation — 2026-10-13++The read-only independent T2444 recommendation at+`/Users/arjen/Documents/Codex/2026-10-13/task/halo-t2444-independent-recommendation.md`+was checked against the source, current Xcode 27 public headers and its fresh+Apple source captures. ADR-3/D22–D29 own current technical decisions; older reviews+above retain their dates and history, rather than remaining the active blocker list.+All approved requirement text and D1–D9 are retained. No source implementation,+store opening, test, cloud operation or signing/deployment change was performed.++| Recommendation / assumption | Current assessment and decision |+| --- | --- |+| One owner graph save, then normal framework mirroring | Adopted. Exact owned rows plus root, one same-store commit witness and retained history. No automatic owner CKShare deletion; share retention/cloud observation is separate. |+| Participant Leave through exact Shared CKShare, including read-only participants | Adopted. Readable verified export and accepted current membership suffice; graph edit permission is unnecessary. Never delete participant graph rows manually. |+| Public mapping checkpoints | Adopted as identity inputs, never authority. Exact root/entity/UUID/URI/store/record/zone.share/share/account/environment/database/role conjunction gates Shared actions. Missing non-root owner IDs limit observation. Undocumented plain-subclass lookup is not a dependency. |+| Per-family atomic import fence in normal mirroring | Still unavailable under 3.2; do not weaken the unchanged-local-dataset promise. Fresh plain process plus all participating entry-point/host ownership is the proposed construction. |+| Universal proof that no system service can ever mutate SQLite | Rejected as an additional blanket gate. Supported construction plus bounded C1 acceptance is the platform bar; an unexplained imported transaction fails the candidate and creates a concrete Apple question. This is an inference, not an Apple compare-and-delete guarantee. |+| Globally fresh snapshot, permanent server-permission lock, universal tombstone acknowledgment | Rejected as stronger than approved scope. Check current available authority; server outcomes remain separate. D7/D9 permit unavailable remote/offline edits and honest pending/unknown; those are not pre-enablement impossibilities. |+| Sole-family zone proof for all owner removal | Removed from owner row deletion. Exact one-family share provenance remains required for participant Leave; unknown/legacy multi-family scope is withheld. |+| Running-app version can identify a legacy Mac process | Corrected by technical peer. After in-place update the URL can expose new files while old code runs. Require every other identified host to exit, confirmed by termination state/notification; a marker or request return is insufficient. |+| Signed environment and safe resumption | Real prerequisites with specific exits. C0 inspects the final authorized fixture package; C2 verifies retained plain-save history delivery; C3 verifies membership and cleanup. Current `cd98717b` environment remains unestablished; no backend is guessed. |++The critic ran first. PERSONAL_PROJECTS=1 is set, but external Codex/Kiro callable+tools are unavailable, so the validator uses the documented two-independent-agent+fallback: technical correctness/edge cases and architecture/proportionality/access.+The critic accepts the construction/acceptance bar and asks for concrete compatibility,+authority, rerun and precedence rules; these are applied. The technical peer adds+the Mac loaded-image distinction above; the architecture peer supports the staged+plan and independent unrelated-family permissions. The critic and technical peer bounded rechecks clear the applied changes; the+architecture peer reports no material finding. Validator synthesis finds no+remaining material design issue. This clears the technical design for approval,+not native feasibility or implementation authority.++### Explanation self-validation — current design++Beginner: save and verify one chosen external file before removing one family.+The owner removes its graph; a participant leaves its share, including if read-only.+Cloud status can remain pending, and an explicit restore creates a new private+family. The proposed cloud workflow restarts into a mode that temporarily delays+sync, so that workflow still needs design approval and native acceptance.++Intermediate: the offline foundation adds byte verification, qualified admission,+draft control, one graph save, durable outcomes and full fresh-ID remapping. Public+checkpoint metadata identifies CloudKit targets; network checks supply current+authority. Original eligibility is never carried through a restart. Owner graph+commit and participant share submission have different witnesses and outcomes.++Expert: importer exclusion is a composed fresh-process/plain-container/participating-+host ownership design, not a queue or optimistic-lock theorem. C1 exercises queued+work, entry points and legacy retirement before either cloud action. C2 tests known+history delivery; C3 tests exact membership departure and callback-loss recovery.+Unknown originals remain closed, with no application replay. No raw framework+metadata edits, hidden payload copy or global-snapshot promise is introduced.++### Bounded plan and approval boundary++[Design](design.md#bounded-implementation-and-verification-plan) names O1–O5 offline+work and C0–C3 native enablement, with ten fixed native cases, one 60-minute serial+campaign and five-minute observation deadlines. Invariant violation is failure;+expected pending behavior is asserted as pending; observation timeout is incomplete+acceptance. No timeout or lost callback becomes success or destructive resubmission.+One permitted defect-correction rerun preserves the original result and uses fresh+fixtures/operation or verified not-started state plus new review/export.++Approval needed next: revised technical design, including fresh-process/both-store+sync delay, and offline implementation using temporary generated stores/accounts.+Native CloudKit authorization is separate and must name exact disposable container/+environment, preconfigured accounts/devices, signed fixture identity and allowed+generated record/share operations. Current app signing/runtime environment binding+needs separate authority that preserves existing identity/data; installations,+account changes or schema operations are never implied. No approved product default+needs another answer. This specification update authorizes none of those actions.++### Primary source links++- [Apple Shared Records](https://developer.apple.com/documentation/cloudkit/shared-records): exact participant share departure.+- [Core Data sharing sample](https://developer.apple.com/documentation/coredata/sharing-core-data-objects-between-icloud-users): graph/share scope, history-based delivery and distinct share changes.+- [Public record mappings](https://developer.apple.com/documentation/coredata/nspersistentcloudkitcontainer/recordidsformanagedobjectids:), [known shares](https://developer.apple.com/documentation/coredata/nspersistentcloudkitcontainer/fetchsharesmatchingobjectids:error:), [fetched zone share reference](https://developer.apple.com/documentation/cloudkit/ckrecordzone/share): bounded identity inputs.+- [TN3163](https://developer.apple.com/documentation/technotes/tn3163-understanding-the-synchronization-of-nspersistentcloudkitcontainer), [TN3164](https://developer.apple.com/documentation/technotes/tn3164-debugging-the-synchronization-of-nspersistentcloudkitcontainer): asynchronous synchronization and host ownership/lifecycle.+- [NSRunningApplication bundleURL](https://developer.apple.com/documentation/appkit/nsrunningapplication/bundleurl), [termination state](https://developer.apple.com/documentation/appkit/nsrunningapplication/isterminated): identify another host and observe exit, without inferring its loaded build.
specs/direction-f-redesign/implementation.md Modified +2 / -2
diff --git a/specs/direction-f-redesign/implementation.md b/specs/direction-f-redesign/implementation.mdindex 4df44a0..527c49f 100644--- a/specs/direction-f-redesign/implementation.md+++ b/specs/direction-f-redesign/implementation.md@@ -148,8 +148,8 @@ Both owned simulators are Shutdown and heavy work is released at 16:14:47 UTC. - Separate acceptance: actual audio/permission/models/hardware/recognition, Mac native   input UI, manual accessibility, live account/KVS/share/CloudKit and native extensions.   The phone retains optimized Release `cd98717b`; current input/action source is not installed.-- Design-only: selected-family removal remains blocked on its supported import boundary-  and signed-environment prerequisite. Onboarding/child colour and inline context+- Design-only: selected-family removal has a reviewed staged design for approval; cloud+  enablement awaits explicit environment binding and bounded native C1–C3 gates. Onboarding/child colour and inline context   creation (Idea T2448) are separately scoped; no deletion or future feature is added.  The three-level explanation exposes no new source divergence. It preserves the

Things to double-check

Planned gates are not executed tests

Only Markdown validation, requirement-byte preservation, relative links and independent source reviews were checked. No builds/tests, cloud calls, store opens or deployment occurred. C0–C3 cannot be represented as passed.

Exact future approval

Approve revised technical design/restart/sync-delay and offline implementation separately from disposable cloud fixtures. Cloud authorization must name exact container/environment, accounts/devices, fixture identity and allowed operations; signing/install/account/schema authority is not implied. D1–D9 need no new answer.

Library publication blocker

The existing Library identities and version guards are resolved. Automatic approval review rejected replacing the three remote specifications because it did not recognize destination/replacement authority. No remote Library write occurred; a specific approval request is pending. Repository work is complete.