Business: Module Kinetic (operating brand: Module Kinetic Ltd.) Owner: Digital Currensy Inc. (all rights reserved) Document: Public portfolio showcase. Documentation only, no source code Status: Published (documentation showcase) Date: 2026-10-19

Module Kinetic

Illustration: product art, not a photo of real equipment.

Proof, not opinion, for every EV charger repair.

When a commercial EV charger faults, someone eventually writes "cleared". Module Kinetic makes that word mean something. Each fault goes through seven checks in a fixed order. If every check says yes, you get one sealed energy record that anyone with the key can verify. If any check says no, nothing is saved, and the refusal names the question that failed. There's no partial record and no "probably fine". Module Kinetic never runs the chargers. It only decides what can be trusted.

This repository describes what the products do and why. It contains no source code. The code is private and owned by Digital Currensy Inc.

Why it matters

Buyer	The problem today	What Module Kinetic gives them
Charging operator	Faults get lost in status noise, and chargers go back on before they're safe.	Every real fault becomes one repair job. A charger can't return to service until its lockout is lifted and it's inside safe limits.
Utility	Reported power doesn't match what the grid saw, and cabinet ratings are guesses.	Power is planned from measured cabinet limits, and a mismatch is refused, not reported.
Auditor	Timestamps rest on GPS alone, and records can be edited afterwards.	Every record carries a trusted time source, travelled over a checked link, and is sealed so any change shows.

The seven checks

Each check answers one question. A "yes" passes plain values to the next check. A "no" stops the chain and names the failed question.

flowchart LR
    F(["Charger fault"]) --> B
    B["1 Bayline<br/>Was this a real fault?"] --> L
    L["2 Loadclear<br/>Is this charger allowed back on?"] --> C
    C["3 Cabinetfield<br/>Was the cabinet measured?"] --> U
    U["4 Unitcommit<br/>Do the power numbers add up?"] --> P
    P["5 Phasepin<br/>Is the clock good enough?"] --> FL
    FL["6 Fiberlock<br/>Is the line clean enough?"] --> S
    S["7 Photonseal<br/>Is the record sealed?"] --> R(["One sealed energy record"])
    B -. no .-> X(["Refused, with the failed question named"])
    L -. no .-> X
    C -. no .-> X
    U -. no .-> X
    P -. no .-> X
    FL -. no .-> X
    S -. no .-> X

Loading

The products

#	Product	The question	Details
1	Bayline	Was this a real fault?	docs/bayline.md
2	Loadclear	Is this charger allowed back on?	docs/loadclear.md
3	Cabinetfield	Was the cabinet measured?	docs/cabinetfield.md
4	Unitcommit	Do the power numbers add up?	docs/unitcommit.md
5	Phasepin	Is the clock good enough?	docs/phasepin.md
6	Fiberlock	Is the line clean enough?	docs/fiberlock.md
7	Photonseal	Is the record sealed?	docs/photonseal.md

To follow one fault through all seven checks, see docs/end-to-end.md.

Illustration: product art. Step labels, the refusal and the final result: real product output.

Shared principles

• Refuse, don't guess. A failed check saves nothing and names the failed question.
• Once only. Sending the same fault or result twice never creates a second record.
• Never rewritten. Saved records are only ever added to. Nothing is edited or deleted.
• One customer per record. Every record is tied to the customer it belongs to.
• No secrets in the data. Keys and passwords are never stored with the records.
• Separate products. Each check stands on its own and can be licensed on its own.
• Tested end to end. Every product has automated tests, and one test runs a sample fault through the full chain.

Ownership and licensing

Module Kinetic, its seven products and this documentation are owned by Digital Currensy Inc. Module Kinetic Ltd. is the operating brand. This repository is documentation only and grants no licence to any code. See LICENSE.

Licensing enquiries: Digital Currensy Inc.