gridverse-open-low-code-platform-for-cro/MVP_PLAN.md

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.