HelioVerity Pilot

The description states that HelioVerity Pilot is an "evidence-driven monitoring and early-prevention prototype for small and medium mixed-vendor solar systems." It supports two operating modes:

• Permanent monitoring and early prevention — collecting synchronized operational evidence, checking data quality, comparing measurements, and identifying patterns.
• Pre-service diagnostic recording — producing a high-detail technical record before a service visit to help technicians prepare.

It is designed for use with mixed-vendor systems (e.g., Growatt inverter + JK BMS batteries), using three architectural layers:

1. Device layer: safe communication and decoding.
2. Semantic layer: normalization of vendor-specific values.
3. Core/analytics layer: storage as append-only JSONL records, used for evidence packaging, deterministic analysis, reporting, and AI-assisted review.

The system does not autonomously control equipment or replace professional electrical judgment.

Evidence The author's own description.

Inference This is a prototype built for personal use and later refined for a hackathon submission. It is not described as having been deployed in production or used by third parties.

The author positions HelioVerity Pilot as a solution to problems with existing monitoring platforms:

• Limited data access
• Inconsistent vendor interfaces
• Lack of early symptom detection in mixed-vendor systems

It claims to provide:

• Safe edge data capture
• Deterministic analytics
• AI-assisted triage
• Service-ready records

The project evolved from a personal side project into a judge-ready prototype during OpenAI Build Week, where Codex and GPT-5.6 were used to extend the system.

Evidence The author's own description.

Inference The positioning reflects a niche market need for better monitoring in solar installations, particularly those with mixed-vendor components. The claim evolution shows a shift from personal experimentation to a more formalized product concept.

The target customer appears to be:

• Owners of small to medium mixed-vendor solar systems
• Installers and technicians who service such systems
• DIY builders or small companies combining components from different manufacturers

The ICP is likely defined by:

• Use of multiple vendors in one system
• Need for better diagnostic information before service visits
• Desire for more detailed historical data than standard dashboards offer

Evidence The author's own description.

Inference There is no explicit customer segmentation or persona definition beyond the general use case. No evidence of actual customers, partners, or market validation exists.

No business model or pricing information is provided in the description.

Evidence Not evidenced.

Inference The project is described as a prototype and not yet commercialized. There is no indication of monetization plans, pricing models, or revenue streams.

The system uses:

• Raspberry Pi 4 hardware
• RS485 interfaces for communication
• Modbus FC04 reads (Growatt)
• Passive RX-only acquisition for JK BMS
• Python-based implementation
• JSONL storage format
• systemd for deployment
• SQLite for local data management

It includes:

• Device-specific adapters for protocols
• Append-only JSONL records with atomic latest-state and health files
• Deterministic algorithmic analysis
• AI-assisted traceable analysis
• Manifests and SHA-256 checksums for verification

Evidence The author's own description.

Inference The technical stack suggests a focus on reliability, traceability, and safety. However, no evidence of scalability or integration into larger ecosystems is provided.

There is no evidence of traction:

• No customers
• No revenue
• No deployed installations beyond the author’s own testing environment
• No third-party validation or adoption

The system is described as a prototype and not yet commercialized.

Evidence Not evidenced.

Inference The project has not reached a stage where it can be considered mature or scalable. It remains in early development phase.

No competitive landscape is described. The author does not mention existing solutions, competitors, or market positioning relative to others.

Evidence Not evidenced.

Inference Without any reference to competitors, it's unclear whether HelioVerity Pilot addresses a gap in the market or duplicates existing offerings.

Key risks and red flags include:

• Solo builder model: Only one team member (the author), which may limit scalability.
• Prototype status: Not yet commercialized or validated in real-world settings.
• Limited scope: Currently configured for specific hardware (Growatt SPF 6000 ES + JK BMS).
• No traction or monetization strategy: No evidence of customers, revenue, or business model.
• Unverified claims: All descriptions are self-reported and unverified.

Evidence The author's own description.

Inference The lack of external validation, customer data, or commercial viability raises concerns about the project’s potential for growth or impact.

1. What is your plan to validate this prototype in real-world deployments?
2. Have you identified any specific customers or use cases beyond your own testing?
3. How do you intend to scale beyond the current hardware and device support?
4. What are the key assumptions behind the AI-assisted triage functionality, and how will they be tested?
5. Are there any regulatory or safety considerations that need to be addressed for deployment in residential or commercial settings?