42-software-driven-data

$982,387.50
In stock
SKU
2071
Software-Driven Data: an array of three data cartridges and two parity cartridges loses two cartridges and rebuilds them from the others, animated picture

Asset valuation: $2,800,000,000. Master index of all projects: PROJECTSINDEX. Last edited: 2026-05-02 Status: Three custom storage / accelerator hardware designs in active development Maturity (per PACKAGEARCHITECTURE.md): L2 (Designed) — KiCad schematics, BOMs, mechanical / power / architecture do

Think of the drive in your pocket the way you think of a light switch: when it is off, it is off. Unpowered, drawing nothing, and the computer it was plugged into sees a clean disconnect. That switch is the first thing you notice about the Cri-One 2.5-inch Vault.

Software-Driven Data is three storage and accelerator hardware designs plus one software product. The Vault wraps a standard M.2 2280 NVMe drive behind a USB 3.2 Gen 2x2 bridge, moves data at about two gigabytes a second over a single USB-C cable, holds up to eight terabytes, and leans on the drive's own Opal 2.0 hardware AES-256 for encryption; its four-layer board has a JLCPCB-ready 26-line bill of materials. Beside it sit an enterprise SATA hot-swap SSD and an FPGA-based PCIe card that carries compute and storage on one board. Above all three runs Software for Data, a pure-Python reference implementation that manages, encrypts, tags and recalls data, with 40 unit tests and seven demos passing. The whole thing is anchored on a 2017 entry in the inventor's register asking for business software that could be packaged and resold.

This is for the engineering buyer who wants the schematics, bills of materials, mechanical drawings and architecture notes already on file - 106 files, six KiCad project files, two measured DXF outlines, three BOMs, two datasheets. The buyer walks away with the designed package; the design is patent pending and the IP remains with Christopher Gabriel Brown.

Description

42 — Software-Driven Data: Custom Storage Hardware & Software for Data

Inventor: Christopher Gabriel Brown
SKU: 2071

Status: L2 (Designed) — KiCad schematics, BOMs, mechanical and power documentation on file; Software for Data component at L3 (Prototyped) with 40 passing unit tests and 7 passing demos

Patent notice: Patent pending. Designs originally conceived alongside the AutoPhi family may relate to umbrella application US 19/540,453 (“Integrated Technology Portfolio”). Additional filings in the inventor’s portfolio include applications 17/687,656, 63/552,008, 29/839,062, 29/892,202, 17/454,808, 17/454,807, 18/650,137, 18/460,559, 18/370,908, 18/219,732, 19/031,884, 19/177,547, and others — see the full patent portfolio for scope and coverage. All rights to seek additional patent protection are expressly reserved by the inventor.

Licence: Proprietary and Confidential — © 2026 Christopher Gabriel Brown. All rights reserved.

Source IP corpus: Buy Invent A1–A1752 (1,752 inventor-authored entries, © 2017–2019 Christopher G. Brown)

Overview

This package holds three custom storage and accelerator hardware designs plus one software product under the Cri-One brand. Each hardware design is self-contained with its own KiCad project, datasheets, mechanical drawings, and architecture notes; the software product is a working pure-Python reference implementation. Together, the four sub-projects span the entire storage stack — from a pocket-sized encrypted USB vault through an enterprise SATA hot-swap SSD and an FPGA-based PCIe compute-plus-storage card, to the application-layer software that manages, encrypts, tags, and recalls data across all of them.

The product-as-a-whole is anchored on A649 (2017): “software software please make my software software information and data management creation and business software… an easy and re-sell able application package maker and formatted.”

Package Statistics
Metric Value
Total files 106

Sub-projects 4 (cri-one-2-5-vault, cri-one-l3-ssd, cri-one-pcie-accelerator, cri-one-software-for-data)

