@cernion/openclaw-energy-tools-sidecar 0.1.0 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +15 -1
- package/README.md +95 -12
- package/dist/index.js +1 -1
- package/docs/POSITIONING.md +86 -0
- package/openclaw.plugin.json +2 -2
- package/package.json +36 -3
package/CHANGELOG.md
CHANGED
|
@@ -2,7 +2,21 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to the Cernion Energy Tools Sidecar for OpenClaw are documented here.
|
|
4
4
|
|
|
5
|
-
## 0.1.
|
|
5
|
+
## 0.1.2 - 2026-06-30
|
|
6
|
+
|
|
7
|
+
- Repositions the package and README around discoverable energy use cases:
|
|
8
|
+
MaStR assets, grid context, Redispatch, ZNP, §14a/§14d, Knowledge RAG,
|
|
9
|
+
process intake, and read-only operational APIs.
|
|
10
|
+
- Adds package keywords and a Sidecar positioning note for ClawHub/npm
|
|
11
|
+
discoverability and follow-up documentation work.
|
|
12
|
+
|
|
13
|
+
## 0.1.1 - 2026-06-25
|
|
14
|
+
|
|
15
|
+
- Adds required ClawHub code-plugin metadata:
|
|
16
|
+
`openclaw.compat.pluginApi` and `openclaw.build.openclawVersion`.
|
|
17
|
+
- Adds `openclaw.runtimeExtensions` pointing at the built runtime entry.
|
|
18
|
+
|
|
19
|
+
## 0.1.0 - 2026-06-25
|
|
6
20
|
|
|
7
21
|
- Initial dedicated Cernion Energy Tools Sidecar package for OpenClaw.
|
|
8
22
|
- Exposes Cernion descriptor, tool-list, provider tool calls, Knowledge RAG, OSM grid context, Evidence Router, process-intake, capability/operation resolution, read-only REST plan execution, and direct read-only Cernion API requests.
|
package/README.md
CHANGED
|
@@ -1,17 +1,100 @@
|
|
|
1
1
|
# Cernion Energy Tools Sidecar for OpenClaw
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
3
|
+
Cernion-backed energy evidence tools for OpenClaw agents: MaStR assets, grid
|
|
4
|
+
context, Redispatch, Zielnetzplanung (ZNP), §14a/§14d EnWG, regulatory
|
|
5
|
+
Knowledge RAG, process intake, and read-only operational APIs.
|
|
6
|
+
|
|
7
|
+
Most users will not search for a "Cernion Sidecar" directly. They usually have
|
|
8
|
+
an energy-domain question and need an agent that can work with evidence instead
|
|
9
|
+
of generic model memory. This plugin is the bridge: OpenClaw provides the agent
|
|
10
|
+
runtime, conversation, tool orchestration, and final answer synthesis; Cernion
|
|
11
|
+
Energy Tools provides the fachliche energy layer, policies, evidence semantics,
|
|
12
|
+
and read-only execution plans.
|
|
13
|
+
|
|
14
|
+
Use it when an OpenClaw assistant should answer questions such as:
|
|
15
|
+
|
|
16
|
+
- "Welche PV-Anlagen, Speicher oder Lasten gibt es in dieser Gemeinde?"
|
|
17
|
+
- "Welche Redispatch-, §14a-, §14d- oder ZNP-Pruefschritte sind relevant?"
|
|
18
|
+
- "Welche Netzbereiche wirken fuer PV, BESS, HPC-Laden oder Waermepumpen kritisch?"
|
|
19
|
+
- "Welche MaStR-, OSM-, Marktpartner-, Last-, CO2- oder Betriebsdaten stuetzen diese Aussage?"
|
|
20
|
+
- "Welche Cernion-Faehigkeit oder API sollte fuer diese Energiefrage genutzt werden?"
|
|
21
|
+
- "Kann ein Prozess vorbereitet werden, ohne ihn schon auszufuehren?"
|
|
22
|
+
|
|
23
|
+
## Who This Is For
|
|
24
|
+
|
|
25
|
+
- Stadtwerke, Verteilnetzbetreiber, Energieberater, Asset-MDM-Teams, grid
|
|
26
|
+
planning teams, Redispatch teams, market-communication teams, and software
|
|
27
|
+
teams building energy-domain assistants.
|
|
28
|
+
- OpenClaw users who want a local/private assistant to use Cernion data and
|
|
29
|
+
policies without copying tokens, business logic, or raw operational context
|
|
30
|
+
into prompts.
|
|
31
|
+
- Cernion users who want a conversational agent surface without moving Cernion's
|
|
32
|
+
capability routing, policy gates, or source-of-truth semantics into OpenClaw.
|
|
33
|
+
|
|
34
|
+
## How OpenClaw And Cernion Work Together
|
|
35
|
+
|
|
36
|
+
| Layer | Responsibility |
|
|
37
|
+
| --- | --- |
|
|
38
|
+
| OpenClaw | Agent runtime, user conversation, memory/workspace instructions, model choice, tool orchestration, answer synthesis, and human-readable explanation. |
|
|
39
|
+
| This Sidecar | Host-side plugin configuration, secret loading, Cernion tool discovery, request validation, token scrubbing, read-only REST plan proxying, and boundary enforcement. |
|
|
40
|
+
| Cernion Energy Tools | Energy-domain capabilities, MaStR and grid evidence, Knowledge RAG, Evidence Router, process-intake policy, capability manifests, and read-only operational APIs. |
|
|
41
|
+
|
|
42
|
+
This split is the product value: OpenClaw can become an energy assistant without
|
|
43
|
+
learning Cernion internals, while Cernion remains the authority for policies,
|
|
44
|
+
evidence semantics, and which operations are safe.
|
|
45
|
+
|
|
46
|
+
## Example Prompts
|
|
47
|
+
|
|
48
|
+
```text
|
|
49
|
+
Mich wuerde interessieren, ob die Gemeinde Meckesheim bereits so viel Erzeugungskapazitaet hat, dass sie sich unter idealen Bedingungen selbst versorgen koennte. Wenn nicht, wie viel Solar muesste zugebaut werden?
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
```text
|
|
53
|
+
Welche Pflichten ergeben sich aus §14a EnWG fuer einen Verteilnetzbetreiber, und welche Cernion-Evidenz sollte ich fuer einen konkreten Fall pruefen?
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
```text
|
|
57
|
+
Ich plane 20 MWp PV, 10 MW / 20 MWh Speicher, 30 HPC-Ladepunkte, 800 Waermepumpen und 1.500 Wallboxen in Sinsheim. Welche Spannungsebenen und Netzbereiche koennten kritisch werden, und welche Evidenz fehlt?
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
```text
|
|
61
|
+
Welche Cernion-Capability passt zu einer Redispatch-Asset-Register-Pruefung, und kann OpenClaw den passenden read-only REST-Plan ausfuehren?
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
## Capabilities At A Glance
|
|
65
|
+
|
|
66
|
+
- Regulatory and procedural knowledge: EnWG, §14a/§14d, BNetzA guidance,
|
|
67
|
+
internal procedures, roles, obligations, and job-help context through Cernion
|
|
68
|
+
Knowledge RAG.
|
|
69
|
+
- Asset and market evidence: MaStR-backed PV, storage, load, market-partner,
|
|
70
|
+
and operational evidence through read-only Cernion APIs.
|
|
71
|
+
- Grid context: OSM-visible substations, transformers, lines, voltage-level
|
|
72
|
+
hints, and topology metrics for ZNP, Netzanschluss, PV/BESS/HPC siting, fNAV,
|
|
73
|
+
and planning hypotheses.
|
|
74
|
+
- Evidence routing: Cernion recommends the safe read-only endpoint and result
|
|
75
|
+
semantics; OpenClaw executes through this Sidecar and synthesizes the answer.
|
|
76
|
+
- Capability resolution: OpenClaw can resolve Cernion capability and operation
|
|
77
|
+
manifests instead of hard-coding domain routing.
|
|
78
|
+
- Process intake: OpenClaw can prepare a pending process receipt through a
|
|
79
|
+
separate token boundary without executing or resolving the process.
|
|
80
|
+
|
|
81
|
+
## Install From ClawHub
|
|
82
|
+
|
|
83
|
+
```bash
|
|
84
|
+
openclaw plugins install clawhub:@cernion/openclaw-energy-tools-sidecar
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
Then configure the Cernion base URL and a read-only token:
|
|
88
|
+
|
|
89
|
+
```bash
|
|
90
|
+
export CERNION_BASE_URL="https://cernion.example"
|
|
91
|
+
export CERNION_READONLY_TOKEN_FILE="$HOME/.config/cernion/readonly-token"
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
See [docker/README.md](docker/README.md) for a browser-based demo container
|
|
95
|
+
that starts OpenClaw with this plugin preinstalled.
|
|
96
|
+
|
|
97
|
+
## Cernion Sidecar Contract
|
|
15
98
|
|
|
16
99
|
The plugin consumes the Cernion Sidecar contract implemented by Cernion Energy Tools:
|
|
17
100
|
|
package/dist/index.js
CHANGED
|
@@ -807,7 +807,7 @@ function scrubSecretValues(value, token) {
|
|
|
807
807
|
export default defineToolPlugin({
|
|
808
808
|
id: "cernion-energy-tools-sidecar",
|
|
809
809
|
name: "Cernion Energy Tools Sidecar",
|
|
810
|
-
description: "
|
|
810
|
+
description: "Give OpenClaw agents Cernion-backed energy evidence for MaStR assets, grid context, Redispatch, ZNP, §14a/§14d, Knowledge RAG, process intake, and read-only operational APIs.",
|
|
811
811
|
configSchema,
|
|
812
812
|
tools: (tool) => [
|
|
813
813
|
tool({
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# Positioning OpenClaw + Cernion Energy Tools Sidecar
|
|
2
|
+
|
|
3
|
+
This document captures how to explain the plugin to users who do not yet know
|
|
4
|
+
that a Cernion/OpenClaw integration exists.
|
|
5
|
+
|
|
6
|
+
## Core Message
|
|
7
|
+
|
|
8
|
+
OpenClaw is the agent runtime. Cernion Energy Tools is the energy-domain
|
|
9
|
+
evidence and policy layer. The Sidecar connects both so an assistant can answer
|
|
10
|
+
energy questions with Cernion-backed evidence instead of generic model memory.
|
|
11
|
+
|
|
12
|
+
Short form:
|
|
13
|
+
|
|
14
|
+
```text
|
|
15
|
+
Give OpenClaw agents Cernion-backed energy evidence: MaStR assets, grid context,
|
|
16
|
+
Redispatch, Zielnetzplanung, §14a/§14d, Knowledge RAG, process intake, and
|
|
17
|
+
read-only operational APIs.
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
## Discovery Problem
|
|
21
|
+
|
|
22
|
+
The expected users usually search for their job problem, not for a "sidecar".
|
|
23
|
+
They may look for:
|
|
24
|
+
|
|
25
|
+
- OpenClaw energy assistant
|
|
26
|
+
- MaStR assistant or MaStR evidence
|
|
27
|
+
- Redispatch agent
|
|
28
|
+
- Zielnetzplanung or ZNP assistant
|
|
29
|
+
- §14a EnWG or §14d EnWG workflow
|
|
30
|
+
- Netzanschluss, PV, BESS, HPC charging, or heat-pump grid context
|
|
31
|
+
- Cernion Knowledge RAG
|
|
32
|
+
- Verteilnetzbetreiber AI assistant
|
|
33
|
+
- Stadtwerke agent
|
|
34
|
+
- energy evidence router
|
|
35
|
+
|
|
36
|
+
Documentation and marketplace copy should put those words near the top.
|
|
37
|
+
|
|
38
|
+
## Audience
|
|
39
|
+
|
|
40
|
+
- Stadtwerke and Verteilnetzbetreiber teams that need grounded answers across
|
|
41
|
+
MaStR, grid planning, Redispatch, regulatory duties, and operational status.
|
|
42
|
+
- Energy consultants and software teams that need an agent interface over
|
|
43
|
+
Cernion capabilities without embedding Cernion tokens or business logic in
|
|
44
|
+
prompts.
|
|
45
|
+
- OpenClaw users who want a local/private energy-domain assistant with tool
|
|
46
|
+
discipline, not a generic chatbot.
|
|
47
|
+
|
|
48
|
+
## OpenClaw/Cernion Split
|
|
49
|
+
|
|
50
|
+
| Part | What to say |
|
|
51
|
+
| --- | --- |
|
|
52
|
+
| OpenClaw | Conversation, model selection, workspace instructions, tool orchestration, memory, and final answer synthesis. |
|
|
53
|
+
| Sidecar | Plugin configuration, token loading, request validation, token scrubbing, safe proxying, and tool surface inside OpenClaw. |
|
|
54
|
+
| Cernion Energy Tools | Energy capabilities, policies, Knowledge RAG, Evidence Router, MaStR/grid/market data semantics, and read-only operational APIs. |
|
|
55
|
+
|
|
56
|
+
The product promise is not "install another API wrapper". The promise is:
|
|
57
|
+
OpenClaw can become a fachlich disciplined energy assistant while Cernion stays
|
|
58
|
+
the source of truth for evidence, routing, and policy gates.
|
|
59
|
+
|
|
60
|
+
## Documentation Improvements Already Applied
|
|
61
|
+
|
|
62
|
+
- Rewrote the README opening so the first screen names the actual user problems:
|
|
63
|
+
MaStR, grid context, Redispatch, ZNP, §14a/§14d, Knowledge RAG, process
|
|
64
|
+
intake, and read-only operational APIs.
|
|
65
|
+
- Added "Who This Is For", "How OpenClaw And Cernion Work Together", example
|
|
66
|
+
prompts, and capability bullets before the low-level endpoint contract.
|
|
67
|
+
- Added a ClawHub install command near the top.
|
|
68
|
+
- Expanded `package.json` keywords so package registries and marketplace search
|
|
69
|
+
have energy-domain terms to index.
|
|
70
|
+
- Updated plugin/package descriptions away from "Dedicated sidecar" toward the
|
|
71
|
+
actual outcome.
|
|
72
|
+
|
|
73
|
+
## Recommended Next Moves
|
|
74
|
+
|
|
75
|
+
- Republish a patch version so ClawHub and npm show the new description and
|
|
76
|
+
keywords in their metadata.
|
|
77
|
+
- Add one short demo GIF or screenshot to the README showing a real
|
|
78
|
+
Cernion-backed answer in OpenClaw Control UI.
|
|
79
|
+
- Publish a short "OpenClaw energy assistant with Cernion" guide that starts
|
|
80
|
+
from one concrete use case, for example Meckesheim self-supply, §14a duties,
|
|
81
|
+
or ZNP siting for PV/BESS/HPC.
|
|
82
|
+
- Link the ClawHub package from Cernion Energy Tools documentation under
|
|
83
|
+
"Agent integrations", not only from the Sidecar repository.
|
|
84
|
+
- Create issue/discussion templates for three discovery paths:
|
|
85
|
+
"I have an energy question", "I have a Cernion instance", and "I want to
|
|
86
|
+
build an OpenClaw energy assistant".
|
package/openclaw.plugin.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "cernion-energy-tools-sidecar",
|
|
3
3
|
"name": "Cernion Energy Tools Sidecar",
|
|
4
|
-
"description": "
|
|
5
|
-
"version": "0.1.
|
|
4
|
+
"description": "Give OpenClaw agents Cernion-backed energy evidence for MaStR assets, grid context, Redispatch, ZNP, §14a/§14d, Knowledge RAG, process intake, and read-only operational APIs.",
|
|
5
|
+
"version": "0.1.2",
|
|
6
6
|
"configSchema": {
|
|
7
7
|
"type": "object",
|
|
8
8
|
"properties": {
|
package/package.json
CHANGED
|
@@ -1,7 +1,30 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cernion/openclaw-energy-tools-sidecar",
|
|
3
|
-
"version": "0.1.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.1.2",
|
|
4
|
+
"description": "Cernion energy evidence tools for OpenClaw agents: MaStR assets, grid context, Redispatch, ZNP, §14a/§14d, Knowledge RAG, and read-only operational APIs.",
|
|
5
|
+
"keywords": [
|
|
6
|
+
"openclaw",
|
|
7
|
+
"cernion",
|
|
8
|
+
"energy",
|
|
9
|
+
"energy-tools",
|
|
10
|
+
"grid-planning",
|
|
11
|
+
"netzplanung",
|
|
12
|
+
"zielnetzplanung",
|
|
13
|
+
"znp",
|
|
14
|
+
"redispatch",
|
|
15
|
+
"mastr",
|
|
16
|
+
"ma-st-r",
|
|
17
|
+
"enwg",
|
|
18
|
+
"14a",
|
|
19
|
+
"14d",
|
|
20
|
+
"photovoltaic",
|
|
21
|
+
"pv",
|
|
22
|
+
"bess",
|
|
23
|
+
"grid-context",
|
|
24
|
+
"knowledge-rag",
|
|
25
|
+
"evidence",
|
|
26
|
+
"sidecar"
|
|
27
|
+
],
|
|
5
28
|
"type": "module",
|
|
6
29
|
"license": "Apache-2.0",
|
|
7
30
|
"repository": {
|
|
@@ -23,6 +46,7 @@
|
|
|
23
46
|
"dist",
|
|
24
47
|
"scripts",
|
|
25
48
|
"docker",
|
|
49
|
+
"docs",
|
|
26
50
|
"openclaw.plugin.json",
|
|
27
51
|
"README.md",
|
|
28
52
|
"CHANGELOG.md",
|
|
@@ -44,7 +68,16 @@
|
|
|
44
68
|
"openclaw": {
|
|
45
69
|
"extensions": [
|
|
46
70
|
"./dist/index.js"
|
|
47
|
-
]
|
|
71
|
+
],
|
|
72
|
+
"runtimeExtensions": [
|
|
73
|
+
"./dist/index.js"
|
|
74
|
+
],
|
|
75
|
+
"compat": {
|
|
76
|
+
"pluginApi": ">=2026.6.11-beta.1"
|
|
77
|
+
},
|
|
78
|
+
"build": {
|
|
79
|
+
"openclawVersion": "2026.6.11-beta.1"
|
|
80
|
+
}
|
|
48
81
|
},
|
|
49
82
|
"publishConfig": {
|
|
50
83
|
"access": "public"
|