High-level health stays visible to the Toura family without granting access to protected system controls.
Welcome to MEL.
Sign in with your Toura identity. Your dashboard, analytics, and workstations are projected from your governed role after authentication.
Good morning.
Your Toura heartbeat is online. Company-wide context is visible here; workstation authority remains role-specific.
Only workstations granted to your role open operational controls. All others remain visible but locked.
Where you can work
Marketplace
Open the shared Marketplace catalog, supplier resources, and your role-based station.
Member Operations
Visible in MEL so you understand the organization; operational controls are not included in your current role.
Partner Operations
Company context remains visible, while Partner workstation authority stays protected.
Economic Operations
Economic and settlement controls require separate explicit authority.
MEL lets the Toura family understand Toura’s heartbeat and growth without converting that visibility into permission. Direct URLs and server-side commands remain independently enforced.
Toura growth at a glance.
Shared, read-only company analytics. These numbers provide company context and never grant operational authority in the underlying domains.
The Toura family can understand company growth and operating posture here. Detailed governance, system assurance, economic controls, and unrelated workstation records remain outside the current role unless explicitly granted.
Company Growth
Account registrations, public Community profiles, Partner activity and recorded Marketplace revenue — each labeled by its true LIVE source.
Accounts, Community & Businesses
Community visibility is separate from registered Passport accounts and business services.
Historical monitoring starts when the first snapshot is saved. Past account closures will not be invented.
Marketplace Revenue & Commission
Gross and net sales patterns from fulfilled modern Marketplace orders
This is not a company-wide profit-and-loss statement.
Network Overview
One member identity, linked business workspaces and permissioned business services. Read-only owner records.
Account Directory
Search members and businesses by name, email, Passport or workspace.
Current workspaces, active Partners and approved Suppliers are the default. Enable historical associations to include archived and non-approved records. All original history remains available in member details.
Registered accounts include anyone with an existing personal login, including the owner and business/team users. Public Community profiles are a different, opt-in group. Historic hard-deletions cannot be reconstructed from the current records. Team and Partner permissions continue to use account IDs, not email addresses.
Good morning, Robert.
Production command center is online. Owner workstations, live operating context, and governed review queues are available from this shell.
LIVE Passport operations
Your LIVE member, Partner and Supplier totals come from the Passport production database. MEL summarizes existing owner queues; legacy Foundation proofs are separate and do not certify transactions.
What Mel is watching
Sign in to load current LIVE account counts.
Financial operations
Marketplace and business-funded rewards from the current LIVE reporting ledger.
Live operating status.
Foundation runtime and owner-session checks, plus separate current member and business counts. A green runtime check does not certify Marketplace, Passport or payments end to end.
What MEL can prove right now
Work that actually needs an operator.
This queue is derived from governed conditions, not notifications. Controlled limitations that require no action remain visible in Pulse without becoming fake work.
Current items
MEL architect review & owner decisions
Every family suggestion is retained. MEL routes the work through governed architect review first; only items requiring Owner authority are promoted into your Needs Attention count.
Known limitations
Businesses waiting for Toura review.
Verify the business before Marketplace tools unlock. Supplier approval does not approve any Marketplace offer.
Supplier applications
This workspace may approve, request changes, or decline a Supplier application only. It cannot approve Marketplace offers, publish inventory, move Points, settle funds, or activate Production authority.
Marketplace Overview
Catalog, orders, supplier results and verified operational records—separated by source and status.
Financial Overview
Consolidated read-only financial reporting across the existing LIVE Passport ledgers.
Sales allocation
Recorded fulfilled ordersSupplier transfer status pending.
Cash & treasury
Provider source pendingProvider freshness and cash availability status pending.
Business-funded Points
Pending Points ledger read.
Partner funding activity pending.
Reconciliation & reserves
STATUS · NOT COMPLETE- Processing & other recorded fees
- —
- Unrestricted operating cash
- Not reconciled
- Tax / refund / emergency reserve
- Not allocated
Unrestricted funds and net profit are not calculated until all outstanding liabilities, fees and expenses are matched. Do not treat Stripe balances as profit.
Source records & reconciliation
LIVE records pendingView detailed financial recordsSee the original figures, partner balances, orders and payout ledger
Stripe balances
Stripe observed: Not refreshed. Do not treat these amounts as business profit.
Business-funded rewards
Funding value is not a member purchase price.
Supplier settlements and commission
Audit-friendly breakdown
Partner Points capacity
| Partner | Remaining capacity | Funding value equivalent |
|---|
Marketplace orders · USD
| Status / method | Orders | Gross | Commission | Supplier amount |
|---|
Supplier payout queue · USD
| Method | State | Count | Value |
|---|
LIVE Passport source observed: Not loaded. Records in other legacy payment systems may not be included in the modern-ledger aggregates. Currency totals are never mixed. No members purchase Points.
Supplier payout queue
| Payment channel | Recorded status | Transfers | Value (USD) |
|---|
Stripe Connect transfers and actual supplier bank deposits are separate stages. This is a read-only ledger status screen, not a payout processor.
Commission by order status
| Status / payment method | Orders | Gross | Commission | Supplier settlement |
|---|
Gross commission is not net profit. Provider processing fees shown above may cover transactions outside the modern Marketplace ledger.
Marketplace transaction status summary
| Status / checkout | Orders | Customer gross | Toura commission | Supplier |
|---|
Partner funding · settled records
| Funding status | Currency | Base amount | Total charged |
|---|
This v1 activity monitor shows grouped source records, not a complete per-event audit feed. Individual member, business and transaction drilldowns are the next audit-hub addition.
Points Monitoring
Partner-funded balances, earned rewards and funding activity recorded in LIVE Passport.
Partner capacity by business
| Partner | Available Points | USD funding equivalent |
|---|
Partners and suppliers fund Point rewards. Members earn and redeem Points; they do not purchase them.
Legacy SINPE verification workstationSeparate Passport DEV workflow — retained for existing bank-verification operations, not production Points metrics
Verify the bank deposit before Points move.
Toura Control Center reviews the private SINPE evidence. Passport DEV remains the canonical funding and Points source of truth.
Bank verification activity
Grand Cajeta authenticates the Toura owner/admin operator and records the human operator identity. A narrow server-side bridge invokes Passport DEV verification. Confirmation can fund only the existing canonical request snapshot; rejection creates zero Points. Production authority remains disabled.
One certification surface for Mel's nervous system.
Brick 074 begins unifying documentary certification, live Sensors, Pulse, Deep Certification, authority boundaries, and release posture across the connected ecosystem. Documentary truth and live runtime proof remain visibly distinct.
Publication, place identity, evidence freshness, and launch data
Waiting for governed release state.
Waiting for canonical place-link readiness.
Waiting for durable evidence freshness.
Waiting for governed inventory classes.
Waiting for connection-health evidence.
Waiting for release-registry posture.
Marketplace content is not public merely because Owner review passed. Passport acknowledgement must complete first, and Explorer visibility remains blocked until a verified canonical place link exists. Durable sensor evidence is shown with freshness, not historical green. Launch records remain non-destructive until their governed classification is explicit.
Sensor → Pulse → Deep Certification
Session-live tripwires
All 15 registered boundary evaluators are probed every 60 seconds while Control Center is open. Automatic probes never write evidence.
Production-safe active proof
Evidence-backed operational health. Green is earned; unknown remains unknown.
Controlled exhaustive testing
Release-level proof across identity, authority, contracts, events, evidence, sensors, regressions, and failure boundaries.
Unified certification matrix
FOUNDATION-ASSURANCE-001
Certified historical records, live Sensor observations, Pulse state, and Deep Certification are different proof classes. Big Mama may unify their presentation, but never converts missing runtime proof into green and never treats documentary certification as current production health.
Parallel development command board.
Owner-only production governance view of active build lanes, deployment HEADs, stale-base protection, and recent coordination events. This surface observes the control registry; it does not deploy code.
Who is building what
What changed
When a registered production candidate HEAD changes, any writable lane still based on an older deploy is automatically marked REBASE REQUIRED. When Mission Control reserves the deploy baton, that lane becomes UP NEXT FOR DEPLOY and all other execution-lane deploy permissions remain blocked until the baton is released.
Workspace
This domain is registered in the global shell but intentionally not activated in Control Center Build Brick 3.
Loading Partner activation events...
Prove health from evidence, not assumption.
Independently evaluate the durable Brick 008 proof and persist one FOUNDATION_INTEGRITY sensor observation. HEALTHY is allowed only when every required Foundation signal has fresh positive evidence; missing evidence remains UNKNOWN and failed required evidence becomes DEGRADED.
This brick does not trust the writer to certify its own truth. A separate server-mediated FOUNDATION_INTEGRITY evaluator reads the authenticated actor, explicit Production capability, Foundation registries, and Brick 008 durable Event/Evidence correlation, applies freshness rules, then may write one Foundation-owned sensor observation. No production, economic, legacy, or business-domain mutation is introduced.
Connect an existing operator.
No account is created here. Use only the existing Production Supabase Auth identity already provisioned for Foundation testing. Authentication proves identity only; authority remains independently governed.
One audited write path. Zero business effect.
The server-mediated proof writes one fixed foundation.authority_checked.v1 event and one linked FOUNDATION_DURABLE_WRITE_PROOF evidence record. RLS binds both records to the authenticated Production actor and existing test capability.
The writer does not certify its own truth.
The independent evaluator requires fresh positive evidence for application, database connectivity, migration state, auth adapter, authority enforcement, contract registry, event path, evidence path, and observability. Missing evidence cannot return HEALTHY.
Rails beneath Mission Control.
Foundation 001R remains observable from the new shell. Verification is safe, production-safe, and has no economic effect.