Python source files 30 (5,330 lines)
C source files 3 (744 lines)
Documentation (Markdown) 28 files (4,839 lines)
KiCad project files 6 (.kicad_pro, .kicad_sch, .kicad_sym, .kicad_prl, .kicad_pcb)
CAD drawings (DXF) 2 (2.5″ drive outline, M.2 2280 outline)
Bills of materials (CSV) 3 (one per hardware sub-project)
Datasheets (PDF) 2 (Marvell 88SA8052, Marvell 88SF9xxx)
Unit tests 40 methods across 5 test files (726 lines)
Demo scripts 7 (673 lines)

Render specification 1 (photorealistic product-photography spec with negative prompts and generation settings)

Sub-Project 1: Cri-One 2.5″ Vault — Portable Encrypted NVMe Drive

A custom 2.5″ form-factor external NVMe SSD with a physical power switch . The enclosure wraps a standard M.2 2280 NVMe drive behind a USB 3.2 Gen 2×2 bridge, delivering approximately 2 GB/s sustained throughput over a single USB-C cable. When the slide switch is off, the drive is fully unpowered — the host sees a clean USB disconnect event, and the SSD draws exactly 0 W.

Specifications
Spec Value
Form factor 2.5″ SATA-style enclosure — 100 × 69.85 × 9.5 mm

PCB dimensions 80 × 50 mm, 4-layer, 1.6 mm thick (JLC04161H-3313 impedance-controlled stack-up)

Host interface USB-C, USB 3.2 Gen 2×2 (20 Gbps)
Storage interface M.2 2280 NVMe (PCIe ×2 via ASM2364)
Sustained read / write ~2 GB/s (USB 3.2 Gen 2×2 ceiling)
Capacity Up to 8 TB (limited by the M.2 SSD chosen by the user)
Power 5 V from USB-C, ~5 W active, 0 W when switch is off
Encryption Hardware AES-256 via the M.2 SSD’s built-in Opal 2.0
OS support Windows, macOS, Linux — appears as a generic USB mass-storage device
Bridge controller ASMedia ASM2364 (QFN-76) — USB 3.2 Gen 2×2 to NVMe, stock OTP firmware
Voltage regulator Texas Instruments TPS62823 (WSON-8) — 5 V to 3.3 V buck, 3 A capable
ESD protection TPD4S014 (D+/D−) + 2× USBLC6-2SC6 (SuperSpeed pairs)
Crystal 24 MHz, 18 pF load (Yangxing X322524MOB4SI, 3225 SMD)

Power switch C&K JS202011SCQN SPDT slide switch — cuts VBUS upstream of all downstream components

Indicators Green power LED (Kingbright KP-1608SGC, 0603) + WS2812B-Mini RGB activity LED (3535 SMD)

Polyfuse Bourns MF-MSMF050-2 — 500 mA hold, 1 A trip
Mounting 4× M3 non-plated holes on 76 × 41 mm grid
Test points 6 (VBUS, +3V3, D+, D−, PE_RST_N, GND)
Fabrication readiness JLCPCB-ready BOM with JLCPCB part numbers for every component

Estimated BOM cost (qty 5) ~$245 including PCB, assembly, M.2 SSD (Samsung 990 Pro 2 TB), and 3D-printed shell

BOM Summary (26 line items)

Reference Component Manufacturer Package
U1 ASM2364 USB–NVMe bridge ASMedia QFN-76
U2 TPS62823 buck regulator (5 V → 3.3 V) Texas Instruments WSON-8
U3 TPD4S014 USB-C ESD Texas Instruments SON-6
U4, U5 USBLC6-2SC6 SuperSpeed ESD (×2) STMicroelectronics SOT-23-6
J1 USB-C 24-pin receptacle (632723300011) Würth Elektronik SMD
J2 M.2 M-key NVMe socket Hirose SMD
SW1 SPDT slide switch (JS202011SCQN) C&K Through-hole right-angle
Y1 24 MHz crystal Yangxing Tech 3225 SMD
D1 Green power LED Kingbright 0603
D2 WS2812B-Mini RGB activity LED Worldsemi 3535 SMD
F1 500 mA polyfuse Bourns 1812 SMD
FB1 (×2) Ferrite bead 600 Ω Murata 0603
C1–C14 Decoupling & bulk capacitors (18 pF to 22 μF) Murata, Samsung 0402–1206
R1–R8 Resistors (330 Ω to 5.1 kΩ) Yageo 0402
L1 2.2 μH inductor (SRP4020TA-2R2M) Bourns SMD
TP1–TP6 Test points (×6) Keystone Through-hole
H1–H4 M3 mounting holes (×4) — Non-plated
High-Speed Signal Routing
Signal Path Impedance Trace/Space Length Match

