Ingestion flow
Import -> parse -> review -> accept/reject -> KBM promotion. Default trust state is needs review.
Local release review
Public alpha review cockpit
Review real release routes, mobile-critical surfaces, accessibility checks, and route health without claiming certification or fabricated operational state.
14
Routes
14
Passing
0
Warnings
13
Mobile critical
11
Scenarios
9
Workspaces
8
Topology nodes
6
Topology edges
RoutesOpen review surfaceComponentsOpen review surfaceAccessibilityOpen review surfaceMobileOpen review surfaceRuntime previewsOpen review surfaceTopologyOpen review surfaceDesign systemOpen review surfaceTokensOpen review surfaceTypographyOpen review surfaceRuntime statesOpen review surfaceWorkspacesOpen review surfaceLanguageOpen review surfaceSemanticsOpen review surfaceCompletionOpen review surfaceCapturesOpen review surfaceRuntime stateOpen review surface
Mobile-critical routes
publicPublic home/tlpTLP public/tlptlpTLP dashboard/tlp/dashboardtlpTLP Sound Studio/tlp/studios/soundtlpTLP Video Studio/tlp/studios/videotlpTLP VFX Studio/tlp/studios/vfxradioRadio public/radioradioRadio library/radio/libraryradioRadio unlock/radio/unlockmaataaMaataa Runtime/maataamaataaStatus Matrix/statusmaataaStatus Matrix cards/status/matrixreviewRelease review/review
KBM trust preview
Accepted artifacts can become evidence-backed memory. Rejected or unreviewed artifacts remain outside trusted answers.
Desktop preview
Maataa Desktop is the primary standalone workstation for ingestion, KBM review, TLP sessions, Radio release prep, Ayodhya Studio, diagnostics, and evidence.
Mobile preview
Mobile is field runtime: approvals, quick review, cached playback, production updates, and offline recovery.
Offline-state preview
Queue, cache, local media, conflict, and storage state must remain visible. Web indicators are contract snapshots unless backed by a live endpoint.
Topology preview
The architecture order is Offline Core -> Standalone Runtime -> Mobile Field Runtime -> Web Distribution.
Runtime simulator
Operational scenario previews
These are explicit preview states, not production telemetry. Operators use them to review offline, sync, ingestion, rollback, mobile, and distribution behavior before field sessions.
Healthy runtime
All core preview signals are nominal.
Degraded runtime
Runtime is usable but has reviewable warnings.
Offline runtime
Local-only runtime with queued actions visible.
Overloaded queue
Queue growth requires operational review.
Replay failure
Evolution replay evidence blocks promotion.
Sync conflict
Manual conflict resolution is required.
Rollback required
Release governance requires rollback review.
Ingestion overload
Review queue is overloaded and KBM promotion must wait.
Unsigned alpha
Unsigned desktop build is allowed only for controlled alpha.
Topology preview
Runtime relationships
offline-core
Offline Core
storage, queue, cache, events
offline-core
Sync Engine
mutations, conflicts, checkpoints
standalone
Maataa Desktop
workspaces, ingestion, review, diagnostics
standalone
KBM
reviewed-memory, evidence-graph
standalone
Runtime Evolution
proposals, replay, approval
standalone
Status Matrix
health, history, distribution-state
mobile-field
Mobile Field Runtime
approvals, field-updates, cached-playback
web-distribution
Web Distribution
discovery, pricing, public-status
Workspace review
Preview coverage
Runtime Control Centerstandalone
Local orchestration state remains inside the standalone runtime.
Evolution Workspacestandalone
No proposal may promote without human approval.
Ingestion Workspacestandalone
Imported records default to needs_review before KBM promotion.
KBM Review Workspacestandalone
KBM memory accepts reviewed evidence only.
TLP Operationsstandalone
Production sessions persist locally before any sync.
Radio Release Workspacestandalone
Release metadata and media cache state are visible before publishing.
Ayodhya Studio Workspacestandalone
Workstation media operations remain local-first.
Distribution Workspacestandalone
Unsigned alpha updates are visible and blocked from silent install.
Rollback Workspacestandalone
Rollback requires evidence, affected surface notes, and operator approval.