Cernion Grid Intelligence

It is not just a chat frontend for energy APIs. The current platform contains:

- 138 Moleculer servicesinservices/
- 1007 OpenAPI pathsinopenapi-export.json
- 304 JavaScript test filesundertests/
- curated Copilot, Sidecar, OpenWebUI, n8n and OpenClaw integration surfacesthat expose only governed subsets of the backend
- agentic runtime componentsfor routing, receipts, dossiers, HITL, evidence, revalidation and observability

Cernion does not let the chat decide. The platform structures the objective, available data, service chain, evidence, gaps, risk and the next safe gate. The result is not a black-box answer, but a dossier-ready status or decision-readiness view for Stadtwerke, distribution-system operators and energy-service teams.

Cernion Energy Tools is not an automatic contract decision, grid-connection commitment, device-control system, MaKo execution system, billing/settlement system or tariff-mutation machine. Suitable integration scopes areask,plan,evidence,capability lookupandread-only status. Write-like or consequential steps stay indraft,prepareorpending confirmationstates and require HITL.

The public website explains Cernion as an energy-intelligence and decision platform for Stadtwerke: MaStR analysis, grid planning, §14a, Redispatch, Energy Sharing, customer-service automation and Microsoft Copilot complementarity. This repository is the deeper technical system underneath that product narrative.

Cernion is API-first, but the API is only the integration layer. The agentic part is the runtime behavior:
- Understand an energy-domain objectiveExamples: validate a grid-connection scenario, build a VDMI responsibility matrix, assess BESS finance risk, identify Energy Sharing data conflicts.
- Select a governed capability pathThecapability-brokermaps intent to curated service chains instead of exposing the full tool catalogue to an LLM.
- Execute deterministic microservicesEnergy-domain calculations and regulatory checks remain code-backed and reproducible.
- Maintain process statePersonal-agent sessions, receipts, dossiers, HITL items and object-store evidence allow work to continue beyond a single chat turn.
- Produce auditable artifactsOutputs are not only natural-language answers; they include dossiers, evidence packages, decision frames, validation reports, receipts and traces.
- Govern revalidationNew facts can become control signals for agents: if a MaStR asset, datapoint or object-store evidence item changes, dependent decisions can be identified and rechecked.

This is the practical difference between a question-and-answer bot and an agentic energy-operations platform.

External systems / humans / agents | v REST API, Copilot API, OpenClaw Sidecar, MCP-like tool surfaces | v Personal Agent / Capability Broker / Agent Receipts / Blueprints | v Governed Moleculer services | v Datapoints, Object Store, Knowledge RAG, Dossiers, Jobs, Observability

The platform covers several energy-industry work areas. The following list is representative; the OpenAPI export is the source of truth.

services/personal-agent.service.jsis the user-facing orchestration layer. It keeps conversation state, routes intents, calls deterministic services and synthesizes results without turning the whole backend into one prompt.

- layered context management ("Zwiebelmodus")
- durable execution state and resumable sessions
- file and datapoint intake
- evidence-gap handling
- work-out-loud events
- presentation-aware final artifacts

services/capability-broker.service.jsandsrc/capability-catalog.jsprovide curated capability routing. This is the control point that prevents agents from seeing or choosing the entire backend surface directly.

Examples of curated capabilities include:

- vdmi_role_boundary_governance
- vdmi_asset_validation_governance
- vdmi_grid_connection_decision_governance
- netzfahrplan_fnav_assessment
- znp_portfolio_assessment
- settlement_a96_reconciliation
- financier_due_diligence_assessment
- reporting_governance

services/agent-receipts.service.jsturns repeatable agent workflows into versioned, testable recipes. Receipts describe matching conditions, required inputs, tool plans and knowledge plans. They are the bridge from "the agent answered" to "the platform selected a governed, inspectable workflow".

Cernion uses dossiers and decision frames for auditable outputs. A result can include:

- facts used
- hypotheses
- evidence gaps
- risks
- forbidden assumptions
- VDMI responsibilities
- next actions
- human-review requirements

Two active architecture tracks are captured in GitHub issues:

