← Blog Raise catalog Team Product / The file door

NeoDrive

Ask for the contract. Get the one you signed.

Ask for the contract. Get the one you signed.

The original file

NeoDrive is the file door on the same archive the Memory install already runs. Write the object once — the executed agreement, the design that shipped, the module that compiled, the decision that killed a feature, and the reason it was kept. Ask later. Receive that object. Fuzzy folder search ranks a near-match; NeoDrive returns the file that was written.

A general counsel does not want a draft that looks like last quarter’s deal. A product lead does not want a slide that drifted from the kill decision. The get is the stored item: bytes, name, and the binding that says why it stayed. NeoDrive stores those as resonant patterns — phase and amplitude in one field — so the later ask is a key, not a keyword. The model on top can still draft. The model is not the filing system.

That is the product to want. A company memory that can hand the signed page back to the person who asked for it. Contracts, designs, code, decisions, and the communications that explain them live as one store. Counsel asks for the agreement that closed. NeoDrive answers with that agreement.

Ask for the contract. Get the one you signed — the stored object, not a cousin that sounds like it.

A geometry address

Every file sits at a lattice place. The address is an outer root, then a finer cell, then a nested inner copy — decoded at each level without walking an estate tree. The house already addresses the archive on 240 E8 roots. NeoDrive uses that same geometry for the file: a coordinate you can resolve. Grow the estate and the decode stays a decode. The get does not become a hunt just because more objects were written.

The hot path stays in the frequency domain. Bind by multiplying. A key and a value become one object in the field. Later recall conjugates the probe and the stored component answers. There is no slot allocation that evicts the neighbor. A new write adds a coherent component. Multiple files coexist by superposition. φ-scaled nesting keeps the inner copy inside the parent cell so two holograms do not fight for the same band.

  • Lattice place — outer root, inner cell, nested copy. Geometry is the address.
  • Bind — multiply into the field. The write adds. The neighbor stays.
  • Recall — conjugate the probe. The stored component answers.

Seven rooms share that grammar — security, agents, build, identity, infra, creative, meta — so a contract, a design, and a decision can live in one palace. Each room uses the same bind and the same conjugate probe. The file does not change species when it changes aisle. The address is still a place.

Retrieval is reconstruction

Optical phase conjugation plays the stored pattern backward. The phases reverse. The distorted path unwinds. The original state reconstructs. If you know the path forward, you can find the path back. The read path probes with a time-reversed key, cleans against a threshold, and refreshes the pattern on the way out.

That is why the signed agreement comes back as the signed agreement. The get is a reconstruction of the wave that was written. Counsel asks. The field answers with the object that was stored. A decade later the same key still reconstructs the same file. The pattern is refreshed by the read. There is no silent rewrite of the contract while a confident filename still lists it.

Retrieval is reconstruction of the wave that was written.

Thresholding is part of the get. A thin probe does not mint a polite cousin to keep the conversation moving. Below the gate the archive says it does not have that object. Silence is how the signed page stays the signed page. Reconstruction is the feature. Refusal is the honesty that protects it.

Light that holds the file

Information lives as resonant patterns of light, addressable by geometry and retrieved by playing the stored pattern backward. The palace is not a metaphor parked on a disk. The building is a frequency spectrum. Rooms are spectral bands. Shelves are subbands. A write adds a coherent component. The neighbor stays. Density comes from superposition and nesting — hologram inside hologram — because the field can hold more than one object in the same place.

Phase and amplitude are the record. Photons keep phase where charge leaks. That is why NeoDrive is designed as a photonic memory palace rather than a smaller cell on the same medium. Photonic capacity is a research path. The file door you can want is the get that is already specified: original object, geometric address, reconstruction on the way out.

The same FHRR grammar the Memory install already uses — bind, conjugate, clean — is the grammar of the file. NeoDrive is the storage face of that archive, not a second vault beside it. Write the file into the field. Keep the key. Ask with the key. Receive the reconstruction.

On the buyer’s hardware

The files live on the buyer’s hardware — in the building, or in the VPC the CIO already owns. When the relationship ends, the archive stays. That is ownership with an exact get: the company keeps the store, and the store keeps the original. A later change is visible. The fingerprint of the signed page is the fingerprint counsel can show. A model upgrade does not move the address of the file.

Write it on their rack. Ask from their desk. Get the object that was stored. The commercial motion is still NDA, a proof on their floor, and an archive they own. NeoDrive inherits that install. Research on denser addressing and photonic media continues. The door is get-the-original-back storage on infrastructure the customer already runs.

A contract that ends does not take last year’s bindings with it. A vendor swap does not rename the signed page. The language model on top can still write prose. The model is not the filing system. The filing system is NeoDrive — the original file, at a geometry address, reconstructed on hardware the buyer already pays to keep.

What the buyer is looking at

Read this page for the product we are designing toward: original-file retrieval, a geometry address, reconstruction of the stored wave, on hardware the buyer already runs.

NeoDrive is a research door on the catalog — never a SKU on the public raise. Isolated recall on a quiet machine is 13.834 µs. Under load we have also seen 5,127 µs. Those are memory clocks, shown together. They are not a NeoDrive service-level agreement. Photonic capacity stays off the commercial card. Twenty million dollars is an ask to land the archive first. This door inherits that install.

Sources: Trinity Sky, Quantum NeoDrive (docs/whitepaper-neodrive/chapters/). Book §7.4. Original-file retrieval, lattice addressing, OPC reconstruction, and buyer-hardware custody are paper features. Isolated 13.834 µs and loaded 5,127 µs shown together as memory clocks, not a NeoDrive SLA. Photonic capacity stays in diligence. $20 million is an ask.

$20 million is an ask. No customer logos yet. Forecasts are a plan. Full papers are diligence.