MIO°Portfolio
Look around

Three Cockpit examples

The Cockpit is MDSL’s working screen. These pages show what its three kinds of viewer would see, so you can picture the products in use. The data is invented and the layout follows the real Cockpit.

cockpitmy digital sovereignty
MIO · portfolio (illustrative)
  • Today
  • Service Desk
  • Fleet & Health
  • Villages
  • Comms & Content
  • People & Access
  • Governance
  • Agentic Centre

Today

A possible portfolio view for a commercial company. Names and most figures are invented; the counts of offerings and distributors reflect the position today.

Needs attention

  • Critical
    A distributor enquiry has waited three days
    Example Advisory Ltd · Service Desk
  • Needs attention
    Qualified stamps used this period: 40
    Example figure · the real Cockpit exposes a per-period qualified-stamp record as an API only, and there is no allowance
  • Lower priority
    One invitation not yet accepted
    Example Trust · Invitations

Across the portfolio

Service Desk

3
open items

Offerings

8
live or available on request

Distributors

0
appointed

Governance

2
human review required

Comms & Content, People & Access, Governance and Agentic Centre are shown as “Arriving in a later build phase” in the real Cockpit too.

cockpitmy digital sovereignty
Distributor · own villages
  • Today
  • Service Desk
  • Villages

Villages

What a distributor would see of the organisations it looks after: their own villages only, and metadata rather than content.

Village™StatusTypeOpen items
Example Rowing Clubactivecommunity0
Example Family Trustactivegovernance1
Example Charitypendingcommunity1 · owner setup

Access windows

No active windows. (A window gives time-limited access to one or more named categories of a village’s material, and is not designed to widen beyond them.)

Provision a Village the distributor looks after

switched off A readiness check exists. It creates no village.

Quota is not shown because the real system has no quota screen: only usage counts exist, in the API. A distributor sees only Today, Service Desk and Villages.

cockpitmy digital sovereignty
Practice · my clients (concept)
  • Today
  • Service Desk
  • Fleet & Health
  • Villages
  • Comms & Content
  • People & Access
  • Governance
  • Agentic Centre

My clients

The single screen an accountant would use to look after many small clients. It would need a rule, agreed with each client, for what the practice may see of their financial records.

ClientRecords being sealedLast invoice sealed
Example Plumbing Ltdyes2 days agoHistory →
Example BakeryyestodayHistory →
Example Society Inc.not yet—Set up →

Add a client Depends on distributor provisioning, which is switched off, and on the access rule above.

What is real today

  • A Cockpit exists and is in use by MDSL, with three scope tiers: platform, distributor and village. The tier follows from the account that signs in, never from anything a visitor can choose on a page. The village tier also needs the Village to switch its cockpit on.
  • The platform and distributor tiers see metadata, not members’ content. The village tier sees what the member’s own role already allows, and nothing more.
  • The Cockpit has a distributor view. Its provisioning action is switched off, and would be switched on at the first real onboarding.
  • The MIO view and the practice console are the two additions planned, drawn here so you can react to them.