# Repository handoffs, one at a time

This is the durable coordination queue, not an instruction to run all projects
at once. Keep one handoff active; record its reply and verification here before
opening the next. Project-owned releases and confidential boundaries take priority
over making the dashboard appear newly updated.

| Order | Project | State / bounded outcome |
| --- | --- | --- |
| Activity priority | AI Briefing | Ready to send: owner-approved daily working report and classified upkeep. Prompt below; existing release export remains unchanged. |
| 1 | AI Dystopia Quotes | Ready to send: review the one source/export difference, deliberately publish only if approved, add shared freshness support. Prompt below. |
| 2 | Windigo Portfolio Portal | Awaiting handoff: establish sanitized export for existing `confidential-project` identity, verify active branch/runtime/release privately. |
| 3 | Financial Planner | Awaiting handoff: owner-reviewed sanitized export; confirm active runtime and release policy without exporting planning data. |
| 4 | Woods Financial Dashboard | Awaiting handoff: sanitized export and private discrepancy/runtime review; keep separate from the other two applications. |

AI Briefing's release export and Star Swarm's deployment notification were verified
in the October 22 audit. AI Briefing now needs the separate working-activity export,
not another release-export repair. Aurora is managed on another machine: its
working-history report follows AI Briefing, without changing its release lane.
Star Swarm's separate working report follows that, measured from Star Swarm's
actual working history. Firstmate is the development platform used to build it,
not a separate source-report handoff. Never combine Star Swarm and Aurora work.
MMath and PhD
freshness-template improvements can be considered after the active queue; their
source identities matched during the audit. Archive research gaps are already in
the portfolio overview and are not another cross-repository setup campaign.

If the previously supplied Quotes prompt is already running, verify that reply
first; do not start two source handoffs concurrently. Its numbered section below
is intentionally unchanged so existing forwarded prompts stay valid. Otherwise
the next newly requested handoff is AI Briefing working activity.

## AI Briefing working activity: prompt to send

```text
Add a privacy-safe working-activity export for AI Briefing, without changing your
released status or existing two-file release export.

Read your repository instructions, privacy rules, current work state, and these
hub documents first:
https://github.com/sgwoods/public/blob/main/WORKING-ACTIVITY-INTERFACE.md
https://github.com/sgwoods/public/blob/main/PROJECT-STATUS-CONTRACT.md
https://github.com/sgwoods/public/blob/main/data/activity/ai-briefing.json

The public code mirror has eight October 22 commits, while the October 22 private
working-history audit found 391 commits across October 5-22. The hub has published
only daily Toronto-date aggregates, all unclassified, as an assisted baseline.
That is not proof of automatic upkeep or 391 code changes. Recheck the source.

In your own project, implement a reviewed exporter for ONLY
data/activity/ai-briefing.json in sgwoods/public. Keep its measurement separate
from ./np hub push's released-status manifest/page contract. Working reports may
publish at a daily or deliberate work checkpoint without releasing anything.

Pin the chosen working source head(s), read all history pages/commits in the
reported window, deduplicate, and bucket committer dates in America/Toronto.
Classify each measured commit once as development, publication, automation,
or unclassified under a documented private policy. Leave ambiguous work
unclassified; do not treat every private commit or backup as code development.
Use owner-approved-export only after approval. Include honest coverage and
check/generation times; missing or failed history must not become zero.

Export no private hashes, messages, authors, branch names, filenames, repository
or deployment URLs, raw histories, financial/editorial/subscriber data, or secrets.
Keep classification evidence private. Review the exact staged JSON and allowlist.
Use the hub validator and tests; add source tests for deduplication, categories,
timezone boundaries, unknowns, failed checks, and private-data exclusion.

Use the existing approved cross-repository credential, enforcing a one-path
allowlist; do not expand the public hub token's access to private repositories.
Authenticated activity-report pushes trigger the hub renderer, which explicitly
requests Pages. Verify the live #working-activity view and unchanged release facts.
Do not edit hub index/notes, other projects, or release labels for this work.

Report source/hub commits, tests, counts by category, scope, approval, the actual
upkeep mechanism/cadence, live verification, and any remaining gates. If approval
or reliable classification is missing, explain the gate rather than inventing it.
```

## 1. AI Dystopia Quotes: prompt to send

```text
Please review and, only if approved, reconcile your public export with the portfolio hub.
Read your repository instructions, publication/review rules, working-tree state,
and release authority first. Preserve unrelated work and the private/public boundary.

The October 22 hub audit found the approved export still represents
3cbaf56f1f4aa31d01b536e747f25bbdd8c83b5c, while public main has
a0e7cc899512bdb0c3973903851387f993387b99 (cached artwork, work links,
and editorial changes). Recheck these identities; they may have advanced.
Decide whether the newer batch is actually approved for publication.
If not, retain the existing release facts and explain the remaining gate.

Read these hub interfaces before changing the exporter:
https://github.com/sgwoods/public/blob/main/PUBLIC_STATUS_INTERFACE.md
https://github.com/sgwoods/public/blob/main/PROJECT-STATUS-CONTRACT.md
https://github.com/sgwoods/public/blob/main/assets/project-freshness.js

If approved, run supported validation and export the complete approved outputs:
manifest, HTML, approved corpus, and required local artwork assets. Do not merely
advance dates or a SHA while leaving the corresponding page/data/assets behind.
Do not publish pending review material or private working records.
Record the real released clean public source commit, its committer time/ref,
and the actual export time; fail clearly if the source identity cannot be resolved.

Add the hub's shared freshness widget to the exporter-owned page template,
using the contract's exact integration and project id ai-dystopia-quotes.
Keep CSS at assets/public-site.css and the established shell/hero/panel structure.
Update your exporter, not only its generated copy, so the integration survives.

Publish only your approved allowlisted files to sgwoods/public. Do not modify
the hub index, portfolio judgments, observations, or other projects. An authenticated
export push triggers the hub workflow; if necessary use the supported post-export
notification only after publication. Verify the hub workflow and explicit Pages
build, approved corpus/artwork links, source comparison, and rendered check time.
Report source and hub commits, tests, publication result, remaining gates, and
anything requiring a hub-owned change. Do not call unapproved work released.
```

## Completion record

No source-repository handoff has been completed as part of this queue yet.
Next newly requested action: send the AI Briefing working-activity prompt unless
the Quotes handoff is already running, then bring the reply back for verification.
No source exporter has been installed by this hub-only implementation. Do not
mark a handoff complete on a prompt, a baseline, or a successful hub render alone.