Google review request links, QR campaigns, email follow-up drafts, private recovery, widgets, visibility, reports, agency, team access, brand readiness, settings governance, billing readiness, operational QA readiness, customer onboarding readiness, audit/export readiness, growth, API layer and owner summaries all point to controlled app surfaces.
Track what RatingE source covers and what still needs approval.
This private ledger maps every visible RatingE feature promise to a controlled app workspace. It separates delivered source coverage from approval-gated live balance so operators do not confuse ready UI with deploys, imports, payment, provider sync, brand publishing, live sending or customer outreach.
Delivered source coverage is separated from approval-gated live balance
The ledger is source-only. It is a control surface for evidence and planning, not an activation surface for runtime, data, billing, providers or customer communications.
- Feature Delivery Ledger workspace
- Public promises mapped to private app workspaces
- Delivered source coverage is separated from approval-gated live balance
- No deploy/runtime switch is triggered
- No DNS or routing change is made
- No Appwrite customer mutation is performed
- No customer data import is performed
- No payment activation is performed
- No checkout is created
- No provider sync/import/OAuth is performed
- No live messaging or outreach is sent
Contacts, campaigns, AI reply briefs, email follow-up and review-to-social assets remain prepared evidence, not send queues.
Agency permissions, team access, staff handoff, industry benchmarks and billing/provider activation stay behind owner approval gates.
Delivery claims need the dedicated delivery guard, full feature guard, build and local smoke before they can be treated as current.
Review links, QR endpoint, client workspace and Reputation hub
No fake review or guaranteed-star claim is made.Draft-onlyWhatsApp and QR review campaignsContacts, Campaign Draft Workspace, QR API and Flow Wizard
No WhatsApp, email or SMS provider send is triggered from the workspace.Draft-onlyEmail review follow-upContacts import channel, Campaign Draft Workspace and Reports
Live email delivery remains disabled until provider, opt-out and approval gates are approved.ImplementedPrivate feedback recovery workflowFeedback Inbox, Recovery drafts, Reputation hub and Reports
The inbox prepares recovery work only; it does not send replies or public responses.ImplementedWebsite review widgetsWidget API, install kit, schema endpoint and client workspace
Only approved proof should be published; private feedback stays private.Approval-gatedGoogle profile and local visibility readinessVisibility Readiness, Reputation hub, Rollout board and onboarding checklist
No GBP sync, listing submission, SEO publish, GSC action, customer write or outreach is triggered.ImplementedMulti-location campaign reportingReports workspace, Rollout board and client workspaces
Reports are read-only and do not trigger imports, sends, checkout or route changes.ImplementedReputation performance reportingReports workspace, Feature Delivery Ledger and Launch Handoff
Reporting reads existing evidence only; it does not generate exports, send handoffs, create campaigns or mutate customer records.Approval-gatedAgency workspaceAgency Workspace, Rollout board, Reports and client workspaces
No invite, role mutation, white-label publication, customer write or outreach is triggered.Approval-gatedStaff and branch handoff playbooksTeam Access readiness, client invite drafts, Rollout board and customer workspace handoff
Invite drafts do not send email, mutate roles or create customer access until approved.ImplementedOwner-ready reputation summariesControl Center, Flow Wizard and Reports
Summary surfaces distinguish ready from sent and do not import contacts, send messages, create reports, mutate payment or trigger delivery systems.Approval-gatedPilot customer readinessPilot Readiness, Rollout board, Delivery Ledger and Launch Handoff
No deploy, route change, import, provider send, payment activation, owner handoff, customer handoff or outreach is triggered.Draft-onlyAI response assistanceGrowth Delivery workspace and Reputation hub
No AI provider call, public reply, review-source API or customer message is triggered.Draft-onlyReview-to-social publishingGrowth Delivery workspace, Reports and Website proof widgets
No social post, media upload, provider queue or external publishing action runs from RatingE.Approval-gatedIndustry benchmark libraryGrowth Delivery workspace and Reports
Benchmarks are planning guidance only; no ranking, revenue, review-count or star-rating guarantee is made.Approval-gatedAPI and integration layerAPI Layer readiness, Provider readiness, Delivery Ledger and Launch Handoff
No CRM write, helpdesk ticket, webhook, provider sync, Appwrite mutation, live message or route change is triggered.Approval-gatedProvider and review-source readinessIntegrations readiness, Settings Governance, API Layer readiness and Delivery Ledger
No credential capture, token exchange, provider sync, review import, live message, Appwrite mutation or owner/provider handoff is triggered.Approval-gatedBrand and white-label readinessBrand Readiness, Agency Workspace, Settings Governance and Delivery Ledger
No custom domain, DNS change, white-label report publication, widget theme push, custom code injection or customer mutation is triggered.Approval-gatedAccount settings governanceSettings Governance, Team Access, Billing, Provider readiness and Brand Readiness
No profile save, invite mutation, plan change, credential write, DNS change, Appwrite mutation or outreach is triggered.Approval-gatedBilling and plan activation readinessBilling Readiness, Pricing, Settings Governance and Delivery Ledger
No checkout, payment link, card collection, subscription, invoice API, payment provider call, Appwrite customer mutation or outreach is triggered.Approval-gatedOperational QA readinessOperational QA Readiness, Delivery Ledger, Launch Handoff and Activation Plan
No deploy/runtime switch, DNS/routing change, Appwrite mutation, payment activation, provider sync, support ticket or outreach is triggered.Approval-gatedCustomer onboarding readinessOnboarding Readiness, Rollout board, Team Access, Provider readiness and Launch Handoff
No account activation, import, provider send, payment change, Appwrite mutation or outreach is triggered.Approval-gatedAudit trail and export readinessAudit and Export Readiness, Reports, Delivery Ledger and Launch Handoff
No audit event write, export generation, retention change, customer mutation, provider action or outreach is triggered.Approval-gatedEvidence handoff readinessEvidence Handoff Readiness, Audit and Export Readiness, Delivery Ledger and Launch Handoff
No audit event, export, retention change, dispute notification, owner/customer handoff, customer mutation or outreach is triggered.Approval-gatedSupport operations readinessSupport Operations Readiness, Support Center, Delivery Ledger and Launch Handoff
No ticket creation, helpdesk/CRM/Suhep queue action, customer notification, Appwrite mutation or live messaging/outreach is triggered.Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Tracked in the delivery ledger before any live activation claim.
Dry-run workflow packets stay local before persistence, sends or report handoff.
Contact preview, request draft, feedback classification and report readiness packets map to the private Flow Wizard before any import, request campaign, provider queue, report delivery, customer handoff or live action is approved.
- Contact preview packet
- Request draft packet
- Feedback classification packet
- Report readiness packet
- Owner approval boundary
- No contact import is performed from /app/flow.
- No request campaign is created from /app/flow.
- No WhatsApp, email, SMS, provider queue or live send is triggered from /app/flow.
- No feedback record, recovery draft, report, export or customer handoff is created from /app/flow.
- No Appwrite customer mutation, payment action, DNS change, deploy or runtime switch is triggered from /app/flow.
Pilot packets stay source-only before activation or customer handoff.
Owner selection, manual route proof, draft records, prepared-not-sent copy, triage evidence and owner handoff report packets map to the private Pilot workspace before any customer activation, import, provider queue, route change, payment action or outreach is approved.
- Pilot customer readiness workspace
- Owner selection packet
- Manual route proof packet
- Draft records packet
- Prepared-not-sent copy packet
- Triage evidence packet
- Owner handoff report packet
- Pilot intake desk
- Pilot intake sheet
- Route proof run
- Channel decision strip
- Tiny contact sample rule
- Manual pilot proof run
- Five checks before the first customer is treated as live
- Owner confirms the business and Google review link.
- Operator proves the review route manually on desktop and mobile.
- Tiny contact sample is checked for consent, duplicates, and formatting.
- Request copy is reviewed as human text before any automation decision.
- First owner report is prepared only after the manual loop has evidence.
- No runtime deploy from /app/pilot.
- No route, DNS, Traefik or Cloudflare change from /app/pilot.
- No Appwrite schema/import or customer-data mutation from /app/pilot.
- No WhatsApp, email, SMS, provider queue or live sending from /app/pilot.
- No payment, checkout, subscription or billing activation from /app/pilot.
- No owner handoff, customer handoff, report delivery or outreach is triggered from /app/pilot.
Provider packets stay checklist-only before OAuth, import or sending.
Credential inventory, policy consent, sender readiness and review-source readiness map to the private Integrations workspace before any provider login, token exchange, review import, rating fetch, live send, provider handoff or owner handoff is approved.
- Credential inventory packet
- Policy and consent packet
- Sender readiness packet
- Review-source readiness packet
- Owner/provider handoff boundaries
- No credential capture, token exchange, secret write or provider login is triggered from /app/delivery.
- No review-source OAuth, rating fetch, review import or reply publishing is triggered from /app/delivery.
- No WhatsApp, email, SMS, provider queue or live message is triggered from /app/delivery.
- No owner or provider handoff is delivered from /app/delivery.
Support packets stay readiness-only before helpdesk or outreach action.
Support triage, escalation readiness, SLA review, policy response and owner handoff labels map to the private support operations workspace before any Suhep ticket, helpdesk webhook, notification, owner handoff or customer reply is approved.
- Support triage packet
- Escalation readiness packet
- SLA review packet
- Policy response packet
- Owner handoff packet
- Owner/customer support handoff boundaries
- No ticket creation is performed from /app/delivery.
- No support ticket is created from /app/delivery.
- No helpdesk/CRM/Suhep queue action is triggered from /app/delivery.
- No Suhep API call, helpdesk webhook or automation queue is triggered from /app/delivery.
- No customer notification is sent from /app/delivery.
- No notification, customer reply or support outreach is sent from /app/delivery.
- No owner or customer support handoff is delivered from /app/delivery.
Evidence packets stay review-only before any owner handoff.
Exact audit and export labels now map to the private audit workspace before any export, retention dispute, owner handoff or customer handoff action is approved.
- Private feedback routing
- Private feedback routing is mapped to the Feedback Inbox before public escalation.
- Audit event review
- Activity evidence packet
- Export review packet
- Retention review packet
- Dispute evidence packet
- Operator verification packet
- Audit trail handoff packet
- Export review handoff packet
- Retention evidence packet
- Dispute evidence packet
- Dispute evidence packet is manual-ready
- Owner handoff boundary is approval-gated
- Customer handoff boundary is approval-gated
- Owner/customer handoff boundaries
- No owner or customer handoff is delivered
- No audit event write
- No export generation
- No retention policy change
- No dispute notification
- No audit event is created
- No export is generated
- No retention policy is changed
- No dispute notification is sent
- Support triage packet
- Escalation readiness packet
- SLA review packet
- Policy response packet
- Owner handoff packet
- No owner or customer support handoff is delivered
- Credential inventory packet
- Policy and consent packet
- Sender readiness packet
- Review-source readiness packet
- Owner/provider handoff boundaries
- No owner or provider handoff is delivered
- Flow wizard readiness workspace
- Dry-run packets stay local before imports, sends or handoff.
- Contact preview packet
- Request draft packet
- Feedback classification packet
- Report readiness packet
- Owner approval boundary
- No contact import is performed from /app/flow.
- No request campaign is created from /app/flow.
- No WhatsApp, email, SMS, provider queue or live send is triggered from /app/flow.
- No feedback record, recovery draft, report, export or customer handoff is created from /app/flow.
- No Appwrite customer mutation, payment action, DNS change, deploy or runtime switch is triggered from /app/flow.
- Pilot customer readiness workspace
- Owner selection packet
- Manual route proof packet
- Draft records packet
- Prepared-not-sent copy packet
- Triage evidence packet
- Owner handoff report packet
- Pilot intake desk
- Pilot intake sheet
- Route proof run
- Channel decision strip
- Tiny contact sample rule
- Manual pilot proof run
- Five checks before the first customer is treated as live
- Owner confirms the business and Google review link.
- Operator proves the review route manually on desktop and mobile.
- Tiny contact sample is checked for consent, duplicates, and formatting.
- Request copy is reviewed as human text before any automation decision.
- First owner report is prepared only after the manual loop has evidence.
- No owner handoff, customer handoff, report delivery or outreach is triggered from /app/pilot.
- No audit event is created from /app/delivery.
- No CSV, JSON or report export is generated from /app/delivery.
- No retention, archive, delete or purge policy is changed from /app/delivery.
- No dispute notification or customer record mutation is triggered from /app/delivery.
- No owner handoff, customer handoff, report delivery or outreach is triggered from /app/delivery.
QA proof stays evidence-only before deploy approval.
Fresh disk truth, guard order, build proof, smoke evidence, rollback notes and incident templates can be prepared before release claims. They map to the private Operational QA workspace before any runtime switch, support ticket or owner notification is approved.
- Operational QA Readiness, Delivery Ledger, Launch Handoff and Activation Plan
- Fresh disk truth required before green claim
- Dedicated guards must run before full guard set
- Build must pass before smoke
- Runtime smoke evidence must be fresh
- Temporary server must be stopped
- Port 3068 must be clear after smoke
- Rollback note required before deploy approval
- Incident/postmortem template prepared only
- No deploy/runtime switch is triggered from /app/delivery.
- No DNS or routing change is made from /app/delivery.
- No Appwrite customer mutation is performed from /app/delivery.
- No payment activation is performed from /app/delivery.
- No provider sync/import/OAuth is performed from /app/delivery.
- No support ticket is created from /app/delivery.
- No live messaging or outreach is sent from /app/delivery.
- No deploy/runtime switch, DNS/routing change, Appwrite mutation, payment activation, provider sync, support ticket or outreach is triggered.
Approval-gated live activation, not missing UI
The remaining balance is live activation work that needs explicit owner approval, fresh verification and separate execution. This page does not run those actions.
- Runtime deploy or route switch
- DNS, Cloudflare or Traefik change
- Appwrite schema, import or customer mutation
- Checkout, invoice, card collection or charge
- Provider OAuth, token exchange, sync or review import
- GBP sync, listing submission, SEO publish, schema submission or GSC action
- CRM write, helpdesk ticket, webhook delivery or automation queue
- Custom domain, white-label report, widget theme or custom-code activation
- Profile save, user invite, credential write, plan change or settings mutation
- Account activation, customer import, provider send, payment activation or onboarding outreach
- Billing and plan activation readiness
- Billing readiness
- Plan activation stays prepared, not live.
- Payment activation is blocked by design.
- Ready for review, not collection.
- No checkout, payment link, subscription, invoice API, paid flag, customer upgrade or provider webhook
- Operational QA readiness
- Fresh disk truth required before green claim
- Dedicated guards must run before full guard set
- Build must pass before smoke
- Runtime smoke evidence must be fresh
- Temporary server must be stopped
- Port 3068 must be clear after smoke
- Rollback note required before deploy approval
- Incident/postmortem template prepared only
- Audit event write, export generation, retention change or dispute notification
- Support ticket, Suhep call, helpdesk webhook, notification or support outreach
- No account upgrade, plan write, invite send or role mutation
- WhatsApp, email, SMS, social post or customer outreach
