pastilhasandClaude Fable 5
6071ded175
TODO.md had reached 1050 lines and 72 open items across 28 sections, read mostly on a phone. It is now a directory: todo/<theme>/<item>.md, one card per file, with frontmatter carrying id, status, created date and order, and the prose body copied across verbatim. TODO.md becomes a generated index (bun run todo:index). Dates: where an item's prose stated one it is used; otherwise its old section's; otherwise 2026-08-20, floored at the day before the split rather than invented. date_source records which. Shaped for a two-way Kanban board, filed as todo/tooling — a card is a file, id is the identity, frontmatter is the machine's half and the body is the owner's. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
---
|
|
id: mobile-apps/iphone-action-button-run-an-officer-task-from
|
|
title: "iPhone Action Button → run an Officer task from a locked phone"
|
|
theme: mobile-apps
|
|
status: open
|
|
created: 2026-08-21
|
|
date_source: stated
|
|
order: 1
|
|
---
|
|
|
|
**iPhone Action Button → run an Officer task from a locked phone.** Wanted 2026-08-21. The
|
|
driving use case: an idea arrives, press the Action Button, an audio recorder opens immediately —
|
|
even on the lock screen — and the recording goes straight into an Officer chat session, without
|
|
unlocking, opening the app and navigating there.
|
|
Shape (assumed, not verified): the Action Button runs a Shortcut, and a Shortcut runs an App
|
|
Intent the Officer app exports — so the work is shipping App Intents ("record to chat", and
|
|
task-running more generally). **The load-bearing unknown is the lock-screen constraint**: what an
|
|
App Intent may do while the phone is locked (microphone access, network, whether iOS forces an
|
|
unlock prompt) decides whether this is the feature as imagined or a compromise. Settle that
|
|
first, on a real device.
|