USB SuperSpeed pairs (4 diff pairs, 10 Gbit/s per lane) 90 Ω differential 5/5 mil ≤5 mil intra-pair, ≤50 mil inter-pair

PCIe Gen 3 ×2 pairs (4 diff pairs + REFCLK) 85 Ω differential 5/9 mil ≤5 mil intra-pair, ≤100 mil inter-pair

USB 2.0 D+/D− 90 Ω differential 5/5 mil ≤20 mil
PCIe REFCLK (100 MHz) 85 Ω differential 5/9 mil ≤5 mil (most sensitive net)
Design Files Included
File Purpose

cri-one-2-5-vault.kicad_pro / .kicad_sch / .kicad_sym / .kicad_prl KiCad 9/10 project with symbols and schematic

bom.csv JLCPCB PCBA-format bill of materials (26 line items)
notes/schematic.md Block diagram, power flow, net summary (164 lines)
notes/netlist.md Pin-by-pin connection list for every component (236 lines)

notes/layout-guidelines.md 4-layer stack-up, impedance rules, DRC targets, placement sketch (219 lines)

notes/mechanical.md 2.5″ enclosure dimensions, 3D-print specs, assembly procedure (136 lines)

notes/2-5-drive-outline.dxf Measured DXF outline — 100.5 × 69.85 mm
notes/m2-2280-outline.dxf Measured DXF outline — 22.0 × 80.0 mm
notes/pcb-outline-template.kicad_pcb KiCad PCB outline template

_gen_schematic.py / _fix_footprints.py Schematic generator and footprint correction scripts (694 lines combined)

Sub-Project 2: Cri-One L3 SSD — Custom 2.5″ SATA Hot-Swap Drive

A from-scratch custom 2.5″ SATA SSD designed to slot into HPE ProLiant Smart Carrier sleds via the standard SAS/SATA backplane. The architecture uses a hardware SATA-to-managed-NAND bridge chip — no FPGA, no firmware to write , no Phison or SMI partnership required. The flash translation layer, wear levelling, ECC, and bad-block management are all handled inside the eMMC chip’s built-in controller; the bridge chip provides fixed-function SATA protocol translation via mask-ROM firmware.

Specifications
Spec Value
Form factor 2.5″ SFF (SFF-8201) — 100.45 × 69.85 × 7.00 mm (preferred) or 9.50 mm
Mass

Connector SATA 22-pin edge (15-pin power + 7-pin data), gold-finger pads on PCB (ENIG finish, 30° chamfer)

Data interface SATA III differential pairs — 100 Ω impedance, ≤5 mil length matching

Storage medium Managed NAND (eMMC) — Kingston EMMC256G-W729-T01U, 256 GB, BGA-153 (11.5 × 13 mm)

Bridge chip Marvell 88SA8052 (sourcing in progress; JMicron JMB389/390 as documented fallback)

Performance ceiling 100–300 MB/s (bridge-chip and eMMC speed dependent)
Power rails from backplane +5 V (primary) and +3.3 V; +12 V unused
Estimated total draw 500–800 mA peak
Voltage regulators 2× TPS62823 bucks (5 V → 3.3 V at 1 A; 5 V → 1.8 V at 0.5 A)
Power supervision TPS3823-33 reset generator (or simple 47 kΩ × 100 nF RC delay)
HPE compatibility Smart Carrier Gen8, Gen9, Gen10, Gen10+, Gen11 (SATA variant)

Design state v0 design exploration — architecture, mechanical, power, tentative BOM on file; blocked on bridge-chip datasheet

Estimated timeline 3–6 months from chip arrival to drive working in HPE server
Tentative BOM (23 line items)

