Context
A full-text search of design/ for the obvious incumbents in this space — Ink/Inkle, Yarn Spinner, Twine, Ren'Py, ChoiceScript — returns exactly one hit, and it's a design contrast for variable-bag semantics (10-design.md decision N6), not a competitive analysis. There is no pricing, revenue model, or named customer anywhere in design/00-brief.md or 10-design.md. 01-vision.md §5 explicitly defers "the hosted service, accounts, billing... cloud sync, analytics, multiplayer, white-labelling" to SubZeroDev.Platform, and §6 states "The engine is the product. Campaigns are the catalogue" without naming a buyer.
This isn't a criticism of the engineering — the core/kind/campaign architecture is validated by three independent implementations against one interface, which is real technical evidence. But right now nothing in the repository answers: who pays, why, versus what alternative, and what evidence (if any) suggests demand. gh release list is empty; the package publishes only to GitHub Packages under @the-running-dev, not public npm; there's no waitlist, analytics, or public track record of users.
Session context suggests the engine may be intended as "one capability in a nine-part ecosystem, not a standalone product" — if that framing is accurate, it materially changes how this gap should be read, but it isn't recorded anywhere in design/ today.
Ask
Not a code change. Add a short section to design/00-brief.md (or a new decisions entry in 90-decisions.md if the answer is "deferred, and here's why") that states explicitly:
- Who the intended customer/user is (even if hypothetical/deferred), consistent with the ecosystem framing if that's the real intent.
- The one or two nearest alternatives (Ink/Yarn Spinner/Twine/Ren'Py are the obvious set) and what this engine's determinism + cross-version replay oracle + MCP-as-player actually buys over them.
- Whether monetization is genuinely out of scope for this repo (in which case, say so plainly, the way
01-vision.md §5 already does for hosting) or whether it's an open question worth tracking in OPEN-QUESTIONS.md.
The goal is to convert "unstated" into "explicitly deferred, with reasoning" — the same treatment this repo already gives every other deferred concern.
Origin
Raised in a 2026-08-06 project assessment.
Context
A full-text search of
design/for the obvious incumbents in this space — Ink/Inkle, Yarn Spinner, Twine, Ren'Py, ChoiceScript — returns exactly one hit, and it's a design contrast for variable-bag semantics (10-design.mddecision N6), not a competitive analysis. There is no pricing, revenue model, or named customer anywhere indesign/00-brief.mdor10-design.md.01-vision.md§5 explicitly defers "the hosted service, accounts, billing... cloud sync, analytics, multiplayer, white-labelling" toSubZeroDev.Platform, and §6 states "The engine is the product. Campaigns are the catalogue" without naming a buyer.This isn't a criticism of the engineering — the core/kind/campaign architecture is validated by three independent implementations against one interface, which is real technical evidence. But right now nothing in the repository answers: who pays, why, versus what alternative, and what evidence (if any) suggests demand.
gh release listis empty; the package publishes only to GitHub Packages under@the-running-dev, not public npm; there's no waitlist, analytics, or public track record of users.Session context suggests the engine may be intended as "one capability in a nine-part ecosystem, not a standalone product" — if that framing is accurate, it materially changes how this gap should be read, but it isn't recorded anywhere in
design/today.Ask
Not a code change. Add a short section to
design/00-brief.md(or a new decisions entry in90-decisions.mdif the answer is "deferred, and here's why") that states explicitly:01-vision.md§5 already does for hosting) or whether it's an open question worth tracking inOPEN-QUESTIONS.md.The goal is to convert "unstated" into "explicitly deferred, with reasoning" — the same treatment this repo already gives every other deferred concern.
Origin
Raised in a 2026-08-06 project assessment.