COMPANY HEARTBEATREAD ONLY
♥
CHECKINGGOVERNED OPERATIONAL HEALTH
High-level health stays visible to the Toura family without granting access to protected system controls.
♥
MEL · FAMILY ACCESS
Checking MEL heartbeat…Welcome to MEL.
Sign in with your Toura identity. Your dashboard, analytics, and workstations are projected from your governed role after authentication.
Role-aware accessMEL shows the company heartbeat and shared company analytics to authenticated members of the Toura family. Workstation controls activate only when your current role has explicit authority.
MEL · FAMILY HOME
Good morning.
Your Toura heartbeat is online. Company-wide context is visible here; workstation authority remains role-specific.
ROLEFAMILY MEMBERMEL access projection
COMPANY GROWTH
—MEMBERS
—PARTNERS
MY ACCESSROLE BASED
1ACTIVE WORKSTATIONOnly workstations granted to your role open operational controls. All others remain visible but locked.
MY WORKSTATIONS
Where you can work
MARKETPLACE
OPEN
Marketplace
Open the shared Marketplace catalog, supplier resources, and your role-based station.
MEMBERS
LOCKEDMember Operations
Visible in MEL so you understand the organization; operational controls are not included in your current role.
PARTNERS
LOCKEDPartner Operations
Company context remains visible, while Partner workstation authority stays protected.
POINTS / FINANCE
LOCKEDEconomic Operations
Economic and settlement controls require separate explicit authority.
Visibility is not 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.
MEL · COMPANY ANALYTICS
Toura growth at a glance.
Shared, read-only company analytics. These numbers provide company context and never grant operational authority in the underlying domains.
What this page is for
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.
GLOBAL COMMAND
Good morning, Robert.
Production command center is online. Owner workstations, live operating context, and governed review queues are available from this shell.
ENVIRONMENTPRODUCTIONLIVE
MEL · GOVERNED INTELLIGENCEOBSERVING
Canonical rails are holding.
No critical conditions are currently known. MEL is the governed assistant for current operating context, review queues, and role-authorized decisions.
MEL OPERATING STATUS
♥
—AUTHENTICATED PRODUCTION HEALTH
Foundationproduction connection
Owner SessionAAL2 governed access
Marketplacegoverned workstation
NEEDS ATTENTION
0PRIORITY / ACT NOWMaterial conditions requiring prompt review
0STANDARD ATTENTIONReviewable conditions that are not urgent
LIVE ECOSYSTEM
What Mel is watching
ECOSYSTEM LAYERS
Inspect the nervous system
MEL · PRODUCTION STATUS
Live operating status.
Current Control Center health and governed Member/Partner operating readbacks. Historical certification fixtures are no longer part of the Production operator view.
CURRENT STATEUNKNOWNAwaiting evidence
ACTIVE SCOPEFOUNDATION + 2Foundation · Members · Partners
FRESHNESSUNKNOWNDerived from last verified health snapshot
ACTIONABLE0Conditions requiring operator action
LIVE OPERATING SIGNALS
What MEL can prove right now
NEEDS ATTENTION
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.
OPERATOR QUEUE
Current items
MEL · MARKETPLACE FEEDBACK
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.
CONTROLLED / NON-ACTIONABLE
Known limitations
SUPPLIERS · APPLICATION REVIEW
Businesses waiting for Toura review.
Verify the business before Marketplace tools unlock. Supplier approval does not approve any Marketplace offer.
OPERATOR QUEUE
Supplier applications
Loading canonical Supplier applications…
Authority boundary
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.
POINTS · SINPE BANK VERIFICATION
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.
SINPE REVIEW & HISTORY
Bank verification activity
Loading canonical SINPE applications…
Authority boundary
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.
BIG MAMA · UNIFIED ASSURANCE
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.
ECOSYSTEM CERTIFICATIONCONNECTED / CERTIFIEDCertified records across the currently connected nervous-system layers
CERTIFIED LAYERS15Documentary certification records preserved
LIVE SENSOR PROOF0Current healthy GET-only sensor evaluations in this browser session
ASSURANCE BLOCKERS0No known certification blocker is being hidden
CROSS-SYSTEM GOVERNANCE
Publication, place identity, evidence freshness, and launch data
PASSPORT PUBLICATIONCHECKINGReading downstream acknowledgement truth.
EXPLORER VISIBILITYCHECKINGCanonical place identity is a separate gate.
DURABLE SENSOR EVIDENCECHECKINGHistorical observations are not treated as current.
LAUNCH DATACHECKINGReference, archive, and readiness classes remain explicit.
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.
Governance doctrine
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.
THREE-LAYER ASSURANCE
Sensor → Pulse → Deep Certification
SENSORS
REGISTEREDSession-live tripwires
All 15 registered boundary evaluators are probed every 60 seconds while Control Center is open. Automatic probes never write evidence.
PULSE
FOUNDATION LIVEProduction-safe active proof
Evidence-backed operational health. Green is earned; unknown remains unknown.
DEEP CERTIFICATION
CERTIFIED RECORDSControlled exhaustive testing
Release-level proof across identity, authority, contracts, events, evidence, sensors, regressions, and failure boundaries.
CONNECTED ECOSYSTEM
Unified certification matrix
FOUNDATION DEEP CERTIFICATION
FOUNDATION-ASSURANCE-001
FOUNDATION CERTIFICATIONNOT RUNCurrent-browser runtime proof is evaluated independently from documentary certification.
AUTOMATED PASS0Checks proved by current runtime evidence
BLOCKED0Required prerequisites currently unavailable
MANUAL0Human validation required
Big Mama doctrine
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.
MEL · BUILD CONTROL
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.
LIVE · 1s
ACTIVE LANES
Who is building what
RECENT CONTROL EVENTS
What changed
Loading recent activity…
Deployment guard
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
Workspace
This domain is registered in the global shell but intentionally not activated in Control Center Build Brick 3.
SYSTEMS · BRICK 010
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.
PRODUCTION CONNECTIONCHECKINGBrick 005.2 connection proof remains prerequisite evidence
OPERATOR IDENTITYCHECKINGBrick 006 authenticated session required
TEST AUTHORITYCHECKINGExplicit Production capability grant must be independently proved
INTEGRITY SENSORCHECKINGIndependent FOUNDATION_INTEGRITY observation must be proved
Brick 009 boundary
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.
External Production connectionPROVEDRead-only Foundation Production connection remains proved.
Production operator identityCHECKINGResolving authenticated Brick 006 session.
Explicit production authorityNOT PROVEDAuthority must come from the Foundation capability registry, never browser state.
Durable Foundation evidence writeCHECKINGInspecting the dedicated Production persistence policy without writing.
Foundation Integrity Sensor observationCHECKINGInspecting the Brick 009 sensor policy without writing.
PRODUCTION IDENTITY
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.
DURABLE FOUNDATION EVIDENCE
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.
Checking the Foundation-only persistence migration and authenticated authority gate…
FOUNDATION INTEGRITY SENSOR
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.
Checking the Brick 009 sensor observation migration and evidence prerequisites…
FOUNDATION INTEGRITY
Rails beneath Mission Control.
Foundation 001R remains observable from the new shell. Verification is safe, production-safe, and has no economic effect.
FOUNDATION STATEUNKNOWNAwaiting verification
EXTERNAL PERSISTENCECHECKINGFoundation-only production path
CONTRACT REGISTRY
SESSION EVIDENCE