Engineering
FAQ
· Mechanism (“how is energy transferred?”) — closed by the charge model together with classical electrodynamics.
· Accounting (“does energy balance close?”) — closed by the Frame 0 identity and by measurements only.
· Attribution (“what is the source?”) — closed only after a closed balance together with a boundary inventory.
An answer to the first question is never presented as an answer to the third.
· System level — multi-level resonant power architecture; this is the description that leads on every page.
· Block 5 excitation-stage attribution — the block 5 excitation stage belongs to the Armstrong-type discharge-resonant oscillator class (a class known since 1912), within classical Maxwell–Lorentz electrodynamics. The class is over a century old; the novelty is not in the class but in the regime-level implementation.
· Validation stage — TRL 5–6. Independent boundary metrology is a TRL 6 milestone; controlled disclosure of the implementation belongs to the TRL 8 track.
· Patent family — six jurisdictions: ES2950176B2 granted (OEPM Spain) · WO2024209235A1 (PCT anchor) · EP4693872A1 regional phase (37 EPC states) · US20260088633A1 national phase · CN119096463A national phase · IN 202547010911 national phase · EUIPO trademark 019220462.
· Illustrative prototype boundary values, subject to validation. The ~24 V / ~24 A input boundary of block 5.
· Representative prototype regime parameters, metrology-dependent. The ~2.45 MHz coupled HF regime frequency and the internal amplitudes inside block 5.
· Approximate startup/regime-supply boundary value, subject to startup validation. The ~9 V startup source and the internal 9 V regime-supply line.
· Target configuration and interface values. The 48 V / 25 A base telecom rating per ETSI EN 300 132-2 and the ~220 V / ~16 A / 50 Hz AC interface.
Investigations of the full energetic balance at all boundaries of the device are not complete. The series is published for understanding the mechanism and the organisation of charge motion; it is not a power specification and does not replace independent boundary metrology. Products of separately measured quantities are not published and are not treated as active power. Values at different boundaries are not compared directly; their ratio is not the device efficiency.
Architecture — functional levels 0–5 with the patent numbering.
· Level 0 — external startup: startup source ~9 V. Startup is characterised in charge terms by Qstartup = ∫ istart dt (coulombs) at a per-coulomb cost of ~9 J/C; numerical values are the subject of validation. After the regime is established the startup accumulator is physically disconnected; its role as a boundary condition at the same schematic point is then taken over by the internal 9 V line.
· Level 1 — block 3 (aggregate). Block 3 contains the electrical conversion and switching functions disclosed at patent level and establishes the ~24 V / ~24 A input boundary of block 5. These are illustrative prototype boundary values, subject to validation; they describe a local internal port and do not by themselves establish whole-device input, output, efficiency or source attribution. The converter topology, component values, switching sequence and control implementation remain confidential.
· Level 2 — block 5. Excitation and holding of the coupled HF resonant regime at ~2.45 MHz. Block 5 is a controlled system of coupled electromagnetic resonators — not a single ideal transformer — with three coil structures inside its functional boundary: the Tesla coil for excitation, the resonator for holding the regime, and the secondary winding 10 that feeds the secondary extraction node 10–11.
· Level 3 — secondary extraction node 10–11. Secondary winding 10 together with capacitor 11: the output electrical boundary of block 5. This is the extraction node; there is no parallel branch. Capacitor 11 is not merely a filter — depending on topology it participates in resonant tuning, reactive compensation, charge accumulation, impedance matching, signal formation and preparation for rectification. The extraction coupling is bidirectional: by Lenz's rule the load pushes back on the primary circulation, which is why internal amplitudes are dynamic and require BBMS supervision.
· Level 4 — bridge 12. The single canonical diode bridge in the system (ACHF → DC), located at the boundary of block 5. It is the first element beyond block 5. The internal rectification inside the block 13 output stage is a module internal and does not constitute a second architectural rectifier.
· Level 5 — block 13 (aggregate). DC bus; the 9 V regime-supply line and the 5 V control line; BBMS; the tertiary power transformer (buffers load influence and provides the galvanic safety boundary of the output stage); own switching; internal rectification of the output module; the customer output; the DC/AC fork. The term “tertiary” is reserved exclusively for the block 13 power transformer; it is not applied to winding 10 or to any other extraction element.
Steady-state ring architecture. In the steady state the topology closes into a functional ring: DC bus (block 13) → 9 V regime-supply line → startup entry point → block 3 conversion aggregate → block 5 input boundary (~24 V / ~24 A) → node 10–11 → bridge 12 → DC bus. The 9 V line connects at the same schematic point where the external startup accumulator was connected during initiation. The 24 V bus is formed by the block 3 conversion aggregate — not directly from the 9 V line. The 9 V regime-supply line and the ~24 V / ~24 A block 5 input boundary are distinct internal ports; their values do not form an input–output pair for computing an efficiency and are not compared directly. The 9 V line, the regime supply and the excitation bus are internal flows relative to the complete device boundary; they do not enter Pin,boundary. The ring is public as an architectural principle; ratings and physical implementation of intermediate stages are closed engineering documentation. The ring does not mean “infinite reuse of the same energy”.
BBMS — supervisory layer. BBMS is a distributed supervisory system of energy state and dynamic regime stability. The historical expansion “Battery Boundary Management System” is retained for continuity; it does not mean the battery is the source, and BBMS is not a classical Battery Management System. BBMS holds the regime inside its operating window, prevents amplitude runaway and decay, coordinates the distribution of power between the regime supply, control and the customer output, and executes startup and shutdown sequences. Its main control question is not “how much power is available at the output?” but “how much power can be permitted at the output right now without destroying the internal regime?” BBMS steers the regime behind the load; its algorithmic target is Rcontrol(t) → 0. BBMS is not an energy source; the reading “BBMS replaces an energy source” is an interpretation the canon forbids.
Product fork. After the block 13 output stage there is a controlled DC flow with a defined energetic cost per coulomb. At this point the physical core of VENDOR has completed its work; what follows is the user interface. Base configuration is DC (target window 48–75 V DC; base telecom rating 48 V / 25 A per ETSI EN 300 132-2); the AC configuration adds a DC-link and an inverter for a ~220 V / ~16 A / 50 Hz output. The inverter is not part of the physical core and is interchangeable as an output module. Product line: 48V DC First. 220V AC Later.
Engineer-facing answers covering the functional levels 0–5, the ring architecture of the steady state, the Frame 0 accounting identity, the seven high-level causes of imbalance, the outcome classes A–E of independent metrology, the charge-model reading of the ring, BBMS supervision, and the boundary-relative attribution of the “where does the energy come from?” question. Q 00 is expanded by default; it fixes the vocabulary of the complete device boundary and the accounting identity required for a correct reading of every subsequent answer.
This page is the canonical engineering evaluation surface.
Interpretation framework, not a metrology proof.
All statements reflect TRL 5–6 validation stage.
Legal entity: MICRO DIGITAL ELECTRONICS CORP S.R.L. · Romania, European Union · CUI 50047468 · EUIPO trademark 019220462 (VENDOR mark, registered) · Six-jurisdiction patent family with common priority date 2023-04-05.
Functional levels 0–5,
Frame 0 accounting identity
The most common analytical error is to read a multi-level resonant architecture as a single converter and to divide a customer output by a superficial boundary term. The canonical whole-device framework is different. Read this block first.
VENDOR is evaluated through functional levels 0–5 in the patent numbering, together with a steady-state ring that closes the topology, and through the accounting identity of the complete device boundary (Frame 0). The levels are functional accounting boundaries, not a mechanical decomposition of the enclosure. Mixing levels produces boundary-definition errors, not physical conclusions.
The six functional levels
· Level 0 — external startup. Startup source ~9 V. Charge characterisation of startup: Qstartup = ∫ istart dt (coulombs) at a per-coulomb cost of ~9 J/C; numerical values are the subject of validation. After the regime is established the startup accumulator is physically disconnected; its role as a boundary condition at the same schematic point is taken over by the internal 9 V line.
· Level 1 — block 3 (aggregate). Block 3 contains the electrical conversion and switching functions disclosed at patent level and establishes the ~24 V / ~24 A input boundary of block 5. These are illustrative prototype boundary values, subject to validation; the converter topology, component values, switching sequence and control implementation remain confidential. The switching node of block 3 is a discharger; the term “discharger” is always used with an explicit attachment (block 3 switching node or block 5 internal switching).
· Level 2 — block 5. Excitation and holding of the coupled HF resonant regime at ~2.45 MHz. Block 5 is a controlled system of coupled electromagnetic resonators, with three coil structures inside its functional boundary: the Tesla coil for excitation, the resonator for holding the regime, and secondary winding 10 that feeds the secondary extraction node 10–11.
· Level 3 — secondary extraction node 10–11. Secondary winding 10 together with capacitor 11: the output electrical boundary of block 5. This is the extraction node; there is no parallel branch. Capacitor 11 is not merely a filter — depending on topology it participates in resonant tuning, reactive compensation, charge accumulation, impedance matching, signal formation and preparation for rectification. The extraction coupling is bidirectional: by Lenz's rule the load pushes back on the primary circulation, which is why internal amplitudes are dynamic and require BBMS supervision.
· Level 4 — bridge 12. The single canonical diode bridge in the system (ACHF → DC), located at the boundary of block 5. It is the first element beyond block 5. The internal rectification of the block 13 output stage is a module internal and is not counted as a second architectural rectifier.
· Level 5 — block 13 (aggregate). DC bus; the 9 V regime-supply line and the 5 V control line; BBMS; the tertiary power transformer (buffers load influence and provides the galvanic safety boundary of the output stage); own switching; internal rectification of the output module; the customer output; the DC/AC fork. The term “tertiary” is reserved exclusively for the block 13 power transformer; it does not apply to winding 10 or to any other extraction element.
In the steady state the topology closes into a functional ring:
The 9 V line connects at the same schematic point where the external startup accumulator was connected during initiation. The 24 V bus is formed by the block 3 conversion aggregate — not directly from the 9 V line. The 9 V regime-supply line and the ~24 V / ~24 A block 5 input boundary are distinct internal ports; their values do not form an input–output pair for computing an efficiency and are not compared directly. The 9 V line, the regime supply and the excitation bus are internal flows relative to the complete device boundary; they do not enter Pin,boundary. The ring is public as an architectural principle; ratings and physical implementation of intermediate stages are closed engineering documentation. The ring does not mean “infinite reuse of the same energy”.
A charge-model reading of the ring makes the point sharper. For charge, the ring is trivial — the local law of charge conservation is closed at every node by Kirchhoff's balances without any flow crossing the device boundary. For energy, the ring resolves nothing on its own — in the steady state energy moves through the ring; the question of its origin is adjudicated only at Frame 0.
Frame 0 — the complete device boundaryFrame 0 is the outer energetic boundary of the entire installation — the only boundary at which the question of the source can be answered. At Frame 0 the canonical accounting identity is:
Signs are defined relative to Frame 0: incoming flows are positive inward; the customer output and losses are positive outward; dEstored/dt > 0 means the internal store is growing. Internal feedback does not cross Frame 0 and is not counted as external input.
The identity is an accounting identity: it is bound to hold at all times; it checks the completeness of the accounting (“is everything counted?”) and does not name the source (“from where?”). The canon deliberately makes no claim about the numerical value of Pin,boundary in the steady state; conclusions about its magnitude, origin or absence are premature in either direction until independent metrology completes.
Strict order: route → balance → attributionInterpretation follows a strict order: charge route → energy balance → source attribution. Attribution establishes the physical composition and the quantitative contributions of the incoming flows and/or the decreasing internal stores that numerically cover Pcustomer + Ploss,total and the change in the remaining stores under the closed balance. The result may be a set of contributions rather than a single source. The word “source” applied to internal flows is forbidden: all local “sources” inside the boundary are links in one chain of transfer, conversion, storage and distribution; they are not independent external sources of Frame 0. An answer about the source is always relative to the chosen boundary; in the VENDOR canon that question is addressed to Frame 0.
Why cross-boundary η ratios are not the whole-device metricThe error is not to compute an efficiency at the complete device boundary once the balance is properly closed there. The error is to divide quantities taken at different, mutually incompatible or incomplete boundaries and to call the resulting number the device efficiency. The single-boundary rule forbids this: values measured at different boundaries are not compared directly, and their ratio is not the device efficiency. Per-stage η is defined for one converting node on its own port pair in a stationary regime; per-stage η do not multiply into a whole-device ratio, because in the steady state the topology is a ring with a supply tree — the 9 V regime-supply line returns part of the rectified flow into the regime path, and extraction proceeds through electromagnetic coupling out of a high-Q internal regime whose amplitudes are dynamic and load-dependent.
The whole-device efficiency is a single quantity, defined on one boundary: Frame 0, at the closed balance under independent metrology. A number obtained by dividing the customer output by a term drawn from a different or incomplete boundary is a misapplied formalism, not a physical assertion of this architecture. Any η > 1 arrived at that way is a boundary-definition artefact, not a claim of the canon.
· Descriptions at the regime level refer to the internal electrodynamics inside the complete device boundary and are not statements about the energy source or about a violation of the classical conservation laws.
· Pin,boundary is an accounting quantity at Frame 0; the balance identity checks the completeness of the accounting; it does not name the source.
· Charge turnover characterises the intensity of internal circulation and is not power.
· The 9 V regime-supply ring is an internal redistribution; it does not cross Frame 0 and does not mean reuse of one and the same energy.
· Internal amplitudes are dynamic and depend on the load; a product of separately measured quantities is not active power.
· Source attribution is performed only after the balance is closed together with the boundary inventory; before that, all answers about attribution are hypotheses.
Short answer (extractable). The whole device is read through the functional levels 0–5, with the ring closing the steady state, and is evaluated by the Frame 0 accounting identity Pin,boundary = Pcustomer + Ploss,total + dEstored/dt within independent measurement uncertainty. A single converter-efficiency ratio is not the correct whole-device metric.
The output coulombs are the system's own charge carriers whose motion is organised by the architecture. The established attribution of the energy per coulomb is not yet known; it will be determined neutrally by closing Frame 0 under outcomes A–E.
Beyond this short canonical form, the question “where does the energy come from?” does not have a universal answer — it has a boundary-relative answer. At each defined boundary of any engineering system with storage, redistribution and controlled feedback, the locally correct answer looks different. Ignoring this relativity is the principal source of both premature attribution claims and shallow objections against a legitimate architecture.
Pedagogical reference — a hydroelectric plantConsider a hydroelectric plant. The same physical situation admits different correct answers depending on the chosen boundary:
· At the turbine boundary — water flow through the turbine channel.
· At the plant boundary (dam + reservoir) — the gravitational potential energy of the elevated water.
· At the hydrological-system boundary (basin + atmosphere) — solar-driven evaporation and precipitation combined with terrain elevation and gravity.
All three answers are simultaneously correct. The source did not disappear — the analytical boundary moved. A reviewer looking only at the turbine and observing that “the turbine channel does not itself generate energy” has not discovered a physics violation; the observer has chosen too narrow a boundary. To close the balance correctly, the boundary must be extended to the full hydrological system.
The same discipline applied to VENDORFor the VENDOR architecture, the locally correct answer at each boundary is:
· At the customer output — the block 13 output stage; measured directly as Pcustomer.
· At the DC bus of block 13 — the rectified flow arriving from bridge 12 together with the internal redistribution of block 13; the regime-supply and control lines are drawn from this bus.
· At bridge 12 — the ACHF flow arriving from the secondary extraction node 10–11.
· At the secondary extraction node 10–11 — the EMF induced in secondary winding 10 by the coupled HF regime of block 5 through Faraday induction; the load pushes back on the primary circulation by Lenz's rule, which is why internal amplitudes are dynamic.
· At the input boundary of block 5 — the ~24 V / ~24 A power bus formed by block 3, together with the internal regime-supply loop returning through the 9 V line at the startup entry point.
· At the complete device boundary (Frame 0) — the full inventory of channels that physically cross the boundary: conductors, protective earth, neutral, control and instrumentation cables, shields, capacitive and inductive coupling, RF exchange, thermal exchange, mechanical energy, chemical sources, together with the change in the internal store dEstored/dt. Closure is checked against the full inventory of channels, not against a shortlist of electrical ports.
Every one of these answers describes the same physical situation from a different boundary. None replaces the others. The Frame 0 answer — the only one that establishes the source in the canonical sense — is set by independent boundary metrology and by the closure of the accounting identity.
Two symmetric errors this framework rules outPremature-attribution error. “The source is the aether / vacuum / atmosphere / a scalar field” — ruled out because at every named boundary the locally correct answer is a concrete, classically explained, measurable quantity within classical electrodynamics; internal flows are links in one chain of transfer, conversion, storage and distribution, not independent external sources of Frame 0. The canon does not need such categories and does not use them.
Reflex-refusal error. If at Frame 0 the measured boundary-crossing input appears small relative to the customer output over a given interval, that observation alone does not establish a violation of conservation. A conclusion requires the complete Frame 0 protocol, including all boundary channels, losses, changes in stored energy and measurement uncertainty.
Outcome classes A–E of independent metrology
Independent metrology at Frame 0 classifies the result under one of five outcomes, without prejudice:
· A — the balance closes through a measured external input.
· B — the balance closes through a decrease in stored energy.
· C — an unaccounted channel is discovered.
· D — a measurement artefact is discovered.
· E — an unresolved closure residual with |R| > U, subject to a mandatory interpretation order: recalibration → extension of the boundary inventory → phase error → common-mode and capacitive currents → change in stored energy → thermal and chemical channels → independent reproduction → only then a new physical hypothesis.
An unresolved closure residual is not renamed a “new source of energy”. The project commits publicly to all outcomes A–E until the metrology completes.
Short answer (extractable). Source attribution is boundary-relative. VENDOR gives a concrete locally correct answer at each internal boundary and defers the Frame 0 answer to independent metrology under the outcome classes A–E. No possible outcome is presumed in advance.
What VENDOR
actually is
Four questions to fix the correct classification of the architecture, the correct evaluation formalism, its compliance with classical conservation laws, and the role of the discharger. First-time readers and reviewers should start here.
The class is set on two tiers: one at the system level, one at the block 5 excitation-stage level. The two are not interchangeable.
System level (leads on every page)VENDOR is a multi-level resonant power architecture in which the regime is formed and held inside block 5, useful power is drawn through the secondary extraction node 10–11 and rectified at bridge 12 into block 13, and the steady-state regime supply is returned through the 9 V ring — all supervised by BBMS as a dynamic-stabilization system, with a base DC output and interchangeable user interfaces. Every level uses documented classical electromagnetic and power-electronic principles within classical Maxwell–Lorentz electrodynamics. The novelty is not in the physics of any one stage — it is in how known processes are integrated into a single controllable architecture that forms, holds and uses an electromagnetic regime while useful power is drawn from it.
Block 5 excitation-stage attributionThe block 5 excitation stage belongs to the Armstrong-type discharge-resonant oscillator class (a class known since 1912), within classical Maxwell–Lorentz electrodynamics. The class is over a century old; the novelty is not in the class but in the regime-level implementation. This attribution applies to block 5 excitation only — it is not the description of the whole system.
Physical core (functional levels 0–5, patent numbering)
· Level 0 — external startup source ~9 V; startup characterised in charge terms as Qstartup = ∫ istart dt at ~9 J/C; physically disconnected after regime establishment.
· Level 1 — block 3 (aggregate): electrical conversion and switching functions establishing the ~24 V / ~24 A input boundary of block 5 (illustrative prototype boundary values, subject to validation).
· Level 2 — block 5: a controlled system of coupled electromagnetic resonators holding an HF resonant regime at ~2.45 MHz.
· Level 3 — secondary extraction node 10–11: secondary winding 10 with capacitor 11 as the output electrical boundary of block 5.
· Level 4 — bridge 12: the single canonical diode bridge in the system.
· Level 5 — block 13 (aggregate): DC bus, 9 V regime-supply line, 5 V control line, BBMS, tertiary power transformer (buffers load influence; galvanic safety boundary), output stage, DC/AC fork.
In the steady state the topology closes into a functional ring: DC bus → 9 V regime-supply line → startup entry point → block 3 conversion aggregate → block 5 input boundary (~24 V / ~24 A) → node 10–11 → bridge 12 → DC bus.
Classes VENDOR is notNot a chemical energy source, not a battery-based system, not a fuel-consuming machine, not a closed-form linear input–output converter, not a stand-alone energy source. The historical expansion of BBMS is “Battery Boundary Management System”; it is retained for continuity and does not mean the battery is the source, and BBMS is not a classical Battery Management System.
The error is not to compute an efficiency at the complete device boundary once the balance is properly closed there. The error is to divide quantities taken at different, mutually incompatible or incomplete boundaries and to call the resulting number the device efficiency. The single-boundary rule forbids this: values measured at different boundaries are not compared directly; their ratio is not an efficiency.
Per-stage η values apply only to specific converter nodes on their own boundaries and are defined only in periodic steady state on electrical ports. They do not combine into an end-to-end ratio, because the steady-state architecture is a ring with a distribution tree, not a serial chain: the 9 V regime-supply line returns part of the rectified flow into the regime path, and extraction proceeds through electromagnetic coupling out of a high-Q internal regime whose amplitudes are dynamic and load-dependent.
The whole-device efficiency is a single quantity, defined on one boundary: Frame 0, at the closed balance under independent metrology. Any η > 1 obtained by dividing the customer output by a term drawn from a different or incomplete boundary is a boundary-definition artefact, not a physical assertion of this architecture.
Correct evaluation stack — the five boundary questionsBefore applying any ratio, ask five questions in order: (1) where is the boundary drawn physically; (2) which conductors, fields and couplings cross it; (3) where is voltage measured; (4) where is current measured; (5) do the two belong to the same energy flow. Taking a current at one level, a voltage at another, and calling the product a power at a third level is forbidden.
Other systems in the same evaluation classSystems with internal stored electromagnetic state, controlled feedback and coupled resonators are evaluated the same way — not by a single device ratio, but by boundary-specific figures. RF cavities and particle accelerators (Q-factor, shunt impedance), magnetrons and klystrons (per-stage efficiency, operating-mode and load-matching characterisation), regenerative-class oscillators (loop gain, stability margin), plasma-confinement systems (confinement time, stability parameter). This is standard engineering language for systems with internal storage, controlled feedback and coupled resonator dynamics — not new physics.
No. The project makes no claim of violating any conservation law, and does not use categories of that kind anywhere in its own materials. The architecture is defined within classical Maxwell–Lorentz electrodynamics. At the complete device boundary (Frame 0) the canonical accounting identity applies at all operating states:
The identity is an accounting identity: it must hold at all times; it checks the completeness of the accounting (“is everything counted?”) and does not name the source (“from where?”). The identity applies in every operating state — startup, transient, steady state, shutdown — and it holds by construction; the empirical work is to close the accounting completely.
The neutrality doctrine (locked)The canon deliberately makes no claim about the numerical value of Pin,boundary in the steady state. Until independent boundary metrology completes, conclusions about the magnitude, origin, or absence of an incoming flux are premature in either direction. No possible outcome is presumed in advance — neither the presence of an additional input, nor a closed balance without one, is granted a priori. The open engineering question is exclusively the quantitative completeness of the Frame 0 accounting — a question to be answered by measurement, in both directions, under the outcome classes A–E (see Q 12).
“Discharger” is a term of the charge model of the architecture. The word names two different physical elements, and the canon requires that the attachment be stated on every use: the high-voltage switching node of block 3, and the internal switching inside block 5. Mixing the two into one concept is not permitted.
Two publicly acknowledged discharger typesTwo discharger types are publicly acknowledged in this architecture: open (gas) and vacuum. The charge logic is identical. The types differ in operational characteristics and durability; the difference does not change the end result of the architecture. Which type is used in which unit — a matter of engineering documentation, not a public claim.
What a discharger does — and does notA discharger forms a local pulse discharge channel under a voltage boundary condition: it opens a controlled path for charge redistribution between adjacent local reservoirs when the local field on its plates reaches its breakdown boundary. Charge conservation on each plate closes trivially at every discharge event; energy conservation is not local to the gap — it is a Frame 0 accounting question. The discharger is not declared to be an energy source, a fuel or a consumable resource; those are not roles the canon attributes to it. The medium sets the boundary condition for the gap; whether any medium-related channel constitutes a net boundary input at Frame 0 is inventoried and settled by measurement under the outcome classes A–E (see Q 12) — no medium mechanism is named as a source, and none is asserted absent. The public architectural principle is parallel discharge channels — parallel local reservoirs released in coordinated timing; the microscopic implementation is not published.
Townsend framework — patent-level attributionWhere the Townsend pre-breakdown framework is invoked in the patent documentation, it is a patent-level analytical framework, not a statement about the measured mechanism of the current implementation. Carrier multiplication in the pre-breakdown window is a conductivity effect, not energy multiplication: it characterises the conductivity transition in the gap; it does not multiply the charge of the system and it does not multiply energy. Any invocation of the Townsend framework in VENDOR materials carries this attribution explicitly.
Can the device exchange energy with its surroundings through channels other than the electrical ports?Yes, in principle any real power system exchanges with its surroundings — which is why the Frame 0 inventory includes all boundary-crossing channels: conductors, protective earth, neutral, control and instrumentation cables, shields, capacitive and inductive coupling, RF exchange, thermal exchange, mechanical energy, chemical sources, and the change in the internal store dEstored/dt. Closure is checked against the full inventory of channels, not against a shortlist of electrical ports. Whether any medium-related channel is a net boundary input is an empirical question, formally routed to outcome classes A and C (see Q 12), and answered by measurement under a medium-sensitivity protocol. No specific medium mechanism is named or implied as a source; nothing on this page pre-empts the metrology answer in either direction.
How the architecture
actually operates
Five questions on the ring architecture that closes the steady state, the three coil structures of block 5, the 9 V regime-supply line, the difference between charge turnover and delivered power, and the distinction between reactive circulation and net active power. All within classical Maxwell–Lorentz electrodynamics.
After startup, the topology closes into a steady-state ring. The ring is public as an architectural principle; ratings and physical implementation of intermediate stages are closed engineering documentation.
The 9 V line connects at the same schematic point where the external startup accumulator was connected during initiation. The 24 V bus is formed by the block 3 conversion aggregate — not directly from the 9 V line. The 9 V regime-supply line and the ~24 V / ~24 A block 5 input boundary are distinct internal ports; their values do not form an input–output pair for computing an efficiency and are not compared directly. The 9 V line, the regime supply and the excitation bus are internal flows relative to the complete device boundary; they do not enter Pin,boundary of the Frame 0 accounting identity.
What the ring means — and what it does notFor charge, the ring is trivial: the local law of charge conservation is closed at every node by Kirchhoff's balances, without any flow crossing the device boundary. For energy, the ring resolves nothing on its own — in the steady state energy moves through the ring, and the question of its origin is adjudicated only at Frame 0. The ring is not a direct serial throughput to the load: it sustains regime losses and control requirements. The ring does not mean “infinite reuse of the same energy”.
Two boundaries, one physical flowThe dual-boundary principle applies to the ring: the 9 V line is external with respect to the regime path (an input at that boundary) and internal with respect to Frame 0 (not a boundary crossing). Both statements are simultaneously true at their respective boundaries. Confusing the two produces boundary-definition errors, not physical conclusions.
Frame 0 is the outer energetic boundary of the entire installation — the only boundary at which the question of the source is addressed. The internal boundaries — the input of block 5, the secondary extraction node 10–11, the output of bridge 12, the DC bus, the 9 V and 5 V lines — are functional cross-sections that answer the question “how does the system work?”. They are not designed to answer the source question, and treating one of them as if it were Frame 0 is a boundary-definition error.
Boundary-relative attribution (locked)The question “where does the energy come from?” has no universal answer — it has a boundary-relative answer. The same physical situation yields different correct answers at different analytical boundaries. In the VENDOR canon the source question is addressed to Frame 0 — the pre-defined complete device boundary.
The locally correct answer at each internal boundary
· Customer output — the block 13 output stage; measured directly as Pcustomer.
· DC bus of block 13 — the rectified flow arriving from bridge 12 together with the internal redistribution of block 13; the regime-supply and control lines are drawn from this bus.
· Bridge 12 — the ACHF flow arriving from the secondary extraction node 10–11.
· Secondary extraction node 10–11 — the EMF induced in secondary winding 10 by the coupled HF regime of block 5 through Faraday induction; the load pushes back on the primary circulation by Lenz's rule, which is why internal amplitudes are dynamic.
· Input boundary of block 5 — the ~24 V / ~24 A power bus formed by block 3, together with the internal regime supply returning through the 9 V line at the startup entry point.
· Frame 0 — the full inventory of channels crossing the outer boundary, together with the change in the internal store dEstored/dt; closure is checked against the full inventory (see Q 12).
All local “sources” are links in one chain of transfer, conversion, storage and distribution; they are not independent external sources of Frame 0. The word “source” applied to internal flows is forbidden. The ring is external to the regime path and internal to Frame 0 — both statements are true on their respective boundaries.
The 9 V line is the regime-supply ring that closes the topology in steady state. It runs from the DC bus of block 13 back to the startup entry point — the same schematic point at which the external startup accumulator was connected during initiation. Once the regime is established the startup accumulator is physically disconnected; its role as a boundary condition at that same point is taken over by the internal 9 V line.
The 9 V line feeds the regime path; the ~24 V / ~24 A power bus into block 5 is formed by the block 3 conversion aggregate, not directly from the 9 V line. These two lines are distinct internal ports; their values do not form an input–output pair for computing an efficiency and are not compared directly. Numerical value 9 V is a canonical boundary of the architecture; power on this line is measured separately from the 24 V bus. All ratings and the physical implementation of the intermediate stages are closed engineering documentation.
What the 9 V line is notThe 9 V line is not a direct serial throughput to the load. It sustains regime losses and control requirements; it is not the flow that reaches the customer. It does not cross Frame 0 and is not counted in Pin,boundary. It does not mean “reuse of the same energy”: in the steady state energy moves through the ring, and the origin of that energy is a Frame 0 question.
Why the loop closes at the startup entry pointThe startup entry point plays two roles at different times: during initiation it accepts the external startup accumulator; in steady state it accepts the internal 9 V line. Same schematic point, different boundary conditions. This substitution is the mechanism that lets the startup port be physically disconnected without collapsing the regime.
Coulombs do not replace joules. They give a continuous methodological description of the entire route. The local law of charge conservation is exact at every node and does not require synchronised power pairs or the disclosure of a closed topology. The watt language is discrete per port: on oscillating cross-sections the active power flow cannot be inferred from separate voltage and current amplitudes, and to an observer working in separate amplitudes energy appears to “disappear” in the resonance and “re-appear” at the rectifier. This is an artefact of the language, not physics; the coulomb accounting is continuous along the whole route.
A watt balance requires an approved protocol of synchronised measurements at correct ports; before that protocol is approved, watt calculations produce measurement error, not precision. The energy register will be activated by protocol (scientific supervisor + independent test organisation); until then any external watt estimates are non-canonical. Joules are not cancelled — they are deferred, until the energy register is activated under the approved protocol.
Three charge ensembles — the coulomb pictureThree canonical charge ensembles carry the charge model of the architecture: (i) the output ensemble at the customer interface — charge that reaches the load; (ii) the storage-and-supply ensemble along the ring — charge that supports the regime and the auxiliaries; (iii) the regime ensemble inside block 5 — charge that participates in the coupled resonant dynamics. The ensembles are not exclusive; a given charge participates in more than one ensemble across a cycle. What crosses Frame 0 is a subset of the output ensemble at the customer boundary, plus whatever else is inventoried at Frame 0.
Charge turnover is not powerCharge turnover characterises the intensity of internal circulation — the repeated use of the same charge inside the ring. It is not power. Four charge-rate categories are named separately and are never used interchangeably: Q̇net (net crossing a boundary), Q̇abs (absolute crossing including recirculation), Q̇turn (turnover of the local ensemble) and IRMS (root-mean-square current). Higher turnover at the same per-event energy budget appears physically as higher pulsed current amplitude, not as more energy.
The “plus” on two registersThe “plus” in coulombs is the charge turnover of a high-Q resonance — reuse of charge, not its creation, and never a power figure. The “plus” in joules is the question of the deferred energy register at the complete device boundary (Frame 0), closed neutrally under outcome classes A–E.
In classical AC and resonant electrical engineering, the net real (active) power crossing any defined boundary is defined by the phase-aware time average of instantaneous voltage and current:
In sinusoidal steady state the three quantities are related by S² = Preal² + Qreactive². For non-sinusoidal or pulsed signals additional distortion terms enter the decomposition; the general canonical statement is that only Preal carries net energy across the boundary, and only Preal is counted as Pcustomer in the Frame 0 accounting.
In a high-Q resonant regime, energy oscillating between capacitive and inductive stores at internal nodes can reach amplitudes that substantially exceed the real power crossing any boundary. This does not mean energy creation. Stored internal field energy can exceed the per-cycle sustaining input by a factor related to the quality factor Q — standard high-Q accumulation, not creation.
Implication for VENDOR interpretationWhen observing internal amplitudes inside block 5 (for example through RF probes or oscilloscopes on internal nodes), the instantaneous V · i products can become orders of magnitude larger than the real power crossing any boundary. This does not mean a correspondingly large real power is produced inside block 5. It means significant reactive energy circulates in the high-Q resonant regime. Preal across any boundary of the circulating regime is only the fraction associated with losses and with real extraction into the load path.
Block 5, BBMS,
startup
Three questions on block 5 as a controlled system of coupled electromagnetic resonators, on the BBMS supervisory layer, and on the startup sequence characterised in charge terms.
Block 5 is a controlled system of coupled electromagnetic resonators — not a single ideal transformer. Inside its functional boundary there are three coil structures, each with a distinct role:
· Tesla coil — the excitation path that puts energy into the HF resonant regime;
· Resonator — the regime path that holds the coupled HF resonant regime at ~2.45 MHz;
· Secondary winding 10 — the winding that feeds the secondary extraction node 10–11.
Useful power is drawn through the secondary extraction node 10–11 (secondary winding 10 together with capacitor 11), which is the output electrical boundary of block 5. This is the extraction node; there is no parallel branch. From node 10–11 the flow proceeds through the single canonical diode bridge (bridge 12) into block 13, where the tertiary power transformer buffers load influence and provides the galvanic safety boundary of the output stage.
Terminology disciplineThe term tertiary is reserved exclusively for the tertiary power transformer of block 13. It is not applied to winding 10 or to any other extraction element. Winding 10 is the secondary winding of block 5; the extraction node it feeds is node 10–11.
Bidirectional coupling and load pushbackExtraction coupling at node 10–11 is bidirectional: by Lenz's rule the load pushes back on the primary circulation inside block 5. This is the reason internal amplitudes are dynamic and load-dependent, and the reason BBMS supervision is required to hold the regime inside its operating window. Capacitor 11 is not merely a filter; depending on topology it participates in resonant tuning, reactive compensation, charge accumulation, impedance matching, signal formation and preparation for rectification.
BBMS is the distributed supervisory system of energy state and dynamic regime stability. It is not identical to any one board or processor; it is not a classical Battery Management System. The historical expansion “Battery Boundary Management System” is retained for continuity — it does not mean the battery is the source, and BBMS is not derived from ordinary battery management.
What BBMS doesBBMS holds the regime inside its operating window, prevents amplitude runaway and decay, coordinates the distribution of power between the regime supply, control and the customer output, and executes startup and shutdown sequences. Its main control question is not “how much power is available at the output?” but “how much power can be permitted at the output right now without destroying the internal regime?” BBMS steers the regime behind the load; its algorithmic target is Rcontrol(t) → 0, a regulation quantity, not a metrological measurement.
Bidirectional supervisionBBMS is a two-sided regulator. On one side it prevents runaway: if internal amplitudes tend to grow beyond the stability window, BBMS limits the return of the regime supply and redirects transient excess into managed storage. On the other side it prevents decay: if a load step causes the useful-power extraction to grow, BBMS protects a minimum regime supply back into the regime path, coordinates the switching windows, and uses managed storage as a timing reserve. In both directions BBMS enforces the stability window; it does not create energy on either side.
Why BBMS is not an energy sourceBBMS regulates the redistribution of energy already inside the architecture. The battery it supervises is managed storage, not a hidden source: it absorbs transient excess and covers transient deficit, always inside the stability window. Configuration details (specific control-loop topology, gain parameters, response timing) are engineering know-how at TRL 5–6 and are not disclosed. Nothing about BBMS behaviour presumes any outcome of the Frame 0 accounting in either direction.
Startup is characterised in charge terms. The external ~9 V startup accumulator delivers a bounded quantity of charge through the startup port at the startup entry point:
Numerical values of Qstartup are the subject of validation; the canon does not publish an energy figure for startup, and no separate energy symbol is introduced. The charge cost per coulomb (~9 J/C) is fixed by the startup source; the charge count is set by the initiation requirement of the architecture.
SequenceDuring initiation, current from the startup accumulator flows through the startup entry point into block 3 and into the internal loading of block 5. When the initiation condition is met, block 5 enters its coupled HF resonant regime. Node 10–11 then feeds bridge 12, which forms the DC bus of block 13. At that point block 13 asserts the 9 V regime-supply line at the startup entry point. The external startup accumulator is physically disconnected; its role as a boundary condition at the same schematic point is taken over by the internal 9 V line.
What startup does not doStartup does not presume any outcome of the Frame 0 accounting in steady state. It is initiation of the regime, not a claim about the source. The fact that the startup accumulator is disconnected does not, on its own, establish that the boundary-crossing input in steady state is zero; it removes the accumulator as a boundary flow at that point. The Frame 0 accounting is closed against the full inventory of boundary channels, not against the startup port alone.
After startup — product forkOnce block 13 asserts the DC bus, the base output is DC (target window 48–75 V DC; base telecom rating 48 V / 25 A per ETSI EN 300 132-2). The AC configuration adds a DC-link and an inverter for a ~220 V / ~16 A / 50 Hz output; the inverter is not part of the physical core and is interchangeable as an output module. Product line: 48V DC First. 220V AC Later.
Frame 0 closure,
framework vs metrology
Four questions on how Frame 0 balance closure is verified, on the boundary between an interpretation framework and a metrology proof, on the current TRL 5–6 validation status and the six-jurisdiction patent family, and on the difference between the patent description and the engineering implementation.
Frame 0 closure is verified through synchronised measurement of the full inventory of boundary-crossing channels, the customer-side active power, the change in stored energy of the system, and all real losses, under a defined measurement-uncertainty budget. The metric is the balance residual R = Pin,boundary − Pcustomer − Ploss,total − dEstored/dt; the balance is closed when |R| falls within the expanded uncertainty U = k · uc.
The full boundary inventoryBoundary channels considered at Frame 0: conductors, protective earth, neutral, control and instrumentation cables, shields, capacitive and inductive coupling, RF exchange, thermal exchange, mechanical energy, chemical sources, together with the internal change dEstored/dt. Closure is checked against the full inventory of channels, not against a shortlist of electrical ports. No channel is asserted absent without measurement.
Outcome classes A–E (locked)
The result is classified strictly under one of five outcomes, without prejudice:
· A — the balance closes through a measured external input.
· B — the balance closes through a decrease in stored energy.
· C — an unaccounted channel is discovered.
· D — a measurement artefact is discovered.
· E — an unresolved closure residual with |R| > U, subject to a mandatory interpretation order: recalibration → extension of the boundary inventory → phase error → common-mode and capacitive currents → change in stored energy → thermal and chemical channels → independent reproduction → only then a new physical hypothesis.
A separate result records regime reproducibility. The project commits publicly to all outcomes A–E, including a negative one. No possible outcome is presumed in advance.
The distinction between an interpretation framework and a metrology proof is structural. Both are required for engineering credibility; neither replaces the other.
What this framework doesDefines the canonical accounting identity at Frame 0; defines the canonical vocabulary of the complete device boundary and of internal boundaries; defines the canonical functional levels 0–5 and the ring architecture in the steady state; defines the terminology of the discharger, of block 5, of the extraction node 10–11, of bridge 12 and of block 13; defines the canonical charge model (the three ensembles, charge turnover as distinct from power); defines the canonical order «route → balance → attribution»; defines the outcome classes A–E under which independent metrology returns its result.
What this framework does not doIt does not present primary metrological data; it does not present independent third-party validation results; it does not close the Frame 0 balance under an accredited protocol. That work is the independent boundary-metrology milestone that follows the current validation stage (see Q 14). The framework alone is not a proof; the metrology alone, without framework, would be uninterpretable; together they form the complete engineering case.
The honest scientific positionThe interpretation framework defines what must close. Independent boundary metrology is the protocol that answers whether it closes. Whether the numerical closure R → 0 holds within accredited measurement uncertainty under long-duration synchronised metrology is a separate empirical question, to be answered under the outcome classes A–E. Openness of that question is a position of rigour, not evasion — the canon commits to the protocol that will settle it, in either direction, without presuming any outcome.
VENDOR is at TRL 5–6 — pre-commercial validation stage, with system-level validation in a controlled laboratory environment. On the validation roadmap, TRL 6 is the milestone of independent boundary metrology at Frame 0; TRL 8 is the milestone of controlled disclosure of the engineering implementation. The two milestones are independent and both public.
Six-jurisdiction patent family (common priority date 2023-04-05)EU trademark: EUIPO No. 019220462 (VENDOR mark, registered).
What TRL 5–6 means for VENDORCumulative operational documentation exceeding 1,000 hours, including a documented 532-hour continuous operating segment. Multi-module architecture tested. Failure modes identified and mitigated. Boundary-level energy accounting evaluated under internal validation methodology. Detailed segment-level metrics are documented on the endurance test page.
What TRL 5–6 does not meanNot yet independently verified by an external metrology body at Frame 0 under an accredited protocol (that is the TRL 6 milestone). Not yet released for commercial deployment. The controlled disclosure of the engineering implementation is a TRL 8 milestone. The current stage is a stage descriptor of a normal deep-tech engineering programme — not a credibility signal in either direction.
The patent family covers the maximum defensible architectural scope, in order to protect the intellectual property across all feasible implementations at the patent horizon. It describes operating principles, claimed effects and circuit topology in the broadest formulations that patent law admits. The engineering implementation is a specific realisation of that scope, protected as confidential engineering know-how; the two are not identical documents and are not intended to be.
What the patent text is — and is notThe patent text is a patent-level analytical description. Where it invokes classical analytical frameworks — for example the Townsend pre-breakdown framework — those frameworks are patent-level analytical references, not statements about the measured mechanism of the current implementation. The specific geometry, winding topology, coupling parameters, control logic, frequency tuning, component selection and closed engineering documentation of the current implementation constitute know-how that is not publicly disclosed at this stage of the disclosure matrix.
Disclosure matrix (short form)
· Public — the canonical framework of this FAQ, the functional levels 0–5, the ring architecture, the Frame 0 accounting identity, the boundary language, the six-jurisdiction patent family, the endurance data.
· Closed (NDA) — ratings and physical implementation of intermediate stages; specific control logic and BBMS parameters; specific coupling values; frequency tuning; winding topology.
· TRL 7–8 — controlled disclosure of the engineering implementation.
Manufacturing path,
deployment path
Five questions on disclosure policy, engineering challenges already addressed, production readiness, deployment value and the structure of investor and partner access.
Performance figures — per-stage conversion efficiencies, operating ranges, load characteristics — are disclosed progressively, bound by validation stage (TRL), by the disclosure matrix of the canon, and by ordinary IP-protection practice. Until independent boundary metrology at Frame 0 completes, watt-level figures published outside the approved protocol are non-canonical; the project's own materials use the voltage–current–charge series at the canonical boundaries of the architecture and do not publish products of separately measured quantities as active power.
Disclosure tiers (canonical matrix)
· Public — the canonical framework of this FAQ (functional levels 0–5, the ring architecture, the Frame 0 accounting identity, the boundary language, outcome classes A–E); the six-jurisdiction patent family; the endurance record documented on the endurance test page.
· Closed (NDA) — structured technical review materials, validation methodology, operating-range summaries, manufacturing-readiness documentation; ratings and physical implementation of intermediate stages; control-loop and BBMS parameters; specific coupling values; frequency tuning; winding topology.
· TRL 6 — independent Frame 0 boundary metrology and classification of the result under outcomes A–E.
· TRL 7–8 — extended certification, production-transfer documentation and controlled disclosure of the engineering implementation.
The following engineering challenges have been identified, characterised and addressed through controlled engineering pathways at the current validation stage; the details are closed engineering documentation.
Regime discipline under repeated switching. Long-term operating behaviour of the discharger elements (attached to block 3 switching node and to block 5 internal switching) under repeated events, characterised at the current validation stage. Both publicly acknowledged discharger types — open (gas) and vacuum — are covered by the operating discipline; the charge logic is identical between them; differences in operational characteristics and durability are engineering-selection questions.
Parameter drift under environmental conditions. Effects of humidity, temperature and pressure on regime stability have been evaluated. Operating window and BBMS adaptation logic are defined and validated.
EMC and safety architecture. The MHz-range resonant regime inside block 5 imposes non-trivial EMC control; field containment, shielding architecture and emission compliance are part of the certification track.
Manufacturing and integration documentation. The technical documentation package is being structured for OEM/EMS transfer. Component specifications, assembly protocols and quality-control procedures are defined at the current validation stage.
The VENDOR architecture belongs to the electrical and electronic systems class. Assembly can be organised by qualified OEM/EMS manufacturers working with power electronics, control boards, high-voltage components and industrial enclosures. No proprietary manufacturing infrastructure is required.
Current production-readiness status. The technical documentation package is being structured for OEM/EMS transfer. Component selection, assembly discipline and quality-control protocols are defined at the current validation stage. The architecture is compatible with standard contract-manufacturing workflows.
The main complexity is not in manufacturing capacity but in component-selection precision, calibration protocol, regime initiation procedure and quality-control methodology — all documented and closed as engineering know-how at TRL 5–6.
The value of VENDOR is not defined by any ratio claim ahead of the metrology. It is defined by what the operating architecture removes from the infrastructure equation, and by the ETSI-compliant DC and AC interfaces it presents to the site.
No continuous fuel logistics. No diesel supply chain, no storage, no delivery scheduling, no price exposure. For remote and weak-grid sites, fuel logistics is often the dominant operating-cost driver.
No battery-dominated charge–discharge architecture requiring periodic replacement of large energy-storage packs. No large-pack replacement intervals, no storage-bank capacity loss, no cold-temperature power degradation.
No mechanical conversion stages. No rotating parts, no rotor maintenance, no vibration, no acoustic signature.
Sustained availability under variable load. The architecture maintains output stability under load variation through the supervisory action of BBMS, which steers the regime behind the load.
Product line: 48V DC First. 220V AC Later. Base configuration is DC (target window 48–75 V DC; base telecom rating 48 V / 25 A per ETSI EN 300 132-2). The AC configuration adds a DC-link and an inverter for a ~220 V / ~16 A / 50 Hz output; the inverter is not part of the physical core and is interchangeable as an output module.
Access is organised by validation stage and engagement type, along the canonical disclosure matrix.
Current stage — publicCanonical framework of this FAQ. Six-jurisdiction patent family (ES2950176B2 granted · WO2024209235A1 PCT · EP4693872A1 regional phase (37 EPC states) · US20260088633A1 national phase · CN119096463A national phase · IN 202547010911 national phase). EUIPO trademark 019220462. Endurance record. TRL 5–6 validation framework. Architecture overview.
Current stage — under NDAStructured technical review materials, validation methodology, operating-range summaries and manufacturing-readiness documentation under controlled NDA access. Engineering solution architecture for identified challenges, shared progressively with qualified reviewers.
TRL 6 — independent Frame 0 boundary metrologyIndependent Frame 0 boundary metrology and classification of the result under outcome classes A–E. The project commits publicly to all outcomes A–E, including a negative one; no possible outcome is presumed in advance.
TRL 7–8 — controlled disclosure and production transferExtended certification, production-transfer documentation and controlled disclosure of the engineering implementation. Extended certified technical documentation under controlled access. Specifications ready for production transfer. Preparation for controlled commercial deployment.
Levels 0–5, ring,
Frame 0 accounting
Three questions establishing the canonical evaluation stack (levels 0–5 with the steady-state ring plus the Frame 0 accounting identity), why the architecture appears counter-intuitive to reviewers trained on single-ratio converter formalism, and the field-mediated transfer semantics that prevent an “electrons carry the energy” misclassification.
VENDOR is not evaluated through a single whole-device converter-efficiency ratio. It is evaluated through the canonical stack of the architecture: the functional levels 0–5 with the patent numbering, the steady-state ring that closes the topology and the Frame 0 accounting identity. Each level has its own accounting language; conclusions across levels are made in the strict order route → balance → attribution.
Level 0 — startupExternal ~9 V startup source. Startup is characterised in charge terms: Qstartup = ∫ istart(t) dt (coulombs) at ~9 J/C. Numerical values are the subject of validation; no separate energy symbol is introduced for startup. After the regime is established the startup accumulator is physically disconnected; its role as a boundary condition at the same schematic point is taken over by the internal 9 V line.
Level 1 — block 3 (aggregate)Block 3 contains the electrical conversion and switching functions disclosed at patent level and establishes the ~24 V / ~24 A input boundary of block 5. These are illustrative prototype boundary values, subject to validation; the converter topology, component values, switching sequence and control implementation remain confidential. The switching node of block 3 is a discharger; the term “discharger” is always used with an explicit attachment (block 3 switching node or block 5 internal switching).
Level 2 — block 5A controlled system of coupled electromagnetic resonators, not a single ideal transformer. Three coil structures inside its functional boundary: the Tesla coil for excitation, the resonator for holding the regime and secondary winding 10 that feeds the secondary extraction node 10–11. The coupled HF regime runs at ~2.45 MHz. Internal amplitudes are dynamic and load-dependent; the load pushes back on the primary circulation by Lenz's rule. BBMS supervision is required to hold the regime inside its operating window.
Level 3 — secondary extraction node 10–11Secondary winding 10 with capacitor 11 — the output electrical boundary of block 5. This is the extraction node; there is no parallel branch. Capacitor 11 is not merely a filter; it participates in resonant tuning, reactive compensation, charge accumulation, impedance matching, signal formation and preparation for rectification.
Level 4 — bridge 12The single canonical diode bridge in the system (ACHF → DC), located at the boundary of block 5. It is the first element beyond block 5. The internal rectification of the block 13 output stage is a module internal and is not counted as a second architectural rectifier.
Level 5 — block 13 (aggregate)DC bus; the 9 V regime-supply line and the 5 V control line; BBMS; the tertiary power transformer (buffers load influence and provides the galvanic safety boundary of the output stage); own switching; internal rectification of the output module; the customer output; the DC/AC fork. The term “tertiary” is reserved exclusively for the block 13 power transformer and does not apply to winding 10.
The steady-state ringThe 9 V regime-supply line and the ~24 V / ~24 A block 5 input boundary are distinct internal ports; their values do not form an input–output pair for computing an efficiency and are not compared directly. The 9 V line, the regime supply and the excitation bus are internal flows relative to Frame 0; they do not enter Pin,boundary. The ring is public as an architectural principle; ratings and physical implementation of intermediate stages are closed engineering documentation. The regime-supply ring (9 V line) sustains regime losses and control requirements — it is not direct serial throughput to the load, and it does not cross Frame 0.
Frame 0 — the accounting identityR = Pin,boundary − Pcustomer − Ploss,total − dEstored/dt is the balance residual. Independent metrology closes the balance when |R| falls within the expanded uncertainty U = k · uc. The identity is an accounting identity: it must hold at all times, it checks the completeness of the accounting, and it does not name the source. Per-stage η values apply only to specific converter nodes on their own boundaries and are defined only in periodic steady state on electrical ports; they do not combine into an end-to-end ratio.
The architecture appears counter-intuitive when a reviewer expects a single-ratio linear converter, in which Pcustomer scales transparently with a boundary input Pin,boundary at a single boundary. VENDOR is not a converter in that sense — it is a multi-level resonant power architecture with an internal store, a controlled feedback path and a coupled resonant regime. The apparent counter-intuition disappears when three canonical disciplines are applied.
Three questions that are never conflated
· Mechanism (“how is energy transferred?”) — closed by the charge model together with classical electrodynamics.
· Accounting (“does energy balance close?”) — closed by the Frame 0 identity and by measurements only.
· Attribution (“what is the source?”) — closed only after a closed balance together with a boundary inventory.
An answer to the first question is never presented as an answer to the third.
The question “where does the energy come from?” has no universal answer. It has a boundary-relative answer: the same physical situation yields different correct answers at different analytical boundaries. In the VENDOR canon the source question is addressed to Frame 0 — the pre-defined complete device boundary. Internal boundaries (input of block 5, node 10–11, bridge 12, DC bus, 9 V and 5 V lines) answer “how the system works”, not “where the source is”.
The single-boundary ruleWhere is the boundary drawn physically; which conductors, fields and couplings cross it; where is voltage measured; where is current measured; do the two belong to the same energy flow. Taking a current at one level, a voltage at another and calling the product a power at a third level is forbidden. Values measured at different boundaries are not compared directly; their ratio is not an efficiency.
Where the Townsend framework entersWhere the Townsend pre-breakdown framework is invoked in the patent documentation, it is a patent-level analytical framework, not a statement about the measured mechanism of the current implementation. Carrier multiplication in the pre-breakdown window is a conductivity effect, not energy multiplication: it characterises the conductivity transition in the gap; it does not multiply the charge of the system and it does not multiply energy.
A common engineering shorthand describes a circuit as “source pushes electrons → electrons carry the energy → electrons deliver energy to the load”. The shorthand is pedagogically convenient but physically incomplete. In nonlinear resonant architectures with an internal store, a coupled resonant regime and a controlled feedback path, this shorthand breaks — and a legitimate architecture begins to look inexplicable.
What electrons actually doIn a conductor, electrons carry electric charge (q = N · e), momentum, mass and quantum properties. They are not the principal carrier of macroscopic energy transfer — the drift velocity in a conductor is of the order of millimetres per second; a lamp lights up effectively instantaneously after the circuit closes. This is impossible to explain by a “charge in motion = energy in motion” picture.
What actually carries the energy — the Poynting vectorWithin the standard Maxwell–Lorentz description, the carrier of electromagnetic energy is the electromagnetic field, not the electron. The energy flux is described by the Poynting vector:
Energy flux propagates around the conductor (in the surrounding space and in dielectric elements), not inside the metal. This is the standard interpretation of classical electrodynamics presented in standard graduate-level textbooks. Electrons in this picture act as a field-responsive carrier ensemble — they respond to field changes via the Lorentz force F = qE and redistribute charge so as to enforce conductor boundary conditions. They are not “trucks” carrying energy.
Coulombs describe the route; joules the balanceThe project's working paradigm is coulomb-based: the local law of charge conservation is closed at every node by Kirchhoff's balances, without any flow crossing the device boundary; kilo-coulombs per second can circulate internally without a corresponding kilowatt of active output. Charge turnover is not power. Four charge-rate categories are named separately and are never used interchangeably: Q̇net, Q̇abs, Q̇turn and IRMS. Joules are not cancelled — they are deferred, until the energy register is activated under the approved protocol; until then external watt estimates are non-canonical.
Canonical interpretive mapping for VENDOR
· Electron flow → carrier response to local field; boundary-condition medium.
· Townsend multiplication → conductivity transition (the gap's ability to redistribute electromagnetic energy), not energy creation.
· Coupled HF resonance in block 5 → field-energy storage; oscillation between electric (capacitive) and magnetic (inductive) storage forms.
· Extraction at node 10–11 → field-coupled output extraction into bridge 12 and block 13; delivered energy propagates as Poynting flux, not as electron transport.
· 9 V regime-supply ring → internal redistribution ring, not direct serial throughput to the load, not a boundary input.
· Energy → a conserved scalar accounting quantity closed at Frame 0, not a material substance moving through the metal.
Levels 0–5,
metrology at Frame 0
Six questions for engineers and qualified reviewers. Why event-level arithmetic on its own does not resolve the boundary picture; how the coupled HF regime of block 5 relates to the extraction at node 10–11; why the three coil structures of block 5 are not a low-leakage transformer; what the actual TRL 5–6 engineering challenges are; how independent Frame 0 metrology is structured; and how the canonical disclosure matrix keeps the source question addressed to Frame 0 rather than to any internal boundary.
Because the discharge event is not a converter with a scalar input–output ratio — it is a boundary event of the coupled HF regime of block 5. The physical quantities that are meaningful at event level (per-event charge, per-event conductivity transition, per-event field redistribution) do not carry a whole-device meaning on their own; they enter a larger picture in which the ring closes the steady state and the accounting identity closes on Frame 0.
What is legitimate at event levelThe event-level description is charge-model: at each discharge event a local pulse discharge channel opens under a voltage boundary condition; charge on adjacent local reservoirs is redistributed; charge conservation on each plate closes trivially by Kirchhoff's balances. Where the Townsend pre-breakdown framework is invoked, it is a patent-level analytical framework, not a statement about the measured mechanism of the current implementation; carrier multiplication in the pre-breakdown window is a conductivity effect, not energy multiplication.
What is not legitimate at event levelAn event-level power figure inferred from separately measured amplitudes on oscillating cross-sections is a language artefact: on oscillating sections active power flow cannot be inferred from separate voltage and current amplitudes. Products of separately measured quantities are not published as active power in the canon, and event-scale ratios are not carried to whole-device conclusions.
Where the whole-device conclusion livesWhole-device conclusions live at Frame 0 — at the accounting identity Pin,boundary = Pcustomer + Ploss,total + dEstored/dt and at the balance residual R that independent metrology will close within the expanded uncertainty U = k · uc. Per-stage η values do not combine into an end-to-end ratio, because in the steady state the architecture is a ring with a distribution tree, not a serial chain.
Extraction is at the secondary extraction node 10–11, not through a parallel branch. Secondary winding 10 is coupled to the coupled HF regime of block 5 through Faraday induction; capacitor 11 completes the extraction node as the output electrical boundary of block 5. This is the extraction node in the architecture. The term tertiary is reserved exclusively for the block 13 power transformer and does not apply to winding 10.
Why the Q-factor is essential (and what it does not do)Block 5 holds a high-Q coupled resonant regime; a high loaded Q means that stored internal field energy can exceed the per-cycle sustaining input by a factor related to Q. This is high-Q accumulation, not creation: it says that a small per-cycle input can sustain a large stored oscillation, not that a small per-cycle input produces a large boundary output. The Q-factor governs how long energy remains stored relative to losses and extraction; it does not multiply real power at any boundary.
Bidirectional coupling and load pushbackExtraction coupling at node 10–11 is bidirectional: by Lenz's rule the load pushes back on the primary circulation inside block 5. This is the reason internal amplitudes are dynamic and load-dependent, and the reason BBMS supervision is required to hold the regime inside its operating window. As the customer draws more real active power, the regime is steered by BBMS — its main control question is not “how much power is available at the output?” but “how much power can be permitted at the output right now without destroying the internal regime?”
The specific working geometry is closedThe general topology of the coupled resonant regime inside block 5 is publicly described in the patent family; the optimised working geometry, the loaded Q under the loaded operating regime, the coupling values, the frequency tuning and the control-loop parameters of BBMS are closed engineering documentation at TRL 5–6 under the canonical disclosure matrix.
Because block 5 does not operate in transformer mode. It operates as a controlled system of coupled electromagnetic resonators, and its three coil structures carry three distinct functions inside the same functional boundary.
Tesla coil — excitationThe excitation path that puts energy into the coupled HF regime under the phase-coherent action of the block 5 internal switching. It is not an energy source in itself; it acts as the phase-coherent excitation element of the coupled system.
Resonator — regimeThe regime path that holds the coupled HF resonant regime at ~2.45 MHz. Internal amplitudes are dynamic and load-dependent; the resonator supports the stored electromagnetic field configuration of the regime.
Secondary winding 10 — feeds the secondary extraction node 10–11The winding that feeds capacitor 11 to form the output electrical boundary of block 5 — node 10–11. This is the extraction node; there is no parallel extraction inside block 5.
In a low-leakage transformer, all secondaries essentially see the same flux, and the design target is high mutual inductance with low leakage inductance. In a coupled-resonator system, each coil structure has a distinct dynamic function — excitation, regime, extraction — and the geometry is tuned for the coupled dynamics, not for lumped mutual-inductance transfer.
When block 5 is correctly understood as a controlled system of coupled electromagnetic resonators with a controlled pre-breakdown discharge in the switching path, the real engineering challenges become specific and bounded. They are not fundamental-physics questions — they are implementation-tolerance and metrology questions on the normal deep-tech engineering path.
Frequency stability under geometric toleranceThe coupled resonant regime is sensitive to the geometry of the coil structures. Turn spacing, conductor cross-section, dielectric environment and thermal expansion shift the operating point. Engineering question: for each geometric parameter, what tolerance window keeps the loaded regime sufficient to sustain operation under full extraction load?
Loaded-Q behaviour under extractionAt full extraction load, the loaded Q of the regime is lower than the unloaded Q. Engineering question: how much margin remains before the loaded-Q drop exits what BBMS can compensate through the supervisory action that steers the regime behind the load?
Skin effect and ohmic losses at MHz-range operationAt an operating frequency of the order of a few MHz, AC resistance in the coil conductors due to skin effect is significantly higher than the DC resistance. Ohmic losses in the resonator coils are expected to be a major loss mechanism and a thermal constraint — not a fault of any consumable inside the switching unit. Engineering question: thermal management of the coil structures under sustained circulating power.
EMC in an MHz-range regimeAn MHz-range resonant regime requires non-trivial EMC control. EMC certification per EU Directive 2014/30/EU is a real engineering task, not a formality. Field containment, shielding architecture and emission compliance are part of the certification track.
A real-power measurement at the customer AC output alone does not characterise what happens inside the MHz-range coupled resonant regime of block 5. To independently verify the Frame 0 accounting, the instrumentation must directly capture the resonator stage and the full boundary inventory. The scope of the pending independent boundary metrology milestone (TRL 6) includes the following components.
1. Synchronised boundary metrology. Simultaneous measurement of all boundary-crossing terms — Pin,boundary across the full inventory of channels, Pcustomer, Ploss,total, dEstored/dt — over integrated long-duration windows. This is the canonical measurement of the balance residual R at Frame 0.
2. Full boundary inventory. Conductors, protective earth, neutral, control and instrumentation cables, shields, capacitive and inductive coupling, RF exchange, thermal exchange, mechanical energy, chemical sources, together with the change in the internal store dEstored/dt. Closure is checked against the full inventory of channels, not against a shortlist of electrical ports.
3. Calorimetric loss closure. Full thermal accounting of Ploss,total through accredited calorimetric protocols, cross-validated with electrical-side loss estimates. Independent confirmation that Pin,boundary − Pcustomer is accounted by measurable irreversible losses and stored-energy variation, consistent with the accounting identity.
4. Long-duration energy integral. Cumulative ∫P dt over continuous test segments, including extended synchronised windows with boundary instrumentation.
5. Phase-aware power measurement. Pcustomer is a phase-aware time average ⟨v(t) · i(t)⟩ at the customer interface. Wideband current probes (bandwidth well above the coupled regime frequency), isolated voltage probes and real-time digital integration recover the real-power component. Products of separately measured RMS amplitudes are not treated as active power (see Q 08b).
6. Independent third-party verification and outcome classes A–E.
An accredited independent testing body executes the protocol and classifies the result strictly under one of five outcomes:
· A — the balance closes through a measured external input.
· B — the balance closes through a decrease in stored energy.
· C — an unaccounted channel is discovered.
· D — a measurement artefact is discovered.
· E — an unresolved closure residual with |R| > U, subject to a mandatory interpretation order: recalibration → extension of the boundary inventory → phase error → common-mode and capacitive currents → change in stored energy → thermal and chemical channels → independent reproduction → only then a new physical hypothesis.
The canonical disclosure matrix partitions everything about VENDOR into three tiers, along the axis of validation stage and IP-protection posture. The public tier gives the boundary language and the identity that must close; the closed and controlled tiers hold the engineering realisation.
Public — the canonical frameworkThe canonical positioning of the architecture as a multi-level resonant power architecture. The functional levels 0–5 with the patent numbering. The ring architecture in the steady state. The Frame 0 accounting identity, the balance residual R and the outcome classes A–E. The boundary language of the complete device boundary and of the internal boundaries. The charge-model discipline (three canonical charge ensembles, charge turnover as distinct from power). The six-jurisdiction patent family (ES2950176B2 granted · WO2024209235A1 PCT · EP4693872A1 regional phase (37 EPC states) · US20260088633A1, CN119096463A and IN 202547010911 national phase) and the EUIPO trademark 019220462. The endurance record documented on the endurance test page.
Closed (NDA) — engineering realisationRatings and physical implementation of intermediate stages between the functional levels. The specific control-loop topology, gain parameters and response timing of BBMS. Specific coupling values in the coupled resonators of block 5. Frequency tuning of the coupled regime. Winding topology and geometry inside block 5. Component selection, calibration protocol, regime initiation procedure and quality-control methodology.
TRL 6 — independent Frame 0 boundary metrologyIndependent Frame 0 boundary metrology and classification of the result under outcome classes A–E. The framework defines what must close; independent metrology answers whether it closes, in either direction, without any outcome presumed in advance.
TRL 7–8 — controlled disclosure and production transferExtended certification, production-transfer documentation and controlled disclosure of the engineering implementation. Extended certified engineering documentation under controlled access. Specifications ready for production transfer.
Five clarifications,
in one place
Is the startup accumulator the energy source of VENDOR?
The startup accumulator is the external startup source during initiation, but it is not a steady-state operating source after disconnection. Startup is characterised in charge terms: Qstartup = ∫ istart(t) dt at ~9 J/C; numerical values are the subject of validation, and no separate energy symbol is introduced. After the regime is established, the startup accumulator is physically disconnected; its role as a boundary condition at the same schematic point is taken over by the internal 9 V line.
Is the discharger's medium an energy source?
The discharger is not declared to be an energy source, a fuel or a consumable resource; those are not roles the canon attributes to it. The medium sets the boundary condition for the gap. Whether any medium-related channel is a net boundary input at Frame 0 is inventoried and settled by measurement under the outcome classes A–E — no medium mechanism is named as a source, and none is asserted absent. Both publicly acknowledged discharger types (open gas and vacuum) share the same charge logic; the difference is in operational characteristics and durability.
What is the role of the 9 V ring?
The 9 V line is the regime-supply ring that runs from the DC bus of block 13 back to the startup entry point in the steady state. It sustains regime losses and control requirements — it is not direct serial throughput to the load, and it does not cross Frame 0. The ring is public as an architectural principle; ratings and physical implementation of intermediate stages are closed engineering documentation. The ring does not mean “reuse of the same energy”: in the steady state energy moves through the ring, and its origin is a Frame 0 question.
Does the Frame 0 accounting identity claim a violation of energy conservation?
No. The identity Pin,boundary = Pcustomer + Ploss,total + dEstored/dt is an accounting identity that must hold at all times; it checks the completeness of the accounting and does not name the source. The canon deliberately makes no numerical claim about Pin,boundary in the steady state ahead of independent metrology; the balance residual R will be closed against the full boundary inventory under the outcome classes A–E, with no possible outcome presumed in advance.
Are the patent description and the engineering implementation the same?
No. The patent family covers the maximum defensible architectural scope in order to protect the intellectual property. The engineering implementation is a specific realisation, protected as closed engineering documentation at TRL 5–6 under the canonical disclosure matrix. Where the patent invokes classical analytical frameworks (for example the Townsend framework), those are patent-level analytical references, not statements about the measured mechanism of the current implementation. Evaluating the patent text as a complete engineering specification produces wrong conclusions.