Includes bridge chip (Marvell 88SA8052, sourcing), 256 GB eMMC (Kingston BGA-153), 2× buck regulators (TPS62823), LDO for 1.8 V VCCQ (TPS73218), power supervisor (TPS3823-33), optional Smart Carrier EEPROM (DS24B33), activity LED, decoupling capacitors (100 nF × 8, 10 μF × 4, 22 μF × 2, 100 μF tantalum × 2), pull-up resistors, inductors, and optional crystal. Custom JLCPCB PCB with ENIG gold-finger SATA edge, plus 3D-printed or modified stock 2.5″ enclosure and HPE Smart Carrier sled.

Fallback Strategy
Pivot Plan Approach Datasheet

Plan A — Alternative bridge chip JMicron JMB389 (CF/SD-to-SATA) or JMB390 (SD-to-SATA) Public

Plan B — MCU-based SATA target STM32H743ZIT6 (Cortex-M7 480 MHz with SATA controller) + eMMC via SDIO Public, full ecosystem

Plan C — Drop to L2 build M.2-SATA-to-2.5″-SATA carrier (2-weekend project) N/A

Design Files Included
File Purpose
architecture.md Block diagram, functional partitioning, risk register (126 lines)

mechanical.md SFF-8201 dimensions, SATA connector pinout, HPE Smart Carrier compatibility matrix, mounting holes (153 lines)

power.md Power tree, buck regulator selection, hot-plug staggered-ground sequence, power-good supervision (120 lines)

bom-tentative.csv 23-line-item tentative BOM with status flags
datasheet-hunt.md 8-step search strategy for the Marvell 88SA8052 datasheet (108 lines)
fallback.md Three pivot plans with decision-point checkpoints (121 lines)
Sub-Project 3: Cri-One PCIe Accelerator + Storage Card

A custom HHHL (Half-Height Half-Length) PCIe card that is both a compute accelerator and a 1 TB persistent storage device. Eight RISC-V soft cores, 1 GB DDR3 working memory, 1 TB on-board eMMC, a Lattice ECP5-85F FPGA, and PCIe Gen 2 ×4 host connectivity — all on a single-slot, low-profile card with no auxiliary power connector. Built entirely on an open FPGA toolchain (Yosys + nextpnr + Project Trellis). Spiritual successor to the Intel Xeon Phi 3120A, but with on-board SSD inside.

Specifications
Spec Value
Form factor HHHL — 167.65 × 68.90 mm, single-slot, low-profile bracket

PCIe edge connector x16 mechanical (89 mm, 164 pins), x4 electrical (32 pins wired), ENIG + 30° chamfer, 1.6 mm PCB

FPGA Lattice ECP5-85F (LFE5UM5G-85F-8BG381C) — 84K LUTs, 3.7 Mbit BRAM, 4× 5G SerDes, 381-pin caBGA (17 × 17 mm)

Soft CPUs 8× VexRiscv RV32IM @ 100–150 MHz, 5-stage pipeline, ~1,500 LUTs/core, 4 KB I-cache + 4 KB D-cache each

Working memory 1 GB DDR3-1600 (Micron MT41K512M16HA-125:E, FBGA-96, 16-bit interface, 12.8 GB/s peak)

Persistent storage 4× 256 GB eMMC (Kingston EMMC256G-W729-T01U, BGA-153) = 1 TB total
Storage throughput ~400 MB/s per eMMC × 4 = ~1.6 GB/s aggregate
Host I/O ceiling PCIe Gen 2 ×4 = ~2 GB/s sustained
Peak compute (FP32, software FPU) ~10 GFLOPS
Peak compute (with HW FPU) ~50–100 GFLOPS
Power 15–25 W total (well within PCIe slot’s 25 W budget; no aux 6-pin needed)
DMA round-trip latency ~5–20 μs
Cooling 40 × 40 × 10 mm aluminium heatsink + Noctua NF-A4x10 5 V PWM fan (~17 dBA)
Bitstream source SPI flash (Winbond W25Q128JVSIQ, 128 Mbit, SOIC-8) — FPGA boots in ~1 s
SoC framework LiteX (enjoy-digital) with LiteDRAM, LitePCIe, LiteSDCard
Toolchain Yosys (synthesis) + nextpnr-ecp5 (place & route) + Project Trellis (bitstream)
Estimated BOM cost ~$600–$750 for first working card (including dev board)
Three Roles, One Card
Role Description

