ConCOREdance

Harmony in Complexity

Apple Passwords Access from the Vault Entrance

Cody Valle -> Brandon Hatfield, LPC and the ConCOREdance project team

An explicit vault-screen button opens Apple Passwords. Biometric and passkey decryption remain proposed work, with no credential enrollment performed.

CC-TX-2026-10-28-005|2026-10-28|Active Canon|Native macOS / Vault Entrance
TX

Transmission Record

ID CC-TX-2026-10-28-005
Status Active Canon
Type Implementation and Authentication Design Log
Layer Native macOS / Vault Entrance
From Cody Valle
To Brandon Hatfield, LPC and the ConCOREdance project team
Authorized By Brandon Hatfield, LPC

Apple Passwords Access from the Vault Entrance

The vault entrance now offers an explicit Open Passwords action. It resolves Apple Passwords by its bundle identifier and asks macOS to open the application. A missing application or launch error leaves manual vault-password entry available and produces an actionable message. This launcher does not read credentials, save a password, select a saved entry, autofill the field or unlock the vault. No credential registration or biometric enrollment was performed.

The native development build and ad hoc bundle verification passed. The new button was inspected on the synthetic vault entrance and used to open Apple Passwords. The credential-selection and filling flow remains user-operated. No clinical data or real password was used. The full XCTest suite was not rerun for this launcher-only change.

The private source branch beta/clinical-preview-2026-10-28 now identifies commit f90fe379e14d84c900408afb6c6edb606bb82ce4. This supersedes the previous source pointer while retaining its visual implementation and clinical-beta limits.

Touch ID vault unlock is proposed as explicit per-device enrollment after successful password unlock, with macOS Keychain access control enforcing biometric access to a vault-specific secret and password recovery retained. The existing biometric prompt helper alone is not a cryptographic unlock implementation. Durable signing identity, key/recovery design, cancellation, biometric enrollment changes, device loss and failure behavior must be addressed and tested before this is enabled. Passkey registration is a separate authentication/key-management design and has not been implemented. The app remains a synthetic-data development preview with the earlier clinical beta gates open.

Decisions

  • Provide explicit access to Apple Passwords without reading or saving credentials.
  • Keep biometric key access and recovery design separate from a prompt-only UI.

Next Actions

  • Design and test explicit Touch ID enrollment with Keychain-enforced secret access.
  • Continue the existing clinical beta release gates.
vaultApple PasswordsTouch ID proposalverification limits