How it works

SpinVault is a proposed magnetically guided tunnel-barrier storage concept. The goal is to reduce uncontrolled electron transmission through an ultra-thin barrier and preserve a clearer, more secure storage state.

STATEStored bit as a physical configuration

The website frames data as a state that must remain distinguishable despite thermal noise, process variation, and tunneling leakage.

BARRIERTiN / Al2O3-compatible tunnel membrane

The deck references proven materials and process compatibility. The technical model uses a barrier-height and barrier-width approximation instead of unexplained black-box scores.

CONTROLMagnetic stabilization layer

Magnetic influence is modeled as a stabilizing term that improves spin selectivity and reduces effective leakage exposure.

Reference barrier height3.0 eV
Reference barrier width3.0 nm
Reference electron energy0.5 eV
Core modelWKB tunneling + TMR

Traditional NAND vs SpinVault

Toggle between Traditional NAND and SpinVault to explore how the same physical inputs can produce very different leakage and retention behavior across the small simulations below.

ModeTraditional NAND
Leak36%
Retention52%

Fundamentals first

The technical foundation combines quantum tunneling through a thin insulating barrier with magnetic-tunnel-junction readout theory.

Stored state
01Electrons occupy a state

Data is represented by a physical condition that must remain distinguishable over time.

02A barrier separates states

The tunnel region controls how easily carriers move between stable and unstable configurations.

03A magnetic field biases behavior

Field influence is modeled as a control term that reduces random drift and path variance.

04Noise creates leakage pressure

Temperature, process variation, and disturbance push the system toward weaker retention.

The central technical question

Can a magnetically guided tunnel membrane produce a larger practical margin between intentional read/write behavior and unwanted leakage? A credible answer requires formulas, assumptions, and failure boundaries, not only a visual demo.

Why tunneling matters

At nanometer scale, electron transmission becomes probabilistic. In the low-bias rectangular-barrier approximation, transmission follows an exponential term, so small changes in barrier width or energy height can create massive changes in leakage.

Why magnetic control matters

Magnetic tunnel junctions use spin-dependent tunneling. Parallel and antiparallel magnetic states can produce different resistance values, which is why TMR theory is relevant for a SpinVault-style storage and readout architecture.

Equations used

The simulator uses the same transmission-summary variables shown in the deck, then expands them with standard quantum tunneling and spintronics formulas from published literature.

Finite barrier transmission

T(E) = [1 + V₀² sinh²(κd) / 4E(V₀ − E)]⁻¹

Used for the live electron-wave cell when E is below the barrier.

TMR readout contrast

TMR = 2p₁p₂ / (1 − p₁p₂)

Julliere's model links spin polarization in two magnetic electrodes to magnetoresistive readout contrast.

Thermal stability

Δ = Eᵣₑₜₑₙₜᵢₒₙ / kBT

Retention is modeled through an energy barrier relative to thermal energy. Higher Delta means a state is less likely to thermally flip or drift.

WKB intuition

T ≈ exp[−2d√(2m(V₀ − E)) / ℏ]

The WKB form explains why the design is sensitive: nanometer-level changes in barrier width can shift transmission by orders of magnitude.

Technical theory

The core concept is to treat memory retention as a controllable physical state, not only as a circuit-level error-correction problem.

Controlled tunnel region

Field alignment, barrier geometry, and material behavior are modeled together.

01 · Boundary

Magnetized tunnel membrane

The membrane is framed as the physical boundary where electron movement becomes intentionally constrained. Instead of assuming leakage is just a downstream security issue, SpinVault starts at the material interface where leakage behavior begins.

02 · Control

Electron-flow guidance

The simulation should explore how magnetic field strength and tunnel-barrier assumptions affect the probability of electrons moving through, remaining stable, or drifting under stress.

03 · Reliability

Retention as a state-quality problem

Instead of presenting storage as only binary on/off behavior, SpinVault measures state quality: stability, leakage pressure, noise exposure, and expected attack surface.

04 · Security

Physics-assisted protection

The security thesis is that a more controlled physical layer can reduce the usefulness of leakage-based attacks before software protections even begin.

Conceptual model

