What kinds of WorkWingman exist? (plain English)¶
WorkWingman is not one single “build” that everyone gets the same way. There are a few different ways to run or read it, chosen by how you signed in, which machine you use, and which doors the operators opened. This page says what those are without operator secrets or install recipes.
If a detail is not proven in the project docs, it is marked TODO(verify).
The big picture¶
Think of layers that stack:
- Where it runs — on your Windows PC, or in the family’s hosted cloud.
- Who you are in the hosted app — invitation code path (YC or team) or Google allowlist path (internal, user testing, QA).
- Which environment — real production hosts vs QA hosts (and separate data buckets so test copy cannot overwrite the public site).
- Which docs you can open — some pages are only for YC reviewers, some only for team testers (and the marketing site has its own Team / Internal / Tester lists).
These layers are mostly independent. Turning on “user testing surveys” does not by itself invent a new installer.
Matrix (everyday language)¶
| What people call it | In simple terms | How someone gets it | How it is chosen | How it is handed out |
|---|---|---|---|---|
| Public desktop | The normal app on a Windows computer. Your job-search data stays on that machine by default. | Install the single Windows setup file (WorkWingman-Setup-…). No need to install .NET or Node yourself. |
This is the default when the cloud “server edition” switch is off. | Share the installer file. Optional later auto-update from a hosted feed (configured, but the package still marks the feed as not fully published — TODO(verify) live updates). |
| Internal | Hosted app for people on the internal-testing allowlist (staff / internal checks). | Sign in with Google on the hosted app if your email is listed under internal-testing. | Server-side email list (not a special desktop installer). | Link to the hosted app (production or QA host). |
| Team test | Hosted workspace for team testers who redeem a team invitation. | Use the team invitation code (plaintext is shared privately; the service only stores a hash). | Invitation is configured as audience team-test. | Private out-of-band code + hosted app URL. |
| YC reviewer | Hosted workspace for YC review, with a tighter feature menu. | Redeem a YC invitation code. | Invitation audience yc-reviewer. | Same idea: private code + hosted app. Some docs only appear for this audience. |
| QA / “Test Bench” | Hosted QA cohort. Design notes say some people do “Test Bench QA” and real user testing, so at sign-in they may be asked which mode this session is. | Google allowlist for cohort qa (often a shared QA workspace). Dual-role people are listed for multi-mode choice. | Cohort name becomes the session label. | Hosted app; QA may use a separate QA host so production is not mixed. |
| User testing (related) | Hosted cohort for people using the product like real users; surveys can be turned on for the deployment. | Google allowlist user-testing, and/or deployments with user-testing surveys enabled. | Cohort + optional user-testing flag on the server. | Hosted app; marketing site may show a user-testing notice before sign-in. |
| Cloud website | The public marketing / info site (and staff CMS), not the full desktop install. | Open the public site in a browser. Staff CMS needs staff Google allowlist. | Separate cloud service from the product app. | Public URL (and a QA site URL that must not publish into the live content bucket). |
| YC reviewer docs tier | Certain in-app documentation pages visible only after you are in as yc-reviewer. | Hosted app session with that audience; page must list that audience. | Per-document allow list in the docs manifest. | Same hosted app docs API — fail closed if you are not on the list. |
What “Test Bench mock / live” is not (in this repo)¶
People sometimes expect a pair of products named “mock Test Bench” and “live Test Bench.”
In this repository that pair is not defined. There is:
- A QA cohort (and multi-mode choice between QA-style work and real user testing).
- A desktop sandbox vs real data world for local testing.
- A production vs QA deployment ladder for cloud hosts.
There are no edition flags found named mock/live Test Bench. TODO(verify) if that naming exists only in conversation or another repo.
Desktop packaging (friend-friendly)¶
- One installer carries the window, the screens, the background helper, and the browser used for some sign-in flows.
- Install is per user (no admin prompt).
- Updates can be Manual, Notify-me, or Automatic once a real update feed is hosted.
- Windows may warn about an unknown publisher until signing reputation exists.
There is not a separate “internal desktop installer” product name in the packaging config — one WorkWingman desktop package.
Docs audiences (two different systems)¶
- Inside the hosted product — pages tagged
yc-reviewerand/orteam-test(example test pages: team-only and yc-only). - On the marketing site — Team / Internal / Tester email tiers (different names, different lists).
Do not assume one list controls both.
Missing document¶
A dedicated tester laptop distribution specification file was requested by name but is not in this tree. How testers receive laptops or offline installers beyond “share the NSIS exe” is TODO(verify).
One-sentence summary¶
Desktop is the default everyday product; the cloud is invitation- or allowlist-gated tasting rooms; QA / internal / user-testing are who you are in those rooms; the public site is the brochure and CMS — and “mock vs live Test Bench” is not a formal edition pair in this repo.