← All documentsMAIA — Where the Apps Are Designed
v:4d5e6f
Overview
Guinness Platform · Internal

MAIA — Where the Apps Are Designed

1
MAIA — Where the Apps Are Designed1 / 5  ·  v:4d5e6f

The workbench behind the platform

Design-time hands off to run-timeMAIAdesign the capabilityAirlockrun the capabilityfinished designinternal · designinternal · runtime
2
MAIA — Where the Apps Are Designed2 / 5  ·  v:4d5e6f

Design-time, not run-time

  • MAIA is where a capability is shaped and described.
  • Airlock is where that capability actually runs.
  • MAIA hands a finished design to the runtime.
3
MAIA — Where the Apps Are Designed3 / 5  ·  v:4d5e6f

Why it exists

  • Keeps app definitions consistent across the platform.
  • One place to specify a tool before it ships.
  • Lets the client-facing apps stay clean and focused.
4
MAIA — Where the Apps Are Designed4 / 5  ·  v:4d5e6f

For the team

  • MAIA is internal — most users never see it; it explains how the apps they use get built.
5
MAIA — Where the Apps Are Designed5 / 5  ·  v:4d5e6f

Guinness · Platform briefing

MAIA — Where the Apps Are Designed

Internal · The design-time workbench behind the platform — where new app tools and capabilities are specified before they go live. Not a client-facing app.

The workbench behind the platform#

MAIA is an internal tool. It is the design-time workbench where new app capabilities are specified before they are switched on for users — the part of the platform clients never open directly.

  • Internal tool — not in the client sidebar.
  • Where new app capabilities are designed and specified.
  • The design-time half of the platform.
Design-time hands off to run-timeMAIAdesign the capabilityAirlockrun the capabilityfinished designinternal · designinternal · runtime

Design-time, not run-time#

There are two halves to a capability: designing it, and running it. MAIA is the design half. Airlock is the half that runs the finished design when a user actually uses the feature.

  • MAIA is where a capability is shaped and described.
  • Airlock is where that capability actually runs.
  • MAIA hands a finished design to the runtime.

Why it exists#

Specifying tools in one place keeps every app on the platform consistent, and keeps the client-facing apps clean — the complexity of defining a capability lives in MAIA, not in the app the user sees.

  • Keeps app definitions consistent across the platform.
  • One place to specify a tool before it ships.
  • Lets the client-facing apps stay clean and focused.

For the team#

MAIA is internal. Most users never see it — this guide simply explains where the apps they use are designed before they go live.

↑ ↓ / space to navigate