Two models enter the control cycle. One clean. One needs action.
This synthetic demonstration shows the exact evidence boundary and exception behavior of Energy Market Access Control without using customer or regulator-account data.
Three evidence layers are enough to show the control
Approved model catalog
Three active Northstar commercial SKUs map to two customer-approved regulatory basic models and carry exact brand/manufacturer, technical revision, customer-confirmed jurisdiction scope and portfolio exposure fields.
Official-system evidence
DOE CCMS submission confirmations, California MAEDbS status rows and exact current NRCan compliant-list or CREED/report evidence represent jurisdiction-specific proof. DOE public listing remains corroborative; an exact NRCan compliant-list match can control the Canadian reporting/listing predicate under current NRCan guidance.
Controlled operating policy
Assured regulatory-node matching, customer-approved basic-model mapping, regulatory-material fingerprints, DOE authority-derived annual deadlines, importer/certifier authority controls and forward launch projection are enabled.
Controls exercised
- Customer-confirmed jurisdiction scope is required before any model can be controlled.
- Decisive regulator evidence binds only through a unique assured regulatory node: responsible party + product/equipment class + customer-approved basic model; commercial brand/model keys are candidate-discovery aids only.
- DOE CCMS submission evidence is distinguished from corroborative public database presence.
- California Approved status is decisive; Archived fails closed to a product-specific review state rather than being treated as an automatic no-sale conclusion.
- NRCan exact current compliant-list evidence can control the reporting/listing predicate for the assured regulatory node; absent/unmatched models require report/CREED proof and verification-mark evidence remains separate.
- Commercial SKUs can inherit one regulatory basic model without creating a false new filing, while technical/material changes fail to review instead of silently carrying over.
- DOE importer/certifier/third-party authority is checked when importer control is configured.
- The Launch Gate projects known deterministic obligations through the planned launch date.
- Clean cycles can straight-through close only after shadow-cycle autonomy approval.
Synthetic findings
- FR100 is controlled across all three customer-required markets with exact evidence bound to each jurisdiction.
- DH220 is archived in the synthetic California evidence, so the portfolio cannot be marked controlled until a product-specific California sell-through/grandfathering basis or current Approved record is bound; DOE and Canada remain positive.
- DH220 has a known DOE annual obligation before its planned launch date, so the forward Launch Gate returns “Action required before launch” rather than projecting today's RELEASE indefinitely into the future.
- A correlated synthetic CCMS confirmation can be normalized into evidence, bound to its receipt reference, and trigger an immediate evidence-cycle rerun when the source binding and schedule are approved.
What this demonstration proves
The engine can deterministically separate commercial SKUs from regulatory basic models, detect material changes, bind filing proof and importer/certifier authority, project known launch-date obligations, normalize correlated provider receipts, distinguish controlled/blocked/unresolved states and retain a repeatable proof chain.
What it does not prove
This synthetic run does not prove authorized live customer-source connectivity, a regulator’s legal conclusion, current external/provider acceptance, or paid-customer outcomes. It also does not determine whether a model is legally in scope.
See it against your catalog shape
Start with a redacted sample of your current model export and the evidence sources you already receive.