Compute accelerator Host writes RISC-V code + input data to BAR2/BAR4; 8 cores execute in parallel using DDR3; host reads results via DMA. Use cases: matrix math, crypto, signal processing, custom kernels.

1 TB block storage Host accesses 1 TB of eMMC as a standard block device via PCIe. Exposed as raw blocks; host chooses the filesystem (ext4, XFS, ZFS, BTRFS).

Computational storage Card reads eMMC, RISC-V cores filter/process on-card, only results sent to host. A 100 MB log scan moves 100 MB internally but returns only the 5 KB of matches.

Memory Map (Host-Visible via PCIe BARs)
Region Size Purpose

BAR0 64 KB LiteX MMIO — register file, DMA descriptors, eMMC controller regs, RISC-V reset/run controls

BAR2 256 KB RISC-V instruction RAM windows (32 KB per core × 8)
BAR4 1 GB DDR3 working memory (DMA target / shared compute buffer)
Power Budget
Block Voltage Current Power
ECP5-85F core 1.1 V ~600 mA ~0.7 W
ECP5-85F I/O + aux 2.5 V / 3.3 V ~400 mA ~1.3 W
8× VexRiscv switching (in ECP5) — ~3 W
PCIe SerDes (×4 lanes) 1.2 V ~250 mA ~0.3 W
DDR3 1 GB chip 1.5 V ~1.5 A peak ~2.3 W
4× eMMC chips active 3.3 V VCC + 1.8 V VCCQ ~150 mA each ~2 W combined
SPI flash, LEDs, fan 5 V / 3.3 V ~150 mA ~0.7 W
Buck regulator losses (~10%) — — ~1 W
Total worst-case — — ~11–12 W
Clock Domains
Clock Frequency Used By
clk_pcie 100 MHz PCIe hardcore + SerDes
clk_sys 100 MHz LiteX interconnect, RISC-V cores
clk_dram 200 MHz DDR3 controller logic
clk_dram_io 800 MHz DDR3 DLL/IO
clk_emmc 200 MHz eMMC controllers (HS400 reference)
clk_ledstrip ~1 MHz WS2812B serial timing
Tentative BOM (36 line items, ~$120 excluding dev board)

Key components: Lattice ECP5-85F FPGA ($45), Micron DDR3 1 GB ($8), 4× Kingston 256 GB eMMC ($60 total), Winbond 128 Mbit SPI flash ($1.50), 5× buck regulators (TPS54620, TPS62085 ×2, TPS62823, TPS73218), TPS3823 power supervisor, TPS24700 hot-swap controller, SY58608 clock buffer, 4× WS2812B-Mini activity LEDs, Noctua NF-A4x10 fan ($15), low-profile PCI bracket ($3), 80× decoupling capacitors, 30× bulk capacitors, and JLCPCB 6-layer impedance-controlled PCB with ENIG finish and gold-finger chamfer.

Design Files Included
File Purpose Lines

architecture.md Full block diagram, memory map, data paths, storage architecture, clock domains, boot sequence 225

mechanical.md HHHL dimensions, PCIe edge-connector spec, bracket, internal layout, heatsink/fan, server compatibility matrix 172

bom-tentative.csv 36-line-item BOM with costs and status flags 36

QUICKSTART.md 10-phase bring-up guide from toolchain install to custom HDL accelerators 241

cri_one_accelerator.py LiteX SoC target — CRG, custom HDL slot, 8-core VexRiscv, DDR3, PCIe, eMMC, WS2812B LEDs, fan PWM 359

cri_one_platform.py Pin-assignment stub for custom HHHL board 520

firmware/hello.c RISC-V “hello world” — UART driver, DDR3 memory test, custom-accelerator loopback, LED blink 164

