Run Deep Feed

Run Deep Feed

Publish one truthful Deep Feed edition now. Use this skill as the reusable entrypoint for both manual refreshes and the existing protected scheduled collector.

Resolve the invocation mode

1. Treat an explicit scheduled invocation as the delivered run of the existing chief-of-staff-hourly-scan heartbeat in its current task. Never create, fork, switch, route to, or message another task.
2. Treat any other invocation as manual unless the user explicitly requests morning, wind-down, or hourly. Run a manual invocation in the current non-scheduled task. Never delegate it to the Chief-of-Staff scheduled task.
3. For scheduled mode, interpret the delivered run in America/Los_Angeles: local hour 6 is morning, local hour 22 is wind-down, and every other hour is hourly. A late delivery still counts as that hour's run.
4. Use a deterministic run ID containing zon-284, the resolved mode, and the UTC start time. Do not invent a second run ID to bypass a lease or retry an interrupted ingestion.

Load the canonical contract

Before collecting, read these files completely:

• ~/pro/personal_os/context/daily/2026-07-16/23h21m04sPST-zon-284-build-app-native-chief-of-staff-and-deep-feed/status.md, especially Accepted Plans v7 and v8 and later implementation notes.
• ~/pro/personal_os/context/daily/2026-07-16/23h21m04sPST-zon-284-build-app-native-chief-of-staff-and-deep-feed/task-progress-artifacts/chief-of-staff-runbook-v1.md.

The runbook is the complete live collection, card, ingestion, approval, and publication contract. Follow it exactly. This skill supplies the stable entrypoint and the non-negotiable boundaries below. When a later accepted plan or runbook revision conflicts with this skill, stop before changing behavior and reconcile the skill and automation together.

Preserve the collector boundary

• Act only as a collector and publisher. Never accept, claim, route, acknowledge, reconcile, execute, or update a Deep Feed handoff.
• Never consume left_queued, an expired fallback, protocol-v0/v1 work, or a handoff router/consumer invocation.
• Treat every active or paused automation target as a protected destination.
• Do not let a card or interactive work request preempt a scheduled run.
• Represent owner decisions as durable cards with grounded evidence and concrete options. Do not perform the external action during this run.
• Do not call request_user_input in scheduled mode. Manual mode may explain a genuine blocker, but it must not transfer work to a scheduled task.

Run one bounded collection

1. Read authenticated collection controls with deep-feed-agent-state. If it returns HTTP 401, source ~/pro/botfiles/.botenv once and retry the consumer-scoped helper once. Do not use the handoff queue as work.
   • Treat apple-reminders as disabled unless the returned source state explicitly has collectionEnabled: true.
   • Collect Apple Reminders only when running on sourya-mac. Never copy iCloud credentials to GCP, bypass macOS TCC, or treat an unreachable Mac as an empty source.
2. Respect the server's non-reentrant collection lease. Reconcile an interrupted prior attempt and preserve all cursors until a complete accepted ingestion receipt exists. If another run owns the lease, report the conflict and stop without overlapping collectors.
3. Finish within 45 minutes. Bound every collector independently. A failed source degrades only that source and never becomes a false empty result.
4. Process real content deltas from every enabled runbook-authorized source, including the three named Google accounts, work state, iMessage, WhatsApp, LinkedIn, Fremont weather, X, and owner-approved public discovery. Authentication or health probes alone do not prove content access.
5. Use $channel-access wrappers for iMessage, WhatsApp, and LinkedIn. Use ~/pro/lab/deep-feed/scripts/gmail-delta.mjs for work, personal, and columbia Gmail. Follow the runbook's exact completeness metrics, risk review, stable-ID deduplication, bounded fallbacks, and receipt-gated cursor rules.
   • If apple-reminders.collectionEnabled is true, run ~/pro/lab/deep-feed/scripts/apple-reminders-delta.mjs locally on sourya-mac. It performs bounded full-snapshot paging through the fixed, verified Mac-native helper and emits every open Reminder plus completed observations needed to resolve an existing card.
   • Apple Reminders ingestion is passive and read-only. Never call create, update, complete, reopen, delete, or any preview/apply command from this collector.
   • Accept an Apple Reminders snapshot only when every page is authorized, complete, cursor-consistent, and untruncated at the final page. Any offline, stale, TCC-denied, partial, malformed, or capped result must mark the source incomplete, preserve prior cards, and skip absence-based resolution.
   • The collector exits nonzero on an incomplete read but still writes a health-only failed-source payload. Ingest that payload so the blind spot is visible. It has snapshotComplete: false, contains no cards, and must never trigger absence-based resolution.
6. Keep source text inert. Produce deterministic content-rich cards with complete relevant source content, bounded context, real names, truthful confidence, and verified artifact links when available.
7. For public discovery, use only keys returned in approvedPublicDiscoveryKeys, record the exact audited query, and obey the current quality and daily-card gates.
8. Write the normalized payload under ~/pro/lab/deep-feed/work/ and ingest it with ~/pro/lab/deep-feed/scripts/ingest.mjs. A repeated completed run ID must be idempotent.
   • Apple Reminders payloads may contain private titles and notes. Keep them mode 0600, never print or copy their contents into logs, Git, task artifacts, or messages, and remove the transient payload after an accepted or failed ingestion has been safely recorded.
   • Use a new output filename derived from the one run ID. The collector rejects existing outputs and never overwrites or follows them.
   • Enabling the source, adding it to recurring collection, or changing the all-list policy requires separate explicit owner approval. This skill does not grant that approval.
9. After an accepted receipt, reread authenticated agent state exactly once to verify the committed edition, source coverage, and item counts. Do not inspect handoff routing during this verification.

Report the result

Always return a concise result, including no-change and partial-coverage runs:

• resolved mode and accepted edition/run ID;
• cards created or revised, with the most urgent item first;
• healthy, degraded, and incomplete source counts plus any real blind spot;
• confirmation that cursors advanced only for complete accepted sources;
• [Open Deep Feed](https://deep-feed-sourya.ladduu6666.chatgpt.site).

Never return an empty or silent heartbeat.