Launch readiness
Historical no-go snapshot, not a current completion score. This register predates later test billing, discovery and security work. Live payments, provider delivery and reconciled financial reporting still lack production acceptance. Read current service availability.
2 / 142
Fully verified mandatory requirements
94 / 94
Tests passed at this historical checkpoint · not the current suite or a launch percentage
Pending
Review status at the historical checkpoint, not a current security verdict
Only fully verified requirements count. Partial work, missing functions and untested dependencies receive no completion credit. A working private workspace is not a public visibility engine.
Evidence below is retained as recorded at this earlier checkpoint and is not automatically refreshed. Later publication and test-billing work do not certify every requirement. See current availability for qualified updates; no current indexing, AI citations or launch percentage is asserted here.
1. Business registration and onboarding
0/12 · 0.0% verified
R01-01 · PARTIAL · Business account registration and authentication
src/routes/auth.tsx; prior signed-in acceptance; hosted auth and delivery settings not revalidated
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-02 · PARTIAL · Email verification and password recovery
src/routes/auth.tsx and reset-password.tsx; real email delivery/recovery lifecycle not tested
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-03 · PARTIAL · Business profile creation and editing
Owner-private creation/edit/reload verified in preview; revision conflicts and ownership transfer rejected; 109 tests pass. Full production onboarding and cross-customer lifecycle certification remain unverified.
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-04 · PARTIAL · Business categories and industry classification
manual onboarding category; automated/regulated industry classification absent
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-05 · PARTIAL · Country, city and geographic targeting
saved country/operating-region/preferred markets; no geographic discovery
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-06 · PARTIAL · Business contact information and website links
validated owner-private onboarding fields; no published customer page
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-07 · MISSING · Business logos, images and descriptions
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-08 · PARTIAL · Business ownership verification
internal ownership checks only; no merchant proof or public verification
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-09 · MISSING · Duplicate registration prevention
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-10 · MISSING · Free and paid account entitlements
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-11 · PARTIAL · Customer onboarding and account management
private onboarding and workspace; full lifecycle/account deletion unimplemented
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R01-12 · MISSING · Business profile publication and visibility
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
2. SEO and global search visibility
1/19 · 5.3% verified
R02-01 · MISSING · Automated SEO generation for registered businesses
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-02 · MISSING · Search-friendly public business profile pages
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-03 · VERIFIED · Meta titles and descriptions
SEO foundations scanner: metadata_basics:search_metadata passing; all content routes inspected for head metadata; Current homepage scan and route-source inspection; not indexed-business-profile evidence
Severity: none · Owner: Engineering
Planning estimate: S (0.5–2 engineering days). Estimates exclude provider review and are not commitments.
Next action: Preserve and recheck after changes.
R02-04 · PARTIAL · Structured data and Schema.org
Homepage Organization/WebSite/SoftwareApplication JSON-LD verified in preview SSR; publication and customer public-profile structured data remain unavailable.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-05 · PARTIAL · XML sitemaps and robots.txt
Router-derived four-page XML sitemap and robots reference verified in preview; private/account routes excluded; publication and submission remain unverified.
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-06 · PARTIAL · Canonical URLs
Four discoverable public pages have one self-referencing published-origin canonical verified in preview SSR; publication and future customer public pages remain unverified.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-07 · MISSING · Search engine indexing
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Customer provider authorization + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-08 · MISSING · Google Search Console integration
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Customer provider authorization + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-09 · MISSING · Bing Webmaster Tools integration
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Customer provider authorization + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-10 · MISSING · Internal linking and category pages
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-11 · MISSING · Industry-specific landing pages
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-12 · MISSING · Geographic landing pages
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-13 · PARTIAL · Mobile SEO
homepage mobile fit previously verified; no Core Web Vitals certification
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-14 · MISSING · Core Web Vitals
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-15 · MISSING · Multilingual and international SEO
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-16 · MISSING · Search performance monitoring
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Customer provider authorization + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-17 · MISSING · Automated SEO health checks
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-18 · MISSING · Broken link detection
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R02-19 · MISSING · Duplicate content prevention
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
3. GEO and AI-powered discovery
0/9 · 0.0% verified
R03-01 · PARTIAL · AI-readable business profiles
private structured facts and host markdown support; public business profiles absent
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-02 · PARTIAL · Structured business information
owner-private business fields; no public entity schema
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-03 · PARTIAL · Semantic content optimisation
uploaded-page recommendations and private assistant; not automated website changes
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-04 · PARTIAL · Industry and location relevance
saved customer-declared context; verified public discovery absent
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-05 · PARTIAL · AI-friendly FAQs
uploaded FAQ/schema checks; generated published FAQs absent
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-06 · PARTIAL · Business entity consistency
bounded uploaded evidence checks; cross-source verification absent
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-07 · PARTIAL · Content freshness
draft timestamps and revisions; no delivery or freshness automation
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-08 · MISSING · AI referral tracking
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Customer provider authorization + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R03-09 · MISSING · Generative search discoverability monitoring
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Customer provider authorization + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
4. Global business visibility engine
0/12 · 0.0% verified
R04-01 · MISSING · Business discovery and search functionality
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-02 · MISSING · Industry and category filtering
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-03 · MISSING · Geographic search and targeting
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-04 · MISSING · Business profile ranking logic
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-05 · MISSING · Free versus paid visibility entitlements
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-06 · MISSING · Featured business placement
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-07 · MISSING · Visibility performance measurement
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-08 · MISSING · Business profile sharing
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-09 · MISSING · Search result relevance
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-10 · MISSING · Fair exposure and ranking policies
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-11 · MISSING · Business directory navigation
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R04-12 · PARTIAL · International accessibility
international fields and responsive layout; multilingual/accessibility certification pending
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
5. Stripe, subscriptions and seven-day free trials
0/16 · 0.0% verified
R05-01 · PARTIAL · Subscription pricing tiers of $2.50, $5.99, $7.99 and $10.99, subject to the approved billing intervals
commercial.ts with passing concrete commercial tests; no Stripe catalog
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-02 · PARTIAL · Seven-day free trial eligibility
trial conditions defined and tested; no activated trial enforcement
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-03 · MISSING · Payment method collection before trial activation
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-04 · MISSING · Clear consent to recurring charges
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-05 · MISSING · Automatic subscription billing after trial expiry
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-06 · MISSING · Trial expiration handling
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-07 · MISSING · Subscription upgrades and downgrades
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-08 · MISSING · Failed payment recovery
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-09 · MISSING · Cancellation and refund workflows
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-10 · MISSING · Webhook security and reliability
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-11 · MISSING · Duplicate payment prevention
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-12 · MISSING · Invoice generation
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-13 · MISSING · Customer billing management
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-14 · MISSING · Subscription entitlement synchronisation
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-15 · MISSING · Revenue reconciliation
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R05-16 · MISSING · Applicable tax and payment compliance
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Company/payment owner + engineering; test Stripe enablement and product catalog required
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
6. Marketing automation and business acquisition
0/13 · 0.0% verified
R06-01 · MISSING · Automated onboarding emails
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-02 · MISSING · Welcome campaigns
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-03 · MISSING · Trial reminders
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-04 · MISSING · Subscription conversion campaigns
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-05 · MISSING · Renewal and payment notifications
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-06 · MISSING · Referral mechanisms, if included
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-07 · MISSING · Email marketing integrations
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-08 · MISSING · Business promotion workflows
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-09 · MISSING · Lead capture and conversion tracking
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-10 · MISSING · Customer reactivation
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-11 · MISSING · Campaign attribution
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-12 · MISSING · Email consent and unsubscribe management
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R06-13 · MISSING · Marketing performance analytics
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
7. Backend and database consolidation
0/16 · 0.0% verified
R07-01 · PARTIAL · Database schema and relationships
16 public tables inspected; all RLS enabled; full integrity/recovery review incomplete
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-02 · PARTIAL · Authentication and authorisation
bearer middleware, protected routes and RLS; privileged identities not registered
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-03 · PARTIAL · Business registration APIs
validated authenticated saveBusiness; business duplicate prevention missing
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-04 · PARTIAL · Business profile storage
owner-private Cloud records and schema tests; publication absent
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-05 · MISSING · Subscription and payment records
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-06 · MISSING · Search and discovery services
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-07 · MISSING · SEO automation services
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-08 · MISSING · Background jobs and scheduled tasks
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-09 · MISSING · Webhook handlers
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-10 · PARTIAL · Error handling and retries
audit/AI errors surfaced; some AI terminal/pause recovery and stale-run cases need review
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-11 · PARTIAL · Database security policies
basic scan no findings; deep code scan running
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-12 · PARTIAL · Data consistency and integrity
constraints/revision checks and reservation triggers; broad lifecycle checks pending
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-13 · PARTIAL · API connectivity
real AI assistant replies previously verified; Google consent and payments unverified
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-14 · PARTIAL · Monitoring and logging
error signals and bounded company assistant logs; incident/operational alerting missing
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-15 · MISSING · Backup and recovery
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R07-16 · PARTIAL · Deployment configuration
public publication read; unpublished current assistant/admin changes
Severity: launch-blocker · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
8. Profitability and infrastructure cost protection
0/16 · 0.0% verified
R08-01 · MISSING · Hosting and database costs
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-02 · MISSING · Third-party API expenses
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-03 · MISSING · AI processing costs
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-04 · MISSING · SEO automation expenses
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-05 · MISSING · Email delivery costs
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-06 · MISSING · Stripe transaction fees
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-07 · MISSING · Free-tier operating costs
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-08 · MISSING · Trial-user acquisition costs
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-09 · MISSING · Per-business servicing costs
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-10 · MISSING · Subscription gross margins
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-11 · MISSING · Monthly recurring revenue
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-12 · MISSING · Break-even subscriber requirements
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-13 · MISSING · Cost-per-user monitoring
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-14 · PARTIAL · Usage limits and abuse prevention
audit quotas/one active assistant request and dedup; no per-account assistant cost/count budget
Severity: medium · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-15 · MISSING · Cost alerts and automated safeguards
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R08-16 · MISSING · Infrastructure scaling thresholds
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Finance owner + verified invoices/transactions + engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
9. Security and compliance
1/15 · 6.7% verified
R09-01 · PARTIAL · Account security
managed sign-in and session verification; attack/recovery lifecycle not certified
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-02 · PARTIAL · Role-based permissions
separate company roles; normal-owner denial verified; privileged acceptance pending
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-03 · PARTIAL · Administrative access
restricted /admin; 0 company role assignments; designated account validation pending
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-04 · PARTIAL · Database security
all 16 tables RLS enabled and basic scan clear; deeper scan pending
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-05 · PARTIAL · API protection
authenticated server functions, CSRF middleware and Google callback state; deep review pending
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-06 · MISSING · Fraud prevention
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-07 · MISSING · Payment security
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-08 · MISSING · Bot and spam protection
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-09 · PARTIAL · Business ownership verification
internal ownership checks only; no merchant proof or public verification
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-10 · PARTIAL · Data privacy
private rows and disclosures; production retention/deletion procedures missing
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-11 · MISSING · UK GDPR and applicable international privacy obligations
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-12 · VERIFIED · Secure credential storage
Secret-name inspection: five encrypted configured secrets; Google token encryption implementation and existing tests; Credential values never exposed; provider consent remains unverified
Severity: none · Owner: Engineering/security + company privacy review
Planning estimate: S (0.5–2 engineering days). Estimates exclude provider review and are not commitments.
Next action: Preserve and recheck after changes.
R09-13 · MISSING · Security monitoring
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-14 · MISSING · Incident recovery
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R09-15 · MISSING · Backup protection
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: launch-blocker · Owner: Engineering/security + company privacy review
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
10. Analytics and administration
0/14 · 0.0% verified
R10-01 · MISSING · Total registered businesses
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-02 · MISSING · Free and paid subscribers
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-03 · MISSING · Active trials
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-04 · MISSING · Trial-to-paid conversion
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-05 · MISSING · Subscription revenue
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-06 · MISSING · Churn and cancellations
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-07 · MISSING · Business profile views
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-08 · MISSING · Search impressions and referrals
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-09 · MISSING · SEO and GEO performance
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-10 · MISSING · Business discovery activity
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-11 · MISSING · Marketing conversion
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-12 · PARTIAL · Infrastructure costs
recorded-cost view/schema; 0 cost receipts and no ingestion
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-13 · MISSING · Platform profitability
No implementation or passing end-to-end evidence found for this mandatory requirement.
Severity: high · Owner: Engineering
Planning estimate: L (1–3+ engineering weeks). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
R10-14 · PARTIAL · System health and operational errors
bounded assistant operations view; no full platform health reporting
Severity: medium · Owner: Engineering
Planning estimate: M (3–7 engineering days). Estimates exclude provider review and are not commitments.
Next action: Complete the missing behavior, resolve the named dependency, then verify the real lifecycle before changing this status.
11. End-to-end integration testing
0/0 · NaN% verified