firmware/matmul_kernel.c Matrix-multiply compute kernel for RISC-V cores —

host-driver/cri_one_driver.c Linux PCIe kernel module skeleton — probe, BAR mapping, /dev/cri_one0 chardev, ioctl for firmware load / core start-stop, mmap for DDR3 319

host-driver/cri_one_user.py Python userspace tool for the host driver —
notes/litex-setup.md 8-step LiteX + Yosys + nextpnr + Project Trellis install guide 259

notes/risc-v-cores.md VexRiscv vs Rocket vs BOOM vs CV32A6 vs NEORV32 vs PicoRV32 comparison 182

notes/ddr3-routing.md DDR3 fly-by layout rules (future) —
notes/emmc-routing.md eMMC layout rules and pull-ups (future) —
notes/pcie-bringup.md PCIe enumeration and driver bring-up (future) —
RISC-V Soft-Core Comparison (included in notes)
Core LUTs/core 8 Cores Fit ECP5-85F? Linux? Role
VexRiscv (selected) 1,500 Yes (15% of fabric) With SMP variant v1 default
VexRiscv-SMP 2,500 Yes (25%) Yes v2 candidate (1 SMP + 7 plain)
CV32A6 5,000 Tight (48%) Yes Smaller FPGAs
Rocket 7,000 No (67%) Yes Bigger FPGAs
BOOM 25,000 No Yes Server-class only
NEORV32 1,000 Yes (10%) No Many-core, low-perf
PicoRV32 750 Yes No Too minimal for compute
HPE Server Compatibility

HPE Server Slots Compatible?

ProLiant DL360 Gen10/11 1× HHHL x16 Yes
ProLiant DL380 Gen10/11 3× HHHL or FHHL Yes
ProLiant ML series Varies Yes
ProLiant DL325/DL345 2× HHHL x16 Yes
Microserver Gen10+ 1× x16 Yes (low-profile)
Sub-Project 4: Cri-One Software for Data — v1.0.0

A working reference implementation of Cri-One Software for Data — pure Python, standard library only, no external dependencies for the core runtime. Software for data that does not lose what it stores, that lets people and AI work on the same scenarios at the same time, and that can be packaged, shipped, and resold as a unit. The software component is at L3 (Prototyped) with 40 passing unit tests across 5 test files and 7 passing demo scripts.

Core Capabilities
Capability Module Corpus Anchor

Scenario-level redundancy (not byte-level) erasure.py A1647–A1650 (“quantum RAID processing / memory / service / scale”)

Silent-corruption detection (end-to-end Merkle tree) cartridge.py A1059, A246, A170, A1515, A1556

Double-failure rebuild array.py A222, A234, A246, A260, A1229, A1672

Human + AI write tagging without silent loss conflict.py, mciau.py A1229 (“MCIAU… instructional software that tells the AI what to do”)

Hot add / subtract cartridges live array.py A246 (“raid multi sd flash card device… addition and subtract able”)

Format-doubling encryption envelope envelope.py A376 (“format doubling… encrypted then translated”)

License envelope with kill-switch license.py A1239–A1243 (“data code kill switch agreement”)

Recall at hardware speed (RAG primitive) recall.py A385–A390, A1437–A1440
Buy Invent corpus integration corpus.py A1–A1752 (corpus boundary)

Real Claude AI agent in the co-work loop agents/anthropic_agent.py, agents/orchestrator.py A1229

Real embeddings via Voyage AI agents/voyage_embedder.py —
CSV-styled manifest manifest.py A41 (“everyone is csv. styled now”)
Cartridge File Format (.sfd)
Offset Size Field
0x000 9 bytes Magic: CRIONESFD
0x009 2 bytes Format version (uint16) — 0x0001
0x00B 16 bytes Cartridge UUID
0x01B 8 bytes Scenario count (uint64)
0x023 32 bytes Master key salt
0x043 32 bytes License envelope hash (SHA-256)
0x063 32 bytes Merkle root over all scenarios (SHA-256)

