Project Suite Overview

Public project page synced from its published repository or archive status manifest.

• Likely current work: Public main at 148f82e (October 15) records a beta dry-run pass and music acceptance hold. The live production build-info.json still identifies Aurora 1.4.1 build 1164, source 54398ff5, from June 11; the older exported production date is accurate.
• Next step: On the active machine, review the full working history and prepare an approved daily aggregate report under WORKING-ACTIVITY-INTERFACE.md after the AI Briefing setup. Keep production source metadata tied to the released build; this does not authorize promotion or change release ownership.
• Quality: This is the strongest product-style public surface in the suite, so small inconsistencies are disproportionately expensive.
• Coordination note: High-value continuity task: preserve and review current local work before starting another gameplay or publication batch.

A playable arcade-style formation shooter with data-driven packs and a prompt-assisted content forge, developed with Claude and Firstmate.

• Likely current work: Independent Star Swarm game/content-platform development using Claude and Firstmate, as a parallel comparative attempt entirely separate from Aurora. October 22 deployment, notification, and hub import identify clean build 65d1434; source-owned docs remain authoritative for tested features.
• Next step: Follow the source roadmap: configurable pack/stage editing and playability validation, broader lab previews, and art/audio provenance review. Choose one bounded batch; do not treat roadmap items as shipped.
• Quality: State documentation is checked by tests, and deployment is gated by CI. This audit verified build identity and CI, not exhaustive gameplay quality.
• Coordination note: Firstmate names the development platform used to build Star Swarm, not another project to measure. Attribute Star Swarm's working report to star-swarm, never Firstmate's own repository or agent-state backups. Keep Aurora's code, activity, releases, and roadmap separate. Agent-neutral deployed-build imports and the verified post-deployment notification remain unchanged.

Private property-owner portal for financial review, booking reconciliation, and evidence-backed operations.

• Likely current work: Owner-facing reconciliation, evidence review, and property operations. These are scope observations, not a verified release or current runtime assessment.
• Next step: On the owning machine, review the active work lane and establish a sanitized status export under PRIVATE-PROJECT-STATUS.md. Verify a real release before naming it publicly.
• Quality: Public boundary is explicit. Application correctness and deployment were not tested in this metadata review.
• Coordination note: Private code and data remain fully private. Only approved descriptions, aggregate commit activity, and verified release metadata may be exported.

Private financial-planning application with explicit assumptions, source provenance, and review workflows.

• Likely current work: Financial planning with explicit assumptions, source provenance, and review workflows. Current execution and release readiness need owner confirmation.
• Next step: Establish a sanitized owner-approved status export; validate the active runtime, tests, and release policy privately before publishing a release label.
• Quality: High-level documentation describes structured planning and auditability. This hub review did not validate calculations or financial advice.
• Coordination note: Separate from Woods Financial Dashboard and Windigo. Keep all implementation and planning data private.

Private local-first personal-finance dashboard for source-backed financial review and reconciliation.

• Likely current work: Local-first source-faithful financial review and reconciliation; the current work lane needs owner confirmation.
• Next step: Review the discrepancy ledger privately, confirm the active runtime, and establish a sanitized owner-approved status export without publishing financial records.
• Quality: This is a distinct personal-finance dashboard, not the rental portal. The hub has not validated its calculations or current data.
• Coordination note: Keep source documents, balances, model details, code, and deployment addresses private. Publish approved aggregates only.

Public project page for a curated corpus of recognizable dystopian AI quotations and source metadata.

• Likely current work: Public main a0e7cc8 (October 4) adds cached artwork, work links, and editorial updates. The hub still represents the approved October 3 export from 3cbaf56; one source commit is ahead of the public export.
• Next step: Have the owning project review a0e7cc8 and deliberately publish its approved JSON, page, and local artwork assets through its exporter. Do not update the manifest alone to imply those outputs were deployed.
• Quality: The public page already reads cleanly and feels complete enough to trust; the main question is breadth and selection quality.
• Coordination note: Source metadata reconciled. Measure future curation value by approved additions rather than scan count.
• Evidence status: Approved corpus: 32 entries.

A daily AI briefing, newsletter and podcast for early-stage investors: what happened, what holds up, and what it means, with occasional deep dives.

• Likely current work: Beta publication, reader feedback, and development/release workflow improvements. The verified hub export is v0.1.4-beta, public source e701aaca, with the October 22 edition and deep dive.
• Next step: Implement the separate approved daily working-activity report using REPOSITORY-HANDOFFS.md. Classify the private working history without exposing it, preserving the existing two-file release export and release facts. Then prioritize editorial accuracy and bounded reader feedback.
• Quality: The 19-field export, public tag, canonical page, links, and freshness panel are verified. This audit did not validate editorial accuracy, email delivery, or audio quality.
• Coordination note: Release exports own data/projects/ai-briefing.json and ai-briefing.html. The new independent working report may own only data/activity/ai-briefing.json. Source-owned upkeep remains to be installed; daily public checks cannot refresh private working activity. Keep operational and subscriber data private.

Public project page synced from its published repository or archive status manifest.

