d4e72f280e
- Delete .mcp.json + .claude/rules/repo-mem.md; drop .repo-mem from .gitignore - Remove repo-mem / substrate_score / repo_search references from all .md - Move 15 EVOLV skills from .agents/skills/ to .claude/skills/ so they are auto-discovered by the Claude Code harness and invokable via the Skill tool - Retire .agents/skills/evolv-orchestrator (duplicate of the subagent at .claude/agents/evolv-orchestrator.md); orchestrator lives as a subagent only - Drop OpenAI-format agent yaml metadata from each skill (not needed for CC) - Update CLAUDE.md, CONTRACTS.md, AGENTS.md to point at the new locations and disambiguate skills (.claude/skills/) vs subagents (.claude/agents/) - Fix CLAUDE.md tick-loop wording (opt-in per-node, not a fixed 1000ms) - Widen .claude/rules/ paths frontmatter so node-architecture and telemetry rules trigger on more relevant files; add frontmatter to flow-layout rule - Bump CONTRACTS.md review date to 2026-05-19; add step 7 to the contract- change workflow (review example flows when topic usage changes) - Bump nodes/generalFunctions pin (Home.md substrate_score reference removed) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
54 lines
2.0 KiB
Markdown
54 lines
2.0 KiB
Markdown
---
|
|
name: evolv-telemetry-analytics-dashboards
|
|
description: Design telemetry-to-dashboard contracts for EVOLV operations analytics. Use when defining KPI semantics, chart/topic contracts, aggregation windows, operator diagnostics, and compatibility between node outputs, Influx schema, and dashboard consumers.
|
|
---
|
|
|
|
# EVOLV Telemetry Analytics Dashboards
|
|
|
|
## Mission
|
|
Keep EVOLV telemetry contracts stable, queryable, and useful for operators and performance analysis.
|
|
|
|
## Harness Execution Contract
|
|
- Start from current output payloads, Influx schema assumptions, and dashboard queries.
|
|
- Define invariants before edits:
|
|
- KPI semantics remain explicit and comparable over time
|
|
- topic/field naming stability is preserved or migrated
|
|
- dashboard failure modes are diagnosable
|
|
- Validate with query-level and chart-level evidence.
|
|
|
|
## Scope
|
|
- Node outputs in `nodes/*/src/nodeClass.js`
|
|
- Influx-related contract points and dashboard config/manuals
|
|
- FlowFuse chart usage and topic/category consistency
|
|
|
|
## Workflow
|
|
1. Inventory KPI producers and consumers.
|
|
2. Define measurement/tag/field/topic contracts.
|
|
3. Validate aggregation/downsampling assumptions.
|
|
4. Ensure chart wiring remains consistent (`msg.topic` category baseline).
|
|
5. Verify operator readability and anomaly visibility.
|
|
|
|
## Standards
|
|
- Keep KPI definitions versioned and unambiguous.
|
|
- Preserve backward compatibility for released dashboards.
|
|
- Avoid overloading fields with mixed semantics.
|
|
- Pair every contract change with migration notes.
|
|
|
|
## Test Expectations
|
|
Cover:
|
|
- payload field presence/types for key KPIs
|
|
- topic/category compatibility for charts
|
|
- query compatibility for existing dashboards
|
|
- behavior under missing/null data windows
|
|
|
|
## Deliverables
|
|
Return:
|
|
- KPI and telemetry contract map
|
|
- changed files/tests and dashboard impact notes
|
|
- migration/deprecation notes if compatibility changed
|
|
|
|
Decision interview triggers:
|
|
- KPI definition changes affecting reporting decisions
|
|
- dashboard contract breaks requiring migration
|
|
- retention/aggregation changes impacting trend interpretation
|