0x083–0x0B3 48 bytes Section offsets and lengths (manifest, scenario block, license envelope)

0x0B3 13 bytes Reserved
0x0C0… Variable Manifest + scenario blocks + license envelope
Footer 32 bytes HMAC-SHA256 of header, keyed by master key
Encryption Envelope (Two-Layer, A376)
Layer Scope Key Derivation Integrity

Inner (per-scenario) Each scenario payload + embedding K_scen = SHAKE256(master_key || cartridge_uuid || scenario_uuid, 32) HMAC-SHA256(K_scen, plaintext)

Outer (per-cartridge) CSV-styled manifest K_manifest = SHAKE256(master_key || cartridge_uuid || “manifest”, 32) Footer HMAC keyed by K_manifest

Conflict Resolution Policy (Human + AI, A1229)

Incoming Existing Resolution
HUMAN HUMAN Raise ConflictError — explicit merge ceremony required
HUMAN AI HUMAN wins; AI write archived as “proposal”
HUMAN JOINT HUMAN wins; JOINT write archived as “proposal”
AI HUMAN AI write archived as “proposal”; HUMAN unchanged
AI AI Fork into two scenarios; merge requires explicit ceremony
AI JOINT AI write archived as “proposal”
JOINT * Treat as HUMAN priority

Critical invariant: No conflicting write is silently dropped. Every conflict results in either an explicit merge or a preserved fork.

Collaborative RAID Array Protocol

An array of M cartridges: K data shards + (M−K) parity shards. Two-parity scheme: P0 = XOR of all data shards; P1 = XOR of cyclically-shifted data shards. Tolerates loss of any 2 cartridges without scenario loss (RAID-6 in spirit but operating on scenario chunks rather than disk blocks). Fixed 4 KiB chunk size, single-byte cyclic shift for P1 in the reference implementation.

Software Source Tree
Directory / File Purpose Lines
src/sfd/__init__.py Package init, public API exports, version 1.0.0 41
src/sfd/manifest.py Scenario manifest schema (A41 CSV-styled) —
src/sfd/envelope.py Format-doubling encryption envelope (A376) —
src/sfd/cartridge.py Cartridge writer / reader with Merkle tree (A1059, A246) —
src/sfd/erasure.py Scenario-level erasure coding (A1647–A1650) —
src/sfd/array.py Collaborative RAID array (A222, A234, A1229) —
src/sfd/conflict.py Human / AI write tagging and conflict policy (A1229) —
src/sfd/mciau.py MCIAU AI instruction channel (A1229 verbatim) —
src/sfd/license.py License envelope with kill-switch (A1239–A1243) —
src/sfd/recall.py RAG primitive — cosine similarity recall engine (A385–A390) —
src/sfd/corpus.py Buy Invent A1–A1752 corpus loader —
src/sfd/cli.py Command-line tool (build-cartridge, inspect, recall) —
Total src/sfd/ source 2,358 lines

tests/ (5 files, 40 test methods) test_core, test_array, test_conflict, test_recall, test_agent 726

demos/ (7 scripts) Build cartridge, build array, silent corruption, double-failure rebuild, human/AI conflict, hot add, real AI agent 673

Requirements and Dependencies
Requirement Value
Python ≥3.10
Core dependencies None — Python standard library only
Optional [agents] anthropic ≥0.40.0, pydantic ≥2.0
Optional [embeddings] voyageai ≥0.3.0
Build system setuptools ≥61.0
Console script sfd (installed via pip install -e . )
Licence Posture (Commercial Source Licence)

What the buyer gets: The complete cri-one-software-for-data/ source tree — perpetual, irrevocable, worldwide, non-exclusive, royalty-free, sublicensable licence to run, modify, fork, redistribute, and incorporate into commercial offerings. The buyer owns every modification and derivative work.

What the licensor retains: (1) The Buy Invent A1–A1752 corpus (© 2017–2019 Christopher G. Brown) — referenced for provenance only via A-number citations, not part of the distribution. (2) Any patent that may issue from the method-claim filing (possible umbrella coverage under US 19/540,453). (3) The “Cri-One” and “Buy Invent” trademarks. A non-assertion covenant covers the buyer’s use of the source code as delivered.