The model is built around variables that an advisor can challenge: barrier height, electron energy, barrier width, spin polarization, temperature, and disorder.

Magnetic control

p₁, p₂ ↑ ⇒ TMR ↑

Better spin polarization improves readout contrast in the Julliere approximation, but the page avoids claiming infinite protection because real interfaces, disorder, and temperature reduce performance.

Barrier behavior

d ↑ ⇒ T(d) ↓ exponentially

Tunneling probability is exponentially sensitive to barrier width. That makes barrier engineering powerful, but it also means fabrication variation matters a lot.

Noise response

kBT ↑ ⇒ Δ = Eb / kBT ↓

Higher temperature raises thermal energy and weakens the retention margin. The simulator now exposes this instead of hiding it inside a generic noise slider.

Storage quality

Mᵤₛₐᵦₗₑ ≈ Mᵣₑₜ + Cᵣ − Lₗₑₐₖ

The output is a concept-level engineering metric that combines the WKB transmission estimate, thermal stability, and TMR readout contrast.

Realistic one-cell architecture

SpinVault should be presented as a magnetic tunnel junction style research cell, not as a generic “electron box.” The useful simplified cell is a pinned ferromagnetic reference layer, an ultra-thin insulating tunnel barrier, and a free magnetic layer whose state is read through resistance contrast.

top contact / bit line
Pinned FM referencefixed magnetization m1
MgO or Al2O3 tunnel barrier1-3 nm insulating quantum barrier
Free FM storage layerswitchable magnetization m2
bottom contact / select path
low R: parallelhigh R: antiparallel
Physical abstraction

What one cell represents

The web model treats the cell as a ferromagnet-insulator-ferromagnet junction. The barrier controls quantum transmission, while the relative magnetic alignment controls readout resistance through spin-dependent tunneling.

What changes in the simulator

From cartoon to model

Barrier height, electron energy, barrier thickness, temperature, and spin polarization are now the visible model variables. The simulation should be read as a transparent first-principles approximation, not a fabricated measurement.

Future high-fidelity path

What comes after this

A later model should add bias-dependent Simmons tunneling, interface roughness, magnetic anisotropy, and LLGS magnetization dynamics for switching behavior.

Mathematical model and sensitivity graphs

The goal is not to hide behind animations. These graphs show the relationships the simulator is using: exponential barrier sensitivity, TMR contrast, thermal stability, and the future LLGS switching model.

Transmission vs barrier widthlog scale
Tbarrier width dT ≈ exp(-2κd), κ = sqrt(2m*(V0-E))/hbar

Small changes in tunnel barrier thickness can move leakage by orders of magnitude, which is why fabrication tolerance matters.

TMR readout contrastJulliere
TMRpTMR = 2p1p2 / (1 - p1p2)

Higher polarization improves readout separation between parallel and antiparallel magnetic states, but real interfaces limit ideal performance.

Thermal stabilityretention
ΔE / TΔ = Eretention / kBT

Good retention requires the stored state energy barrier to remain large relative to thermal energy.

Future switching modelLLGS
m(t)timedm/dt = -γm×Heff + αm×dm/dt + τSTT

The current page does not solve LLGS yet. It clearly marks this as the next step for realistic switching dynamics.

Device stack

The technical story is strongest when SpinVault is described as a layered device architecture: substrate, access layer, controlled membrane, sensing logic, and validation output.

ReadoutMeasures state quality and exposes whether the modeled bit remains stable.
AccessConnects the storage region to external control and measurement logic.
MembraneMagnetically influenced tunnel region where electron behavior is constrained.
ShieldReduces uncontrolled leakage paths and frames the security boundary.
SubstrateProcess-compatible foundation for future physical prototyping.

Why layers matter

A storage concept can sound abstract unless every claim is anchored to a physical layer. This stack explains where the field is applied, where electron movement is expected to change, and where measurement would happen in a prototype.

What is being controlled

SpinVault is not claiming that electrons stop moving entirely. The aim is to reduce uncontrolled movement enough that the stored state becomes more reliable, less leaky, and easier to defend against physical side-channel exposure.

What must be proven next

The simulation should identify whether realistic magnetic and material assumptions can produce a useful stability margin. If the model only works under impossible conditions, the team should know early and adjust the architecture.