• Likely current work: Exporter metadata now uses the source commit and real export time. A new --status-only mode refreshes public status without rebuilding thesis artifacts; the release remains 1.0.0.
• Next step: Review the three pre-existing remote migration/reporting documentation commits separately, then continue intake triage.
• Quality: One of the most mature documentation and validation surfaces in the suite.
• Coordination note: Metadata fix published; the remote documentation branch remains a separate integration task.

Public project page synced from its published repository or archive status manifest.

• Likely current work: Exporter provenance and public runner-link reconciliation completed October 3. The exported release remains 1.0.0-rc.1.
• Next step: Continue bounded portability or benchmark work; use the updated exporter for subsequent factual status changes.
• Quality: Strong research-restoration presentation with clear public framing; still benefits from discipline more than expansion.
• Coordination note: Small publication gap closed; defer broader benchmark expansion until deliberately prioritized.

Deep research archive for Steven Woods' talks, interviews, profiles, awards, and cross-company public record.

• Likely current work: Person-centric continuity work, baseline identity tightening, profile preservation, and keeping the source-manifest and review-ledger split deliberate.
• Next step: Use the content inventory to recover prior private transcripts, review existing first-person Q&A and resolve source identity/edition gaps. Keep LinkedIn exports and unreviewed transcripts in a private working repo; public copies need explicit approval.
• Quality: Clear role boundaries and continuity surfaces; 21 of 22 approved records now have local artifacts. New Inovia and bio.link copies are explicit public-browser transcriptions, not original page dumps.
• Coordination note: Use this as the canonical person-centric layer, not a dumping ground for company-depth material.
• Evidence status: Evidence baseline: 22 approved / 0 deferred / 0 rejected (22 total).

Research archive for Steven Woods' Google Canada period, covering leadership, Waterloo engineering growth, talks, interviews, and Canadian media coverage.

• Likely current work: Now that the seeded baseline is public, deepen interview, media, and transition coverage in small, high-signal batches.
• Next step: Add one more interview or ecosystem source batch, then tighten the public summary only if the center of gravity changes materially.
• Quality: Now has a seeded, continuity-safe public baseline with room for deeper source density.
• Coordination note: Good candidate for steady, source-batch progress rather than another structural pass.
• Evidence status: Evidence baseline: 9 approved / 0 deferred / 0 rejected (9 total).

Research archive for Steven Woods' Inovia period, covering leadership, talks, public appearances, and ecosystem-facing material.

• Likely current work: Seeded-baseline maintenance plus current-role, team-profile, and ecosystem appearance capture.
• Next step: Localize the current team profile and add one more public-appearance or ecosystem source batch.
• Quality: The continuity structure is in place; the main gap now is source depth rather than project setup.
• Coordination note: Best advanced through small, explicit source batches.
• Evidence status: Evidence baseline: 3 approved / 0 deferred / 0 rejected (3 total).

Research archive for Steven Woods' Canberra period, combining CSIRO work, Canberra life, and hockey with the Canberra Knights.

• Likely current work: Still mostly a scaffold, with the core value in establishing a first honest source baseline rather than broad research.
• Next step: Seed the first CSIRO, Canberra Knights, and local-context sources so the archive has a real evidence floor.
• Quality: Clear structure exists, but there is not yet enough source depth to treat it as active archive work in the same way as the stronger projects.
• Coordination note: Good candidate for a small, bounded seeding pass rather than a big research campaign.
• Evidence status: Evidence baseline: no formal source records yet.

Research archive for Steven Woods' Software Engineering Institute period in Pittsburgh, covering publications, institute context, and startup-transition material.

• Likely current work: Seeded-baseline maintenance plus additional staff, paper, and startup-transition context around the SEI-to-Quack bridge.
• Next step: Add one more staff or transition-context batch, then refresh the summary only when the bridge story materially improves.
• Quality: Strong continuity and evidence progress, with a published baseline that now supports steady deepening.
• Coordination note: Good steady research lane now that the scaffold phase is over.
• Evidence status: Evidence baseline: 12 approved / 0 deferred / 0 rejected (12 total).

Collection of memories, demos, artifacts, press, and recovered code from the Quack.com era.

• Likely current work: Preservation and source-completeness work around AOL by Phone, investor outcomes, first-party capture gaps, and stronger preserved press.
• Next step: Keep working campaign-by-campaign, preserving fragile or first-party evidence before widening the editorial surface.
• Quality: All 6 approved records now have local content captures, with 8 local paths across all 20 records; 14 deferred leads still need evidence work. The approved-copy page metric is calculated rather than hard-coded.
• Coordination note: Treat the bridge record as compatibility, not as a second canonical home.
• Evidence status: Evidence baseline: 6 approved / 14 deferred / 0 rejected (20 total).

Canonical deep archive inside the shared public repo for the Kinitos origin story and the later NeoEdge Networks era, covering documents, demos, artifacts, and recovered code.

• Likely current work: The preservation branch has been integrated in 993055e after reviewing its derivatives and removing private log filenames from the public lead note. All 24 approved records have existing local artifacts.
• Next step: Resume deferred-source and public-corroboration research in bounded batches; raw private logs remain outside the repository.
• Quality: One of the strongest deep archives in the suite after Steven and Quack, with clear continuity discipline.
• Coordination note: Publication backlog closed; pursue source depth next, rather than repeating preservation setup.
• Evidence status: Evidence baseline: 24 approved / 8 deferred / 0 rejected (32 total).