pwa

Product promise

ProductFlow — a live capability-engine domain node (owner revi-code, T1): lifecycle states, stage logic, gates, and propagation for every product. domains/product-flow.xml:6-6

The domain's data is accurate, current, and correctly routed; the agents that read it act on truth. revi-code owns it; the founder decides it's sound. Here that means: no stage is skippable — the gate decides advancement, never the calendar. domains/product-flow.xml:18-18

Tasks — a live operations domain node (owner bloom, T1): work-queue states, attribution, escalation, and propagation for the fleet's work. domains/tasks.xml:6-6

The domain's data is accurate, current, and correctly routed; the agents that read it act on truth. bloom owns it; the founder decides it's sound. Here that means: no ghost work — every action attributes to a work-queue row or it did not happen. domains/tasks.xml:18-18

Product promise for Installable app. Customer ask centers on a Installable app for GCBC. Link-install app that works offline. You get: A PWA customers can use. Raw ask: Build a Installable app for GCBC.

Detail for Product promise: this Installable app stays locked to a Installable app. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Installable app appears in the working lines, not only the title.

Evidence for Product promise: where a number or rule is stated, it must be re-checkable against your ask (“Build a Installable app for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Installable app could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Product promise: next action is concrete for a Installable app — who does what, by when, and what “done” looks like for this Installable app. Category spine “Product promise” is mandatory; skipping it is a refuse, not a soft omit.

Surfaces & flows

Create D50-compliant XML envelope at products/xml/{id}.xml. Validate against schemas/rll-system.xsd. Register in rll-system.xml domains/product-registry. Emit D57 triple: rl_action=product_defined. domains/product-flow.xml:104-104

Run four-layer-builder cli.mjs with product XML as input. For model products: run mlx training loop → adapter_config.json + adapters.safetensors. For web products: run audit-before-deploy.sh gate 1-4 (static scan). Block advancement if any gate fails. domains/product-flow.xml:110-110

For model products: run product-testing suite (~/RLL/training-data/product-testing/). For web products: run audit-before-deploy.sh gate 5-9 (canary + edge). Require ≥80% pass rate on product-testing before advancing. Emit D57 triple: rl_action=product_tested, rl_result={pass_rate}. domains/product-flow.xml:116-116

For model products: run adapter-bake.sh --role {role} --date {date}. For web products: Netlify deploy via deploy.sh. Verify deployment: ollama list | grep {tag} OR curl -s {url} returns 200. Emit D57 triple: rl_action=product_deployed. domains/product-flow.xml:122-122

For model products: confirm revi-{role}:{date} AND revi-{role}:latest both present on mac1+mac2. For web products: verify revenue surface live (Stripe product_id resolves). Update bake-state.json (models) or product-registry (web products). domains/product-flow.xml:128-128

Run L-tier eval against served model: model-gate.sh --role {role}. Require L3+ to advance to promoted (L5+ is Gate A target). For web products: confirm first purchase event received in historian chain. Emit D57 triple: rl_action=product_validated, rl_result=L{tier}. domains/product-flow.xml:133-133

Surfaces & flows for Installable app. Customer ask centers on a Installable app for GCBC. Link-install app that works offline. You get: A PWA customers can use. Raw ask: Build a Installable app for GCBC.

Detail for Surfaces & flows: this Installable app stays locked to a Installable app. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Installable app appears in the working lines, not only the title.

Evidence for Surfaces & flows: where a number or rule is stated, it must be re-checkable against your ask (“Build a Installable app for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Installable app could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Surfaces & flows: next action is concrete for a Installable app — who does what, by when, and what “done” looks like for this Installable app. Category spine “Surfaces & flows” is mandatory; skipping it is a refuse, not a soft omit.

Standards & sources

Gates fail-closed: any gate failure blocks advancement; test requires ≥80% pass, validate requires L3+; deploy verified by ollama tag or HTTP 200; D57 triples audit every transition. domains/product-flow.xml:15-15

Gate A (capability) depends on stage=validated at L5+; Gate C on stage=promoted domains/product-flow.xml:191-191

No task closes without attribution; no completion without verifier pass; task records are never deleted; the task-attribution-auditor grades every close. domains/tasks.xml:15-15

Standards & sources for Installable app. Customer ask centers on a Installable app for GCBC. Link-install app that works offline. You get: A PWA customers can use. Raw ask: Build a Installable app for GCBC.

Detail for Standards & sources: this Installable app stays locked to a Installable app. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Installable app appears in the working lines, not only the title.

Evidence for Standards & sources: where a number or rule is stated, it must be re-checkable against your ask (“Build a Installable app for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Installable app could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Standards & sources: next action is concrete for a Installable app — who does what, by when, and what “done” looks like for this Installable app. Category spine “Standards & sources” is mandatory; skipping it is a refuse, not a soft omit.

Offline / install path

Must stay consistent with rll-system.xml and its declared propagation; kin to the other domains by ID reference. Here that means: no stage is skippable — the gate decides advancement, never the calendar. domains/product-flow.xml:13-13

D50 product XML envelopes (products/xml) · training corpus + adapter safetensors · customer-signal outputs · founder directives (Notion Founder Tasks DB). domains/product-flow.xml:11-11

Must stay consistent with rll-system.xml and its declared propagation; kin to the other domains by ID reference. Here that means: no ghost work — every action attributes to a work-queue row or it did not happen. domains/tasks.xml:13-13

Founder directives (Notion) · bloom commands · agent outputs (any revi-* completing work) · orchestrator inbox · founder-approval escalations. domains/tasks.xml:11-11

Offline / install path for Installable app. Customer ask centers on a Installable app for GCBC. Link-install app that works offline. You get: A PWA customers can use. Raw ask: Build a Installable app for GCBC.

Detail for Offline / install path: this Installable app stays locked to a Installable app. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Installable app appears in the working lines, not only the title.

Evidence for Offline / install path: where a number or rule is stated, it must be re-checkable against your ask (“Build a Installable app for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Installable app could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Offline / install path: next action is concrete for a Installable app — who does what, by when, and what “done” looks like for this Installable app. Category spine “Offline / install path” is mandatory; skipping it is a refuse, not a soft omit.

Demo path

Emit activity log + health (GREEN/YELLOW/RED) to the historian chain; push blockers to the steward and the founder queue. domains/product-flow.xml:198-198

Report the primary KPI trend up the chain; close or escalate every open task in the domain. domains/product-flow.xml:199-199

Every product that reaches `promoted` is a live revenue surface; the 7-stage gate prevents premature domains/product-flow.xml:181-181

Emit activity log + health (GREEN/YELLOW/RED) to the historian chain; push blockers to the steward and the founder queue. domains/tasks.xml:133-133

Report the primary KPI trend up the chain; close or escalate every open task in the domain. domains/tasks.xml:134-134

Demo path for Installable app. Customer ask centers on a Installable app for GCBC. Link-install app that works offline. You get: A PWA customers can use. Raw ask: Build a Installable app for GCBC.

Detail for Demo path: this Installable app stays locked to a Installable app. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Installable app appears in the working lines, not only the title.

Evidence for Demo path: where a number or rule is stated, it must be re-checkable against your ask (“Build a Installable app for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Installable app could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Demo path: next action is concrete for a Installable app — who does what, by when, and what “done” looks like for this Installable app. Category spine “Demo path” is mandatory; skipping it is a refuse, not a soft omit.

Bound to your ask

If a source is stale or evicted, flag rather than serve wrong data; if ownership is ambiguous, escalate; if authority is uncertain, route to the founder queue (D57). Blocked products advance only with founder approval. domains/product-flow.xml:16-16

Status + blockers + KPI delta delivered to the founder queue; nothing requires the founder during daily ops except escalations. domains/product-flow.xml:207-207

Status + blockers + KPI delta delivered to the founder queue; nothing requires the founder during daily ops except escalations. domains/tasks.xml:142-142

If a source is stale or evicted, flag rather than serve wrong data; if ownership is ambiguous, escalate; if authority is uncertain, route to the founder queue (D57). Stalled tasks go blocked with a defined escalation path. domains/tasks.xml:16-16

Bound to your ask for Installable app. Customer ask centers on a Installable app for GCBC. Link-install app that works offline. You get: A PWA customers can use. Raw ask: Build a Installable app for GCBC.

Detail for Bound to your ask: this Installable app stays locked to a Installable app. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Installable app appears in the working lines, not only the title.

Evidence for Bound to your ask: where a number or rule is stated, it must be re-checkable against your ask (“Build a Installable app for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Installable app could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Bound to your ask: next action is concrete for a Installable app — who does what, by when, and what “done” looks like for this Installable app. Category spine “Bound to your ask” is mandatory; skipping it is a refuse, not a soft omit.