ACTIVE DEVELOPMENTDESIGN TARGET · STATIC PREVIEWAI orchestration architecture

MellyCore AIOS

An AI orchestration architecture and shared-context command center.

This case study deliberately keeps two evidence layers apart: the current Claude Design Portfolio V1 target and the implemented Cockpit V3.1 static product interface. A design state is never used as implementation proof.

Portfolio maturity

IMPLEMENTED · NOT LIVE

Static cockpit implemented and deployed as a static preview; no live runtime, providers or running agents.

Other labels on this page describe individual surfaces and evidence, not the whole project.

NO LIVE PROVIDERSNO LIVE MODEL OR AGENT EXECUTIONNO LIVE MCP / SKILL / PLUGIN INVOCATIONNO LIVE TELEMETRY

DESIGN TARGET · STATIC PREVIEW · NO CONNECTED LIVE SOURCE

01 · Current Portfolio V1 design target

Claude Design MellyCore AIOS v2 is the current visual target: a near-black, graph-centric command center with Context and Routing on the left, Agents and Observability on the right, and governance workflow below. It is an interactive design artifact driven by seeded fixtures. Its LIVE option demonstrates a read-only adapter seam; no GraphSource is connected.

DESIGN TARGET · STATIC PREVIEW · NO CONNECTED LIVE SOURCE. Claude Design MellyCore AIOS v2, captured directly from the supplied artifact with reduced motion enabled. Prototype statuses and values are design fixtures, not product telemetry or runtime state.

Swipe or use arrow keys to inspect the full design artifact.

Designed workflow · prototype semantics

  1. Context IngestionDesign state
  2. Intent & RoutingDesign state
  3. Skill + ToolDesign state
  4. Approval & GuardrailsHuman gate
  5. Evidence & Audit — key stageDesign state

These stages communicate the intended interaction and governance model. They do not prove a running router, tool, agent, MCP server or audit service.

IMPLEMENTED PRODUCT EVIDENCE · PRODUCTION-DEPLOYED STATIC PREVIEW · EXECUTION LOCKED

02 · Implemented static product

Cockpit V3.1 is the source-backed implementation layer: a real HTML, CSS and JavaScript product interface captured from its production deployment. Its topology is a deterministic repository fixture. Production deployment proves the static interface was served; it does not prove a production runtime.

IMPLEMENTED PRODUCT EVIDENCE · PRODUCTION-DEPLOYED STATIC PREVIEW · EXECUTION LOCKED. Cockpit V3.1, captured 2026-08-17 from the deployed static build at production SHA a43e375. Repository-derived topology; no live providers, models, agents, MCP, skills, plugins or telemetry.

Swipe or use arrow keys to inspect the implemented static interface.

DESIGN SEMANTICS VS IMPLEMENTED TOPOLOGY

03 · Graph and context architecture

The design target contains 39 labelled semantic nodes infive families and 46 typed relationships. Those counts come from the supplied mellycore-graph.js fixture; authored positions keep the composition stable. Search, filtering, keyboard selection, focus, provenance and a textual relationship fallback are design interactions, not evidence of a live source.

Claude Design v2 graph-centered view in Static Preview mode: 39 labelled semantic nodes in five families and 46 typed relationship records, with search, filters, source mode and textual Inspector visible.
DESIGN TARGET · STATIC PREVIEW. Graph-centered capture from Claude Design v2: 39 nodes, five semantic families and 46 typed relationships, derived from the source fixture rather than inferred from the image.
Claude Design v2 selected Policy Enforcer node and Inspector in Static Preview mode, showing fixture provenance, four typed relationships, evidence text and a statement that values are not telemetry.
DESIGN TARGET · SELECTED NODE + INSPECTOR. Policy Enforcer is keyboard-selected; the Inspector exposes fixture provenance and typed relationships and explicitly says the values are not telemetry.

Separately, implemented Cockpit V3.1 renders a repository-derived static topology of 45 nodes, 66 relationships and eight clusters. That implemented topology remains a fixture, not live runtime data.

MellyCore operating loopA closed loop of seven steps: observe, analyse, recommend, approve, implement, validate, record, then back to observe. Approve is the one emphasised step, labelled human in the loop.observeanalyserecommendapproveHUMAN-IN-THE-LOOPimplementvalidaterecord
  1. observe
  2. analyse
  3. recommend
  4. approveHUMAN-IN-THE-LOOP
  5. implement
  6. validate
  7. record
  8. ↺ back to observe

SPECIFICATION ACCEPTED · NOT IMPLEMENTED

04 · Routing and governance

Skill/plugin routing contract v1.2 was independently accepted at specification level by REVIEW-003 at commit ecbdeb5. The review closed the blocking addressability defect and preserved fail-closed Runtime, Framework Bridge and Klaus-consumer boundaries. That sibling review commit is not integrated into the currently checked-out MellyCore branch, so it is cited as branch-local specification evidence rather than canonical runtime state.

Acceptance authorizes no Skill Registry, Plugin Registry, Skill Router, adapter, provider, MCP path or Klaus implementation. Prototype capability labels such as AUTHORIZED, CONNECTED, CONFIGURED, AVAILABLE and UNAVAILABLE below are Claude Design states only.

DESIGN TARGET · STATIC PREVIEW. Graph, capability rail, agents, observability, alerts and governance workflow shown as prototype states. No connected source and no runtime authority are implied.

PUBLIC TRUTH BOUNDARY

05 · Execution boundary

Implemented

  • Cockpit V3.1 static HTML/CSS/JavaScript interface
  • Production-deployed static preview
  • Repository-backed topology and context presentation

Design target

  • Claude Design MellyCore AIOS v2
  • Graph-centric Portfolio V1 direction
  • STATIC/LIVE design-state model with adapter seam

Specification accepted

  • Skill/plugin routing contract v1.2
  • Selection contract only; no routing runtime

NO LIVE PROVIDERSNO LIVE MODEL EXECUTIONNO LIVE AGENT EXECUTIONNO LIVE MCPNO LIVE SKILL / PLUGIN INVOCATIONNO LIVE TELEMETRYNO CONNECTED LIVE GRAPH SOURCE

Animated prototype numbers are demo motion, not telemetry. A LIVE design state is not a connected source. A production-deployed static preview is not a production runtime. A specification-accepted routing contract is not an operational router.

DESIGN WIDTH + IMPLEMENTED MOBILE

06 · Responsive evidence

Design target · 1440-wide rendered capture

DESIGN TARGET · STATIC PREVIEW · NO CONNECTED LIVE SOURCE. Claude Design v2 rendered at a 1440-pixel-wide browser viewport with reduced motion; the captured content area is 1440 × 810.

Implemented product · 390 × 844

Implemented MellyCore AIOS Command Center Cockpit V3.1 at a 390 by 844 phone viewport: static-preview boundaries and context counts, with the repository-derived graph represented as an accessible text list rather than a desktop graph canvas.
IMPLEMENTED PRODUCT EVIDENCE · PRODUCTION-DEPLOYED STATIC PREVIEW. Mobile Cockpit V3.1 keeps truth labels visible and replaces the graph canvas with a text-equivalent list. Execution remains locked.