TARGET DOSSIER // TGT-00 // DOGFOOD
warOnSaaS builds itself
warOnSaaS is its own first target. wOS will be built with the same process it runs for every other target: roadmap, Feature Contracts, build units, independent review, gated PRs.
01HEADER
- ID
- TGT-00
- DESIGNATION
- warOnSaaS
- SHORT NAME
- wOS
- STATUS
- PHASE 0
- ROADMAP
- NOT OPENED
- CONTRIBUTORS
- 0
02PROGRESS
THREE INDEPENDENT MEASURESShare of the product written down on the public roadmap.
Share with an agreed, reviewed Feature Contract.
Share built, checked and merged.
Why 0%: Nothing has been merged through wOS yet. The public website exists, but it was built before wOS existed and went through no roadmap, contract or review, so it does not count.
03STATE OF WORK
- Public website
- Exists. This site is the static v0: pages rendered at build time, data from a file, every number 0%.
- Architecture
- In progress. Phase 0: shared contracts, schemas and protocols. Nothing merged yet.
- Everything else
- Not started.
04FEATURE PROPOSAL
PROPOSED — PENDING ROADMAP CONSENSUSThe V1 feature list, written in the roadmap format every target will use: capabilities, and features under each. It is a proposal. It becomes the roadmap only when Fable and Astra both report no material gaps.
- CAPABILITIES
- 10
- FEATURES
- 86
- EXISTS
- 4
- IN PROGRESS
- 8
- NOT STARTED
- 74
C-00 Architecture and contracts
IN PROGRESSPhase 0. The shared foundation every other capability builds against.
Phase 0 is under way. Nothing from it is merged yet.
- Monorepo structure and dependency rulesIN PROGRESS
- PostgreSQL schema and domain modelIN PROGRESS
- Shared TypeScript types, API contracts and event contractsIN PROGRESS
- Roadmap, Feature Contract and Atomic Build Unit schemasIN PROGRESS
- Agent-policy and context-manifest schemasIN PROGRESS
- Contribution and reward-ledger schemasIN PROGRESS
- GitHub integration contracts and security boundariesIN PROGRESS
- Architecture documents: architecture, domain model, roadmap, feature contract, build, context, agent policy, review, reward and security protocolsIN PROGRESS
C-01 Control Plane
NOT STARTEDThe API and system of record for targets, roadmaps, features, build units, leases and progress.
- APINOT STARTED
- Accounts: email magic-link sign-in, linked GitHub identityNOT STARTED
- Projects and Sniper TargetsNOT STARTED
- Application roadmapsNOT STARTED
- Features and Feature ContractsNOT STARTED
- Atomic Build Units and dependency graphsNOT STARTED
- LeasesNOT STARTED
- State machinesNOT STARTED
- Progress calculations: mapped, specified, builtNOT STARTED
- Contributor recordsNOT STARTED
- Application and feature progress eventsNOT STARTED
C-02 Public Web
EXISTSThis website: the Sniper List, target pages, roadmaps, progress and contributions.
Only the static v0 exists: this site, with its data in a file, all numbers 0%.
- Sniper List with real progressStatic v0. Data from a file.EXISTS
- Public application pagesStatic v0. One dossier per target.EXISTS
- Self-hosted and hosted status per appStatic v0.EXISTS
- Leaderboard pageStatic v0 empty state only.EXISTS
- Opt-in public leaderboard with real rankingsNOT STARTED
- Switch from the static data file to the control-plane APINOT STARTED
- Drilldown: application, capability, feature, requirement, build unit, contributionNOT STARTED
- Feature pagesNOT STARTED
- Roadmap viewsNOT STARTED
- Latest activityNOT STARTED
- Contributor profilesNOT STARTED
- Token and reward historyNOT STARTED
- GitHub PR linksNOT STARTED
C-03 wOS Desktop
NOT STARTEDThe contributor app. Electron, React, TypeScript.
- Sign-inNOT STARTED
- Sniper List browsingNOT STARTED
- Application and feature drilldownNOT STARTED
- Build-unit browsingNOT STARTED
- BUILD flowNOT STARTED
- Local Claude Code detection and agent statusNOT STARTED
- Terminal and activity displayNOT STARTED
- Contribution history and contributor profileNOT STARTED
- SettingsNOT STARTED
- Privileged main process for git, worktrees and local processes; isolated rendererNOT STARTED
C-04 wOS CLI
NOT STARTEDThe same protocol as Desktop, from a terminal.
- wos buildNOT STARTED
- wos roadmapNOT STARTED
- wos proposeNOT STARTED
- wos resolveNOT STARTED
- wos reviewNOT STARTED
- wos statusNOT STARTED
- Shared orchestration logic with DesktopNOT STARTED
C-05 GitHub and gated PRs
NOT STARTEDGitHub is the public record. Only the wOS GitHub App opens PRs, and only after qualification.
- Repository management, worktrees and branchesNOT STARTED
- Immutable base commitsNOT STARTED
- Task leasesNOT STARTED
- Allowed and forbidden paths; diff validationNOT STARTED
- Signed submissions uploaded to the control planeNOT STARTED
- Qualification: LEASE, BUILD, VERIFY, REVIEW, QUALIFY, PRNOT STARTED
- PR creation by the wOS GitHub AppNOT STARTED
- PR metadata and contribution provenanceNOT STARTED
- Merge webhooksNOT STARTED
- Branch rulesets and the wos/qualified checkNOT STARTED
C-06 Context Engine and Agent Policy
NOT STARTEDEach agent run gets its own exact, recorded context and a machine-readable policy.
- Role-specific context for roadmap, feature, builder, reviewer and architecture-resolver rolesNOT STARTED
- Immutable context manifestsNOT STARTED
- Context budgets; oversized build units rejected for decompositionNOT STARTED
- Machine-readable agent policiesNOT STARTED
- Model and reasoning-effort attestationNOT STARTED
C-07 Roadmap AI and review orchestration
NOT STARTEDPlanning and consensus: one canonical roadmap per app, two independent reviewers.
- One canonical Roadmap PR per applicationNOT STARTED
- Independent Astra and Fable review rounds until NO MATERIAL GAPSNOT STARTED
- Feature Contract consensusNOT STARTED
- Shared Feature Catalog with de-duplicationNOT STARTED
- Merged roadmap materialises tracked featuresNOT STARTED
- Merged Feature Contract generates a Build GraphNOT STARTED
- Implementation review on other contributors' machinesNOT STARTED
- Bootstrap review mode while the reviewer pool is smallNOT STARTED
C-08 Rewards ledger
NOT STARTEDWOS tokens: one append-only ledger, one unit. In-app credits with no cash value.
- Append-only ledger; balances derived, never mutatedNOT STARTED
- Contribution categoriesNOT STARTED
- Feature and application completion poolsNOT STARTED
- Reward historyNOT STARTED
- Opt-in public leaderboardNOT STARTED
- Transferability and redemption disabledNOT STARTED
C-09 Verification
NOT STARTEDDeterministic checks, and a workstream that tries to break the system.
- Typechecking, linting, unit and integration testsNOT STARTED
- Task acceptance testsNOT STARTED
- Diff and scope validationNOT STARTED
- Security checksNOT STARTED
- Context and roadmap-state testsNOT STARTED
- Concurrency and lease testsNOT STARTED
- Integration-wave and end-to-end testsNOT STARTED
- CI re-verification on every PRNOT STARTED
Source: the founder’s V1 specification and decisions. Status is shape and words only: EXISTS is a filled tag, IN PROGRESS an outlined tag, NOT STARTED a faint tag.
05HOW TO CONTRIBUTE
The same way as any target, once the process exists: propose changes to the canonical roadmap, then build and review leased units. Until the control plane exists there is nothing to lease.