Platform Wiring Blueprint

Canonical end-to-end spine for Ethosia Global. No new feature layer. This is the wiring map.

Total Flow Stages

8

Wired

7

Needs Review

1

Status

REVIEW_REQUIRED

Seq	Layer	Flow	Primary Route	Primary Table	Health
10	Demand	Public Demand Capture public_demand	`/` Route: exists	`public_inquiries` Table: exists	WIRED
	Inputs: visitor, campaign_source, chatbot_message, contact_form, proposal_request Outputs: inquiry, prelaunch_lead, chatbot_lead Supporting Routes: /contact → /request-proposal → /prelaunch → /ai-sales-chatbot/start Note: Entry layer for all public interest, proposal requests, chatbot leads, and prelaunch demand.
20	Qualification	Lead Qualification qualification	`/admin/prelaunch/qualification` Route: exists	`prelaunch_lead_scores` Table: exists	WIRED
	Inputs: inquiry, prelaunch_lead, chatbot_lead, prospect Outputs: qualified_lead, score, recommended_offer, sales_priority Supporting Routes: /admin/chatbot → /admin/ai-sales-chatbot → /admin/prospecting/quality → /admin/conversion-dashboard Note: Determines fit, readiness, intent, and sales priority.
30	Commercial Conversion	Proposal and Pricing proposal	`/admin/proposals` Route: exists	`public_proposals` Table: exists	WIRED
	Inputs: qualified_lead, inquiry, pricing_context Outputs: proposal, proposal_token, proposal_status Supporting Routes: /admin/pricing/engine → /admin/eaf-proposals → /admin/industry-proposals Note: Turns qualified opportunities into client-facing proposals.
40	Commercial Conversion	Deal Board deal	`/admin/deals/board` Route: exists	`public_deals` Table: exists	WIRED
	Inputs: accepted_proposal, manual_deal, sales_signal Outputs: deal, deal_stage, deal_value, won_status Supporting Routes: /admin/deals → /admin/deals/conversion → /admin/sales-closing Note: Tracks commercial movement from proposal acceptance to won deal.
50	Revenue	Invoice and Payment revenue	`/admin/revenue-invoices` Route: exists	`revenue_invoices` Table: exists	WIRED
	Inputs: won_deal, invoice_request, payment_confirmation Outputs: invoice, payment, receipt, paid_revenue Supporting Routes: /admin/revenue/dashboard → /admin/payments/integration → /admin/payment-webhooks → /pay/{token} → /checkout/crypto/{code} → /receipt/{invoiceCode} Note: Controls invoice lifecycle, payment confirmation, receipts, and revenue reporting.
60	Delivery	Client Project Delivery delivery	`/admin/client-projects` Route: exists	`client_projects` Table: exists	WIRED
	Inputs: paid_invoice, won_deal, client_details Outputs: client_project, client_account, client_portal, delivery_status Supporting Routes: /admin/client-accounts → /admin/client-projects/{id}/messaging → /client-login → /client-dashboard Note: Activates client project OS, client login, messaging, and delivery tracking.
70	Intelligence	Revenue and Client Intelligence intelligence	`/admin/revenue-intelligence` Route: exists	`revenue_intelligence` Table: review	NEEDS REVIEW
	Inputs: deal_activity, payment_activity, client_signal, delivery_activity Outputs: recommendation, alert, executive_summary, action_suggestion Supporting Routes: /admin/ai-suggestions → /admin/client-signals → /admin/eaf-conversion-suggestions → /admin/executive-dashboard Note: Reads platform signals and produces advisory intelligence.
80	Governance	Platform Governance and Health governance	`/admin/platform-discovery` Route: exists	`platform_flow_registry` Table: exists	WIRED
	Inputs: routes, controllers, tables, views, permissions, health_checks Outputs: health_status, attention_items, readiness_state, governance_report Supporting Routes: /admin/route-governance → /admin/system/health → /admin/rbac → /admin/security-command → /admin/operations Note: Keeps the platform stable, truthful, auditable, and launch-ready.