Virtual cell model

The cell is modeled as a ferromagnet / insulator / ferromagnet junction. The website shows both the physical stack and the simplified 1D quantum problem solved by the simulator.

FM1spin-polarized source
Al2O3tunnel barrier
FM2magnetic analyzer
incident ψevanescent ψtransmitted ψ

What the virtual cell solves

The interactive model treats the membrane as a one-dimensional finite potential barrier. It calculates electron transmission from V0, E, and d, then applies spin polarization and thermal stability terms to estimate readout contrast and retention margin.

What it does not claim

This is not a full ab initio material solver, NEGF device simulation, or fabricated measurement. It is a physically disciplined web model that makes the assumptions visible and testable.

Cell states

SpinVault's public model explains three useful states: aligned readout, opposing readout, and disturbed operation where leakage and thermal pressure become visible.

pinned FMm1
MgO / Al2O3barrier
free FMm2
parallel: lower resistance

Parallel magnetic state

When electrode polarization is aligned, the model predicts stronger spin-selective transmission and a lower resistance readout path.

pinned FMm1
MgO / Al2O3barrier
free FMm2
antiparallel: higher resistance

Antiparallel magnetic state

Opposing polarization reduces matching spin channels, increasing resistance and creating the readout contrast captured by the TMR term.

pinned FMm1 stable
heated barriernoise + disorder
free FMm2 perturbed
thermal agitation reduces retention margin

Disturbed / hot state

Higher temperature, disorder, or attack disturbance does not change the finite-barrier equation directly, but it reduces the practical retention margin.

Simulation

The large simulator below is the exact reference demo from the source HTML file, restyled so it sits cleanly inside the SpinVault page. It stays separate from the restored small simulations and the graph cards below.

Reference simulatorWave view, particle view, and 0/1 controls

The embedded app below is the exact simulation fromindex 2.html. It gives us the same physics-driven interaction and graphs the user asked for, while this page provides the SpinVault branding and supporting copy around it.

Mathematical representations

These graph cards present the uploaded source-model plots as SpinVault-aligned mathematical representations. They are shown separately from the simulation blocks above.

Transmission model

Transmission probability vs. electron energy

Spin-up and spin-down channels separate because their effective barrier heights differ. The y-axis is logarithmic, so small energy shifts become order-of-magnitude tunneling changes.

Wavefunction density

Electron wavefunction probability density

The shaded barrier region keeps the same mathematical structure as the source file while the canvas styling follows the dark, gridded SpinVault visual system.

Model validation

Every visual claim is checked against the math it represents. This keeps the simulator persuasive without overstating what a browser model can prove.

Quantum barrier

Is this accurate?

Yes for a simplified 1D rectangular barrier. The transmitted wave amplitude scales with sqrt(T), reflected amplitude scales with sqrt(1 - T), and the barrier region becomes evanescent when E < V0.

Spin readout

Is this accurate?

Yes as a first-order Julliere MTJ readout model. It assumes elastic spin-conserving tunneling and uniform electrode polarization, which is why the page labels it as a concept model.

Retention

Is this accurate?

Yes as an engineering indicator. Delta = Eb/kBT is a standard thermal-stability ratio, but the exact retention time requires material-specific attempt frequency and anisotropy data.

Scientific grounding

The web simulator is intentionally a reduced model. It uses reputable foundations and labels what belongs to future high-fidelity simulation.

Quantum transport

Finite barrier + WKB/Simmons intuition

The live chart solves a one-dimensional finite rectangular barrier and reports κ. The RA proxy follows the core tunneling idea that resistance grows rapidly as transmission falls. A production-grade model should add Simmons bias dependence and material-specific effective mass.

Spintronics readout

Julliere TMR approximation

The TMR readout is computed from spin polarization using the standard Julliere form. This is appropriate for first-order public explanation, while real MTJs require interface quality, spin filtering, bias, and temperature corrections.

Thermal retention

Delta = Eb / kBT

The retention score is tied to thermal stability rather than a generic “security” number. The page avoids claiming retention time because that needs magnetic anisotropy, volume, damping, and attempt-frequency data.

Future dynamics

LLGS / STT path