The target direction is that a changed fact can become a control signal for agents:

MaStR / datapoint / object-store change | v Dependency and impact analysis | v Revalidation queue | v Agent receipt / capability flow rerun | v Audit note, updated dossier, HITL item or exception case

This is how Cernion moves from one-time API analysis toward RPA+ for commodity energy processes: standard cases are automated, exceptions are made explicit.

The complete REST API is generated from Moleculer service metadata.

The recipes use only synthetic examples, environment-variable based tokens and tenant-safe demo identifiers. They document consultation/read-only/pending-confirmation boundaries and are not approval, billing, tariff, device-control, contract or production-mutation demos.

npm run export:openapi npm run audit:openapi

Cernion does not expose all 600+ API paths to Microsoft Copilot. The Copilot bridge uses a curated allowlist maintained inconfig/copilot-operations.json.

The Copilot-facing surface distinguishes:

- readoperations with no side effects
- draftoperations that prepare suggestions
- prepareoperations requiring confirmation
- consequential operations that remain blocked until explicitly governed

openclaw plugins install clawhub:@cernion/openclaw-energy-tools-sidecar

The product boundary is intentionally split: OpenClaw is the agent runtime for conversation, tool orchestration, memory and answer synthesis. Cernion Energy Tools is the energy-domain evidence, policy, Knowledge RAG and read-only API layer behind answers about MaStR assets, grid context, Redispatch, Zielnetzplanung, 14a/14d EnWG duties, process intake and operational status.

The sidecar consumes the Cernion Sidecar contract:

npm test npm run test:unit:ci npm run test:tdd-matrix npm run test:rest-usecases npm run lint npm run audit:openapi npm run check:llm npm run release:check

npm run export:openapi npm run export:openapi:copilot npm run generate:llm npm run blueprint:export

Good demos should show anagentic run, not only a chat answer.

- VDMI: generate a responsibility matrix per process step and detect role-boundary violations
- BESS: assess a site across grid connection, risks, revenue assumptions and financier evidence
- Energy Sharing: identify MaLo/MeLo, EDM and settlement conflicts that block the process
- MaStR/Revalidation: show how an external asset update can trigger rechecking of dependent decisions
- Copilot/Sidecar: show Cernion as the governed energy-domain backend behind a general-purpose agent

A useful agentic trace should make these visible:

User objective -> intent and capability -> selected receipt / blueprint -> service chain -> evidence used -> gaps and risks -> HITL / policy decision -> dossier or decision artifact -> audit trace

Chia Health MCP Server — Patient workflow integration for a licensed US telehealth platform. Browse GLP-1 medications (semaglutide, tirzepatide), peptide therapies (sermorelin, NAD+, glutathione), and longevity treatments. Check eligibility, complete intake, sign consents, and manage treatment plans. 30 tools, HIPAA-compliant. All prescriptions evaluated by licensed US healthcare providers and delivered from FDA-regulated pharmacies across 50 states + DC.

Broker + MCP server for last-bidder-wins games on Solana — agents register, auto-fund a Privy wallet, and bid via streamable HTTP

AI-powered no-code app builder with 17 MCP tools — create projects, generate pages from natural language, AI text/image generation (GPT, Claude, Gemini, 14+ models), page CRUD, workflow execution, publish & version control. SSE transport, API key auth.

An mcp server for your food ordering needs.

Agent-to-Agent handoff certification for multi-agent systems — validates context preservation, verifies agent capabilities before handoff, logs transfer chains, and ensures no data loss in agent orchestration.

Unified MCP & skill management gateway with progressive disclosure. Manages multiple MCP servers as Agent Apps, loading tool schemas on demand for 99% context token savings. Shared across Claude Code, Codex, OpenCode and more.

A collection of Model Context Protocol (MCP) servers for various tasks and integrations, supporting both Python and Node.js environments.

Open-souSecurely feeds real security refreshed rules into Cursor, Claude Code, and Windsurf — zero config, no API key.

Health intelligence MCP — access biomarkers, biological age, and personalized longevity action plans from your Aniva profile.