Project Suite Overview

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

• Likely current work: Post-release follow-through on the Aurora and Platinum public family, including lane trust, Galaxy Guardians readiness, and cleaner platform-versus-application seams.
• Next step: Do a quick Aurora release-lane status refresh before any shared-public publish so the manifest and the active release lane stay aligned.
• Quality: This is the strongest product-style public surface in the suite, so small inconsistencies are disproportionately expensive.
• Coordination note: Best handled as protect-and-verify work rather than broad redesign.

Confidential client-facing portal and product work summarized here only at a high level.

• Likely current work: Private rental-portal delivery and related product execution.
• Next step: Keep the public summary minimal and accurate; do not expand the public surface unless there is a deliberate client-safe artifact to add.
• Quality: The public/private boundary is already clear, which is the main quality goal here.
• Coordination note: Track only high-level continuity in public.

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

• Likely current work: Ongoing corpus expansion, stronger discovery lanes, and continued approval-quality curation rather than platform work.
• Next step: Keep adding high-quality approved entries in batches and refresh the public export whenever the approved corpus meaningfully grows.
• Quality: The public page already reads cleanly and feels complete enough to trust; the main question is breadth and selection quality.
• Coordination note: A good example of a healthy incremental export loop.
• Evidence status: Approved corpus: 32 entries.

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

• Likely current work: Disciplined intake, continuity hardening, and bounded 1.x cleanup around the stable 1.0.0 baseline.
• Next step: Continue intake and warning cleanup without destabilizing the verified baseline, then refresh the handbook and dashboard only when the supported story changes materially.
• Quality: One of the most mature documentation and validation surfaces in the suite.
• Coordination note: Good candidate for steady, bounded progress rather than urgent intervention.

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

• Likely current work: Portability hardening, handoff clarity, and careful continuation from the 1.0.0-rc.1 restoration baseline.
• Next step: Keep the release-candidate surface trustworthy, then only widen into deeper benchmark or hosted-runner work once the portability story is comfortably stable.
• Quality: Strong research-restoration presentation with clear public framing; still benefits from discipline more than expansion.
• Coordination note: Treat the hosted runner as mechanism, not the project identity.

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: Preserve the remaining URL-backed baseline pages and reconcile the review-ledger-only captures that should become formal source records.
• Quality: One of the best organized archive areas, with clear role boundaries and strong continuity surfaces.
• 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: A strong archive workflow is in place, but evidence completeness still matters more than polish.
• Coordination note: Treat the bridge record as compatibility, not as a second canonical home.

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: A pushed Kinitos branch has finished the approved-source preservation floor and added private-evidence derivative notes, even though the public line still understates that progress.
• Next step: Promote the preservation-complete Kinitos branch, then shift into deferred-source and public-corroboration follow-up instead of more blocked-press preservation.
• Quality: One of the strongest deep archives in the suite after Steven and Quack, with clear continuity discipline.
• Coordination note: The right sequence is promote the preservation-complete branch first, then reopen broader research through deferred and corroboration campaigns.
• Evidence status: Evidence baseline: 24 approved / 8 deferred / 0 rejected (32 total).