Switching is not fully solved in this browser model. The next credible simulation step is LLGS with spin-transfer torque, damping, anisotropy, and field terms.

Signal flow

The simulation should show the full chain from design inputs to evidence outputs, so reviewers can see exactly how a technical assumption becomes a claim.

InputField strength, barrier thickness, orientation, thermal stress, disturbance noise.
ModelElectron transition probability, drift pressure, leakage pathway estimate, state retention score.
CompareControlled membrane result versus passive reference model under identical stress conditions.
OutputStability margin, leakage reduction estimate, attack exposure score, recommended test window.
Higher field control should increase modeled stability until saturation.Leakage pressure should fall when the membrane assumptions are effective.The useful zone is where stability rises without impossible fabrication demands.

Simulation architecture

The first version should be simple enough to build, but rigorous enough to support investor, advisor, and patent conversations.

Input layer

  • Magnetic field strength and orientation as adjustable control variables.
  • Tunnel-barrier thickness and material assumptions as fabrication variables.
  • Thermal noise, process variation, and disturbance signals as stress variables.

Physics layer

  • Approximate electron movement probability across the modeled membrane.
  • Translate field and barrier changes into stability and leakage pressure estimates.
  • Track where behavior becomes unstable instead of hiding weak results.

Security layer

  • Compare passive leakage exposure against the controlled SpinVault model.
  • Show whether attack visibility decreases when the storage state is more physically constrained.
  • Separate demonstrated results from future claims so the website stays credible.

Output layer

  • Modeled stability score, leakage pressure score, and attack exposure score.
  • Parameter sweeps that reveal the strongest design window.
  • Exportable graphs for the pitch deck, patent appendix, and lab roadmap.

Future orchestration layer

The ideal SpinVault platform is not only a website with sliders. It becomes a controlled simulation system where fast approximations answer instantly, expensive physics solvers validate serious cases, and every run produces traceable evidence.

01 Client / presentation

Interactive web app

Browser interface for parameter changes, visual cell rendering, graphs, and reviewer-friendly model explanations.

Next.js or static prototype now; 3D/WebGL later
02 API gateway

Orchestration layer

Receives parameter requests, validates inputs, decides whether to run a fast surrogate or queue heavy validation, logs metadata, and returns reproducible results.

FastAPI / Python controller
real-time requestvalidation requestcheckpoint + archive
03 Fast path

AI surrogate model

Near-instant predictions for slider interaction: retention margin, leakage pressure, TMR contrast, and recommended design windows.

Physics-informed regression / neural surrogate
04 Validation path

Distributed physics compute

Runs slower but more rigorous simulations for high-value parameter sets: micromagnetic switching, tunneling transport, thermal stress, and sensitivity sweeps.

Ray cluster, CUDA engines, queue workers
05 Solver engines

Specialized physics modules

Separate model engines keep assumptions inspectable: finite-barrier transport, future Simmons/NEGF correction, LLGS switching, and experiment-calibrated retention.

MuMax3 / custom Python / future quantum route
06 Data layer

Experiment metadata database

Stores parameter sets, model version, assumptions, results, reviewer notes, and links to generated graphs.

Postgres metadata + object storage archives
07 Governance

Budget and evidence control

Prevents runaway compute, flags abnormal spend, tracks which claims have evidence, and separates public demos from validation runs.

Budget ceiling, spend alerts, reproducibility log
Built in repo

Gateway

Local FastAPI service accepts parameter snapshots, returns prediction metrics, and exposes validation-job endpoints.

orchestration/app/main.py
Built in repo

Surrogate model

The current fast path uses finite-barrier and spin-polarization equations so website sliders connect to computed values.

orchestration/app/physics.py
Built in repo

Metadata store

Simulation runs and queued jobs can be stored locally, creating the first evidence trail for later review.

orchestration/app/storage.py
Organized now

Platform folders

The codebase now separates client, gateway, surrogate, validation, storage, governance, and future quantum route.

platform/
Build now

A lightweight browser simulator plus a simple API schema for parameter logging and future solver integration.

Build next

FastAPI orchestration, stored experiment records, graph export, and a queue for high-fidelity validation jobs.

Build later

