build(agent): new-agents-3#dd492b iteration

AGENTS.md

@@ -23,7 +23,14 @@ Architecture overview:
 - This skeleton demonstrates verbs for translating contracts to IR, and a small mapper to illustrate adapter wiring without hard coupling to solvers.
 - Use this as a reference when implementing cross-domain adapters and the Adapter Marketplace in Phase 0.
 
-Next steps:
+- Next steps (alignment with MVP plan):
 - Integrate EnergiBridge mappings into the GraphContractRegistry conformance flows.
 - Add lightweight tests for to_ir / from_ir translations.
 - Expand the registry to support per-message metadata for auditability and replay protection.
+- MVP Plan Alignment (8–12 weeks)
+- Phase 0: Protocol skeleton and two starter adapters; minimal ADMM-lite solver; delta-sync seed.
+- Phase 1: Governance ledger scaffold; conformance harness; offline simulations with digital twins.
+- Phase 2: Marketplace scaffolding; minimal codegen path; UI wireframes for graph composition.
+- Phase 3: Hardware-in-the-loop validation across 2–3 devices; KPI dashboards; cross-domain demo.
+- Roles: core protocol work (you), EnergiBridge wiring (me), adapters/marketplace scaffolding (collaborative), governance/audit (joint).
+- Deliverables should be packaged as a publishable MVP with tests passing locally, then signal readiness via READY_TO_PUBLISH.

MVP_PLAN.md

@@ -0,0 +1,34 @@
+# GridVerse MVP Plan (8–12 weeks)
+
+Phase 0 — Protocol skeleton and adapters (0–2 weeks)
+- Define core primitives: Objects, Morphisms, PlanDelta, and contract schemas (0.2).
+- Publish contract schemas and two starter adapters (e.g., DER controller and Building load controller).
+- Build a minimal ADMM-like solver scaffold and delta-sync engine; TLS-ready transport between components.
+
+Phase 1 — Governance and conformance (2–4 weeks)
+- Introduce a governance ledger scaffold and lightweight identity model.
+- Implement a conformance harness to validate adapters against contract schemas.
+- Implement secure delta-sync with bounded staleness for offline/partitioned operation.
+
+Phase 2 — Marketplace and codegen (4–6 weeks)
+- Add adapter marketplace entry points and a minimal codegen path.
+- Provide a reference UI sketch for graph-based device/constraint composition.
+- Extend registry with versioning and per-message metadata for replay protection.
+
+Phase 3 — Cross-domain pilot and HIL (6–12 weeks)
+- Introduce a simulated second domain and demonstrate cross-domain planning.
+- Conduct hardware-in-the-loop validation with 2–3 devices; measure plan quality, convergence, and latency.
+
+Architecture notes (recap)
+- EnergiBridge: Lightweight bridge mapping GridVerse primitives to a vendor-agnostic IR.
+- GraphContractRegistry: Versioned contracts and per-message metadata for auditing.
+- Adapter Marketplace: Starter adapters and marketplace scaffolding.
+- Simulation & HIL: Digital twin support and hardware-in-the-loop testbeds for cross-domain evaluation.
+
+Ownership model (provisional)
+- Core protocol and EnergiBridge wiring: you
+- Registry conformance and adapter conformance tests: me
+- Starter adapters and marketplace scaffolding: you
+- Governance and audit artifacts: joint effort
+
+Note: This plan is a living document and should be updated as milestones are reached and new learnings emerge.

docs/dsl_sketch.md

@@ -1,30 +1,27 @@
-DSL Sketch: LocalProblem -> SharedVariables -> PlanDelta
+# GridVerse DSL Sketch
 
-- LocalProblem (Object) represents a device/problem instance with attributes like id, name, and data.
-- SharedVariables (Morphism-like channel) captures signals shared across locals, with a versioned schema.
-- PlanDelta (Delta) captures changes to local plans to reconcile with the global objective.
-- Minimal DSL flavor (pseudocode):
+This document provides a lightweight, vendor-agnostic DSL seed to bootstrap interoperability between LocalProblems, SharedVariables, and PlanDelta. It is intended for MVP prototyping and should map cleanly to the existing GridVerse core contracts and EnergiBridge translations.
 
-```
-LocalProblem {
-  id: string
-  name: string
-  data: dict
-}
+## Core concepts (seed mapping)
+- LocalProblem: domain-specific optimization task at a site
+- SharedVariables: signals/priors used to inform optimization
+- PlanDelta: incremental changes to the plan with timestamp and author
+- Canonical IR: EnergiBridge-like bridge payloads consumed by adapters and solver
 
-SharedVariables {
-  src: string
-  dst: string
-  version: string
-  schema: dict
-}
+## Simple DSL syntax (example)
+- site_id=site-A
+- description=District cooling optimization
+- variables=cooling_setpoint=22.5,heat_pump_on=true
 
-PlanDelta {
-  plan_id: string
-  delta: dict
-  timestamp: int
-}
-```
+Parsed representation (conceptual):
+- LocalProblem(site_id="site-A", description="District cooling optimization", variables={...})
+- SharedVariables(signals={}, version=1)
+- PlanDelta(delta_id="pd-01", changes={}, timestamp=...)
 
-- Adapters implement a mapping from a device-specific representation into the canonical LocalProblem/SharedVariables/PlanDelta contracts.
-- The registry stores the contract schemas and their versions to enable conformance checks for adapters.
+## Intended workflow
+- DSL text -> LocalProblem/SharedVariables via dsl.parse_local_problem_from_dsl
+- Convert to canonical bundle via dsl.dsl_to_canonical_bundle (which uses EnergiBridge under the hood)
+- Feed into GraphContractRegistry and Adapter Marketplace for downstream solving and adaptation
+
+Notes
+- This is a seed sketch; follow-up enhancements should include richer parsing, error handling, and end-to-end tests.