Kenn Mangum's QuadSovereign platform — cryptographic receipts, local-first AI, provable compliance — lands across beard.Energy's project stack in ways that are genuinely useful. This page maps the real intersections, project by project, with honest assessments of where the fit is strong and where it's not yet the right moment.
Before the project mapping, a quick grounding in what Kenn's platform delivers. Five sealed cryptographic primitives — P1 through P5 — form the spine. Every action follows one shape: sign → gate → serve → receipt → witness. The result is AI execution you can prove happened, not just assert.
The commercial product: receipted AI execution for regulated industries. Every response Schnorr-receipted and Merkle-attested. Already in production. This is the most immediately relevant QSOV product for beard.Energy projects.
Receipted provenance for ITC claims, energy provenance, domestic content, and delivered AI compute SLAs. Designed to replace spreadsheet assertions with cryptographic proof. Currently proposed — rails must run first.
Ledger entries, contracts, and approvals as signed Merkle-chained receipts. Pedersen-shielded amounts — prove a payment cleared without revealing the number. Shipped core.
A headless server — any agent platform attaches, signs actions with locally-held keys. Designed specifically for AI agent action receipting. Keys never leave the box. This is the hook for Voltaire, Sparky, and The Bid.
Tap any project to see the full integration mapping.
QuadSovereign's strongest value for beard.Energy is compliance receipting — converting what are currently assertions in documents, spreadsheets, and emails into independently verifiable cryptographic proof. That's not a small thing when you're stacking §45V, §45X, and §48E credits across six entities with IRS audit exposure.
The financing trust layer (Initiative A) is the highest-upside integration long-term — receipted ITC cost items and energy provenance could materially lower tax equity risk premia. But Kenn's own deck is honest: the rails have to run and prove out before capital claims layer on top. That sequencing is right.
SIX is ready now. The MCP signer is ready now. Those are the two integration points to move on immediately.
Forerunner Energy consortium — beard.Energy, NovaSpark, Landmark Development Services, and Terra IntelliBridge — pursuing a public-private microgrid and industrial energy resilience district in Baytown, TX. Mayor Charles Johnson is engaged and enthusiastic. The Baytown Boardwalk ($750M–$1.8B+ waterfront development, ~7 miles of shoreline) is the natural anchor customer. The critical undisclosed advantage: the IRS direct pay mechanism allows the City of Baytown, as a tax-exempt entity, to receive §48E ITC, §45V PTC, and stacking adders as direct cash payments — no tax equity broker, no intermediary.
The direct pay mechanism is powerful exactly because the municipality captures full credit value without sharing with a tax equity investor. But the IRS doesn't take anyone's word for it. §48E cost basis, domestic content percentages, and energy community qualification all have to be documented and defensible on audit.
SIX converts those documentation obligations from asserted spreadsheets into receipted, independently verifiable proof. An IRS auditor with the standalone verifier can check the claim — no access to QSOV infrastructure required. That's not a marginal improvement; it changes the audit risk profile of the entire direct pay election.
The Boardwalk development team will want ESG substantiation for the power it receives from the microgrid — provenance of clean generation hours, carbon intensity records, grid service receipts. Today those are assertions by the microgrid operator. With QSOV's energy-aware, receipted dispatch (ROE-gated, clean-hour labeled), every dispatch event is logged with a signed receipt.
For a luxury waterfront development that wants to lead on sustainability, "cryptographically verified clean power" is a marketing and financing asset, not just a compliance box.
The public-private structure involves a tax-exempt city as a direct financial participant. Signed, receipted interoperability between the consortium's records and the city's reporting obligations — without any party's books leaving their own ledger — is exactly what QSOV's ERP + ZK shielding is designed for.
| QSOV Layer | Application |
|---|---|
| SIX receipts | ITC cost item provenance for direct pay election |
| Receipted dispatch | Clean-hour ESG ledger for Boardwalk anchor customer |
| ZK shielding | City's financial participation without exposing books |
| Initiative A | Future: bankable receipted compute offtake for debt sizing |
Six-entity tax credit stack built around NovaSpark + Enapter AEM electrolyzers (exclusive US manufacturing agreement). Entity A: methane pyrolysis + §45V PTC. Entity B: solid carbon / §45Q. Entity C: fuel cells / §45Z. Entity D: solar + green hydrogen / §45Y + §45V. Entity E: hydrogen storage hub / §48E ITC. Entity F: NovaSpark AEM electrolyzer manufacturing / §45X + §48C. Active sites: Baytown TX, Houma LA, Duchesne County UT. The entire stack requires rigorous, IRS-defensible documentation across six separate entities, three credit types with stacking adders, and a BOC timing discipline that doesn't leave room for error.
Every credit claim in this stack is currently substantiated by documents, spreadsheets, and third-party attestations. The §45V production pathway requires hourly energy attribute certificates, GREET model runs, and detailed process records. §45X subcomponent credit eligibility for the AEM electrolyzer requires a PLR — and the PLR application lives or dies on the quality of the underlying documentation.
QSOV's receipt spine converts these documentation obligations from paper trails into cryptographic proofs. ITC cost items signed at origin, energy provenance receipted at hourly granularity, domestic content percentages anchored to manufacturing records. An IRS auditor can verify any claim independently — the burden of proof shifts from "trust our accountant" to "check the math."
QSOV's Initiative A was designed for this exact configuration: a financing venture whose economics rest on ITC eligibility, domestic content, energy provenance, and delivered SLAs — all currently asserted in spreadsheets. Kenn's deck describes this as the financing trust layer: receipted claims lower diligence cost and risk premia, which means cheaper tax equity and debt for the same underlying projects.
The sequencing constraint is real — Initiative A waits for the nodes to run and prove out. But beard.Energy's hydrogen stack is a multi-year build anyway. The timing works if QSOV stands up its rails in the next 12 months.
The domestic content adder requires that qualifying components meet domestic manufacturing thresholds. FEOC compliance is required before 2026 for maximum credit eligibility. Both of these require continuous, auditable records across a supply chain that spans multiple entities and potentially multiple countries. Receipted supply chains — each step signed and chained — are QSOV's native domain.
| Credit | Documentation need | QSOV layer |
|---|---|---|
| §45V PTC | Hourly EAC matching, GREET pathway | Receipted dispatch |
| §45X | Component-level manufacturing provenance | ERP + supply chain receipts |
| §48E ITC | Cost basis, domestic content % | SIX cost item receipts |
| §45Q | Carbon capture volume, sequestration records | Receipted contribution ledger |
| §48C | Facility expenditure documentation | ERP cost receipts |
| PLR support | Exhibit-quality component documentation | Receipted manufacturing spine |
beard.Energy is building a full AI-powered CRM for Corey Hancock at Hardwire Electric LLC under agreement BE-HWE-2026-001. The platform includes an eight-stage job pipeline (Lead → Intake → Proposal → Scheduled → In Progress → Complete → Invoiced → Collected) and three named AI agents: Voltaire (strict NEC code compliance), Sparky (owner-operator assistant tailored to Corey's personality), and The Bid (conversational estimating agent). Call recording flows to Groq transcription, Claude parsing, CRM record creation, and automatic OpenSign agreement generation. The IP is protected — non-exclusive deployment license only, beard.Energy retaining full rights to redeploy the platform.
QSOV's sovereign MCP signer is a headless server that exposes keygen / sign / verify / attest as standard tools — any agent platform attaches, keys stay local. This is the native integration point for Voltaire, Sparky, and The Bid.
Right now, every agent decision is a black box. Corey has no cryptographic record of what Voltaire recommended on a given NEC compliance question, what Sparky decided about scheduling, or what line items The Bid generated for a specific job. In a contract dispute — and electrical contractors get into contract disputes — that matters.
Voltaire's NEC compliance outputs carry professional weight — they're being used to make real decisions on permitted work. A receipted Voltaire output isn't just a chat log; it's a signed artifact proving the AI was given specific inputs and produced specific guidance. That's a defensible record for an inspector conversation, a permit submission, or an insurance claim.
This is exactly what QSOV's deck describes as the category difference between SIX and standard AI providers: "Every major AI provider asks regulated customers to trust their logs. SIX gives them mathematical proof."
Because the agreement protects beard.Energy's full rights to redeploy the Hardwire platform, the receipting infrastructure built for Corey becomes a deployable feature for every future electrical contractor client. "Receipted AI agents for licensed electrical contractors" is a differentiator that compounds across the platform's client base.
The QSOV integration follows the ②B posture — sign locally, hand off an already-provable artifact. Hardwire's system handles the receipt; the key never leaves beard.Energy's infrastructure.
| Agent | What gets receipted |
|---|---|
| Voltaire | NEC citation + compliance recommendation, signed at inference |
| Sparky | Scheduling decisions, customer interactions, follow-up actions |
| The Bid | Estimate line items bound to transcript hash — input/output provable |
| OpenSign flow | Agreement generation event tied to intake receipt chain |
Two connected applications under the SolarSlate brand. App 1 (Roof Scan Pro): roof tracing and topology engine with WGS84 coordinate locking, edge labeling, pitch calculation, 3D geometry, and GLB export — stabilized on GitHub with PR #85. App 2 (SolarSlate Assembly Studio): a separate React + Three.js app consuming App 1's exports to simulate the layered BIPV installation sequence (OSB, Dens Deck, high-temp membrane, ventilation battens, mounting profiles, dummy panels, active panels, trim). The Solarislate integrated assembly system is being modeled for §45X credit eligibility using UL 7103 certification as the anchor argument — approximately $4,252 in §45X credits per roof, transferable at ~$0.95/dollar.
The Private Letter Ruling for the full Solarislate integrated assembly depends on convincing the IRS that every layer — from OSB to active panel — functions as a single eligible §45X component. That argument is stronger with exhibit-quality documentation of exactly what the assembly is and how it's installed.
App 2's layer simulation, exported from App 1's topology engine, is already generating that documentation. If those exports are receipted — each layer signed, the assembly sequence chained — the PLR application has a verifiable audit trail that's more than diagrams and affidavits.
At $4,252 per roof transferable at $0.95/dollar, the §45X credit value scales directly with the number of documented installations. QSOV's receipted contribution ledger — each installation a signed, chained event — provides the continuous provenance record that makes bulk credit transfer clean. No single point of failure in the documentation chain.
App 1 and App 2 are in active development. The QSOV integration is a second-phase add-on, not a blocker for the core build. The right moment to wire in receipt generation is when App 2's export pipeline is stable — so the receipts reflect a production-ready assembly record, not a moving target.
50 MW ground-mount solar through a Nevada accelerator, with material committed, crews in place, $40M bonding minimum, NABS/prevailing wage requirements, certified payroll, and a December 31, 2026 target in-service date. Active blockers: Nevada contractor licensing constraints and a panel compatibility issue with approximately 5 MW of Warrior/Wari panels. This is a large execution project with significant compliance overhead — prevailing wage documentation, apprenticeship ratios, domestic content tracking, and a hard IRS begin-of-construction deadline.
The prevailing wage and apprenticeship ratio requirements for IRA adder eligibility require continuous, auditable crew records. Certified payroll is already a requirement — QSOV's receipted contribution ledger could layer on top of that existing obligation, turning compliance documentation from a periodic reporting exercise into a continuous receipted record.
For a $40M+ bonded project with a hard year-end deadline, the risk of losing domestic content adder eligibility on audit is real. Receipted provenance on panel origin, racking materials, and inverter sourcing — chained to the purchase orders and installation records — is a defensible audit position.
The ~5 MW panel compatibility issue creates a documentation risk: if those panels are ultimately excluded from the system or replaced, the cost basis and domestic content calculations need to reflect that clearly. Receipted installation records with panel-level granularity would make that adjustment clean and auditable rather than a retroactive spreadsheet revision.
The project's December 31, 2026 target in-service date is aggressive. Adding a new receipting infrastructure layer to an active construction project with licensing and compatibility blockers is not the right sequencing. The QSOV integration is a post-commissioning and future-project improvement, not a current-build priority.
985 kW ground-mount solar in Duchesne County, Utah using PowerField bucket-ballasted racking and SolarEdge 125 kW inverters. Active design work includes frost line depth (36"), above-ground DC wiring clearance under NEC 690.31, messenger wire homerun architecture, and a minimum-trench approach reducing to two or three short trench stubs plus directional bores at road crossings. This project is in construction design/engineering mode, with a future electrolysis add-on planned as part of the broader hydrogen stack.
Duchesne is in construction execution mode — the immediate value is getting the racking, wiring, and inverters right. QSOV's receipt infrastructure doesn't accelerate panel installation or resolve NEC 690.31 clearance questions. The integration value arrives at two later stages.
Duchesne County was actively being analyzed under IRS Notice 2026-39 for energy community adder eligibility. EC status locks at beginning of construction, so the documentation of the BOC event is already critical. A receipted BOC record — signed at the date of construction commencement with project documentation hash — is a simple, low-friction QSOV application that's worth doing now rather than reconstructing retroactively.
NovaSpark Energy Corporation — Rick Harlow's operation — holds a Louisiana Economic Development LOI (March 9, 2026) covering dual-site operations: Houma (Terrebonne Parish) and West Monroe (Ouachita Parish). Commitments include $30M capital investment in Houma by January 2028, 240 jobs and $22.2M in annual payroll by 2035. State incentives package: High Impact Jobs ($8.2M Houma / $2.5M West Monroe), LED FastStart ($5M / $3M), ITEP (10-year 80% ad valorem exemption). The HTAC airport microgrid opportunity in Houma-Terrebonne is a parallel thread — the utility standoff (TPCG and Entergy both refusing to invest without commitment letters) is the opening for an independent microgrid solution involving beard.Energy, NovaSpark, Rick Harlow, and JPM/Origin financial partners.
Project Aether sits at the intersection of two compliance obligations: Louisiana's LED incentive reporting (job creation, payroll benchmarks, capital deployment through 2035) and federal §45X / §48E credit documentation for the electrolyzer manufacturing operation. These are currently separate reporting tracks going to separate counterparties with separate documentation standards.
QSOV's receipt spine can serve both. Manufacturing provenance receipts for §45X subcomponent credits are the same underlying records that substantiate the capital deployment for LED's ITEP exemption. One chain of receipts, two compliance consumers — and neither requires access to the other's books.
The HTAC opportunity is uniquely positioned for SIX. Airport operations are regulated environments — FAA oversight, emergency power requirements, procurement documentation standards. An independent microgrid serving an airport needs defensible records across its entire operational life. SIX's compliance-as-byproduct model is a direct fit: every dispatch decision, every generation event, and every power quality record becomes a FOIA-defensible receipted artifact.
The QSOV deck specifically calls out government as a target vertical: "FOIA-defensible AI — release execution proofs without exposing system internals." An airport authority is exactly that customer.
The LED LOI carries a live confidentiality clause — disclosure before mutual announcement can trigger withdrawal. Any QSOV integration discussion involving the Project Aether details needs to stay within the existing NDA framework until LED and NovaSpark have made mutual announcement. QSOV's own integration posture (②B — sign locally, hand off provable artifacts) is naturally compatible with confidentiality obligations since keys and data never leave the node.