GPU-backed micromagnetic/transport solvers, surrogate training, secure pre-signed result access, and quantum-hardware experiments only if justified.

Technical assumptions

A serious technical page should make its assumptions visible. These are the assumptions SpinVault should document before anyone treats the simulation as evidence.

Material realism

The model should avoid magical materials. It should begin with plausible magnetic and insulating behavior, then clearly label anything speculative so advisors can challenge it.

Switching feasibility

Retention is only useful if the state can still be written and read. The simulation should track whether stronger control creates an unusable barrier for practical operation.

Thermal tolerance

Any future prototype will face temperature and process variation. The model should test stress scenarios instead of relying on idealized, room-temperature-only behavior.

Leakage definition

The team should define leakage consistently: physical state drift, measurable side-channel exposure, or lost data retention. Each version needs a different test.

Comparison baseline

Every strong claim needs a reference. SpinVault should compare against a passive model so improvement is measured as a delta, not just shown as an isolated animation.

Evidence standard

Early evidence can be simulation-based, but the roadmap should graduate toward expert review, repeatable plots, material consultation, and eventually lab characterization.

Simulation objectives

The model should not be a generic animation. It should answer specific technical questions that matter for proof-of-concept planning.

Electron-flow stabilityShow whether magnetic control produces reliable behavior under defined assumptions.Core
Leakage behaviorCompare expected leakage pressure against a traditional passive model.Core
Barrier sensitivityStress test thickness, field strength, and material assumptions.Model
Security implicationFrame why controlled behavior could make physical attacks less practical.Claim

Validation experiments

Each experiment below turns the idea into a testable claim. This makes the technology page more useful than a concept description alone.

1. Baseline comparison

  • Run a passive storage model and a controlled SpinVault model under the same noise conditions.
  • Measure relative stability, leakage pressure, and disturbance sensitivity.
  • Use the result to decide whether the concept deserves deeper prototype work.

2. Parameter sweep

  • Vary magnetic field strength, barrier thickness, and temperature-like stress inputs.
  • Visualize the safe operating window instead of showing only one perfect scenario.
  • Identify which variable has the strongest effect on usable storage margin.

3. Failure boundary

  • Push the model until leakage or drift becomes unacceptable.
  • Show what breaks first: field control, membrane assumptions, or noise tolerance.
  • Turn weak points into a concrete lab-testing plan.

4. Reviewer package

  • Produce charts and assumptions that advisors can inspect without needing the full codebase.
  • Separate conceptual physics, simulation assumptions, and business claims.
  • Build a technical appendix suitable for e2vc, patent conversations, and manufacturer outreach.

Problem / solution

Traditional systems leak information. SpinVault focuses on stable, controlled behavior.

Traditional model

Leaks data over time and needs energy-inefficient compensation to maintain security.

Core problems

Energy inefficiency, information leakage, and scaling bottlenecks create pressure on future memory systems.

SpinVault solution

Active electron-flow control targets secure architecture and reliable data behavior.

Validation map

Every technical claim should connect to a test, a reviewer, or a future lab milestone.

MechanismMagnetized tunnel membrane controls electron behavior.Simulation + expert review
ReliabilityReduced information leakage and stronger retention behavior.Simulation comparison
ManufacturabilityUses proven material references and process-compatible framing.Lab consultation
Commercial pathPatent, licensing, mass-producer conversations, and production planning.Advisor support

Modules

SpinVault can be presented as a stack of technical modules instead of one flat idea.

Core storage

Magnetic electron control model.

Simulation

Validation environment.

Lab testing

Physical proof-of-concept stage.

IP strategy

Patent and licensing path.

Research basis

These references shape the public-facing technical framing. The website does not claim lab validation yet; it presents a research-backed simulation roadmap.

Magnetic tunnel junctions

MTJs use two magnetic electrodes separated by an insulating tunnel barrier. Parallel and antiparallel magnetic alignment create different resistance states for readout.

Tunneling magnetoresistance

Julliere's TMR formula connects spin polarization to readout contrast. The simulator uses this as a first-order public model, not as a complete device solver.

Barrier transmission

WKB/Simmons-style tunneling models explain why barrier width and barrier height dominate leakage: transmission falls exponentially with barrier thickness.