What ships in lieu of the corpus: sample_corpus.txt — 25 synthetic entries in the same format so demos and tests run out of the box.

Additional Package Contents
File Purpose

README.md Master index with sub-project table, maturity notes, patent status, quick navigation

PLAYBOOK.md Internal playbook — identity, hook lines, reply patterns, status and gaps

MANIFEST.json Machine-readable package manifest (name, title, inventor, maturity, file categories)

CHANGELOG.md Keep-a-Changelog-format change log
CITATION.cff Citation File Format metadata (CFF v1.2.0)
LICENSE Proprietary licence with patent notice
CONTACT_INFO.txt Inventor contact details

RENDER_SPECIFICATION.md Photorealistic render spec — 3 camera views, generation settings (1344 × 896, DPM++ 2M Karras, CFG 5.0), negative prompt

google_patents_search_list.txt 215 USPTO application references across the inventor’s full patent portfolio

1 light trigger.txt Buy Invent A1–A1752 corpus (1,752 entries, © 2017–2019)
Yesterday.txt AutoPhi portfolio overview and technology summary
Contact Information.txt Contact details
cri-one-software-for-data.zip Compressed archive of the Software for Data sub-project

sales-pitches/businesscartridge26_STORE_PRODUCT_DESCRIPTION.html Existing storefront listing for the Software for Data component

sales-pitches/businesscartridge26_PRODUCT_CARD.md Product card summary

datasheets/ (2 PDFs) Marvell 88SA8052 product brief (2015-09), Marvell 88SF9xxx product brief (2011-04)

What Is in the Package
The complete deliverable comprises 106 files across 4 sub-projects:
  • cri-one-2-5-vault/ — KiCad 9/10 project (6 KiCad files), JLCPCB-ready BOM (26 components), 2 DXF mechanical drawings, schematic block diagram, pin-level netlist, layout guidelines with impedance rules, mechanical spec with 3D-print dimensions, and 2 Python generator scripts (694 lines)
  • cri-one-l3-ssd/ — Architecture block diagram, SFF-8201 mechanical spec, power tree with hot-plug analysis, tentative BOM (23 components), datasheet-hunt strategy, and three-tier fallback plan
  • cri-one-pcie-accelerator/ — LiteX SoC target in Python (359 lines), platform stub (520 lines), RISC-V firmware in C (164 lines), Linux PCIe kernel-module skeleton in C (319 lines), Python userspace tool, 6-core comparison study, LiteX setup guide, 36-component BOM, and 10-phase quickstart
  • cri-one-software-for-data/ — 12 Python modules (2,358 lines), 5 test files with 40 unit tests (726 lines), 7 demo scripts (673 lines), architecture specification with binary format and protocol definitions, commercial source licence, pyproject.toml packaging, and sample corpus

Total source code: 5,330 lines of Python + 744 lines of C . Total documentation: 4,839 lines of Markdown across 28 files.

How this is delivered

This package ships on a single Blu-ray disc, posted to the delivery address on your order. The archive on the disc is AES-256 encrypted; the passphrase is sent separately, by email, once the disc is despatched — so the disc alone is of no use to anyone who intercepts it.

Discs are despatched by tracked, signed-for post. Allow 5 business days for mastering and verification before despatch.

© 2026 Christopher Gabriel Brown. All rights reserved. “Cri-One,” “Cri-One Software for Data,” “Cri-One Collaborative RAID,” “Cri-One Business Cartridge,” and “Buy Invent” are product designations of the inventor. Patent pending.

Photo

Desktop monitor in a server room showing a 'Chemical Arrangements Database' app (molecules, DNA, compound table)

Footnotes

  1. Product number 8490.
  2. Family: storage.
  3. Purchase: When you buy, you buy the use of that blueprint only.
Write Your Own Review
You're reviewing:42-software-driven-data
© 2026 Christopher Gabriel Brown (CRI-ONE), cri-one.com