Platform

Identity, trust, and federated services for the M7 stack.

The platform is the shared foundation underneath the tools and services. id.m7 establishes the root identity, user.m7 binds that identity to a user or organization, and the DB and Files services stay inside the same trust model.

  • Identity begins with UUIDs and credentials.
  • User records attach roles, organization context, and login state.
  • Services stay federated so access stays predictable.

Identity

UUIDs and credentials

User

Roles and org context

Services

DB, Files, federation

Wiring

How the platform fits together

These pages are the foundation layer for the M7 federation. The details will grow over time, but the shape stays simple: identity first, user binding next, then shared services like DB and Files.

ID

Root identity starts here with UUIDs, credentials, and the first trust boundary.

User

User-facing identity binding, roles, organization context, and login state live here.

DB

Shared data access stays narrow and inside the trust model instead of leaking everywhere.

Files

Shared file access and delivery stay controlled instead of becoming ad hoc host sharing.

Federation model: use the M7 services directly, or build compatible services that participate in the same trust system.