content by LCUS
The Origin of Comma-Separated Encryption — Computing & Storage Series — 2017 Invent Deposition #41
2 min read
3 parts, 6 paragraphs
FIRST TO MARKET · Publicly documented 2017 · Invent Deposition #41
Among the 1,739 depositions in the 2017 Invent Depositions corpus, #41 is the closest match to the encrypted-storage layer of Project 50 — PCIe 8.0 NVMe SSD and Project 42 — Software-Driven Data on cri-one.com.
“comma separated encryption… another reason is to continue work on a daily basis as intended securely… everyone is csv-styled now, and excel — my microsoft is no reason to degrade the graphical keys to encryption.” — Christopher Gabriel Brown, 2017
From one line to an engineered product
The 2017 abstract argues that everyday tabular data — the CSV, the spreadsheet — deserves first-class, structurally-aware encryption rather than a bolt-on. The same principle drives the inline AES-256-XTS encryption engine in the AutoPhi SSD controller (Project 50) and the software-driven data vault line (Project 42): encryption belongs in the data path, not beside it.
The idea graduated from a one-line deposition into a patent-pending hardware engine without changing its founding claim: encryption belongs inside the data format, not bolted onto it.
Provenance
- Source: Invent Depositions (2017), ISBN-13 978-1-979767-89-7, CreateSpace
- Catalog image:
Firefly_41_comma_sep…jpg(buyinvent.com) - Live products: Project 50 (PCIe8 SSD) · Project 42 (Software-Driven Data)
Cite this
- AP — Brown, C. G. (2017). Invent Depositions, Deposition #41. CreateSpace.
- APA — Brown, C. G. (2017). Invent depositions (Deposition No. 41). CreateSpace Independent Publishing Platform.
- MLA — Brown, Christopher Gabriel. Invent Depositions, Deposition #41. CreateSpace, 2017.
© 2017 Christopher Gabriel Brown · Patent Pending · IP retained by CRI-ONE
Copy one of the formats below: