Chemical-Cooker Laboratory

Chemistry Cooker / Serum Build Platform — software-first, hardware second, recipes designed and exported to G-code without touching a single piece of hardware

Software first. G-code chemistry. Serum Build Platform with subscription + serial key. Hardware build whenever the buyer is ready.

The Chemical-Cooker Laboratory is a complete chemistry-automation platform structured as software-first: all value at acquisition is in the software stack (G-code interpreter, controller with dry-run mode, alchemy recipe loader, Serum Build Platform with subscription and serial-key validation, lite Alchemy data, web UI). The physical hardware build (BOM, assembly steps, wiring diagram, calibration, safety and compliance) is documented in blueprints/ for when the buyer is ready — but the platform produces working recipes and G-code output without any hardware required. v2 adds inline spectroscopy, GMP audit trail, CRI-ONE V20 edge compute, and a 500+ disease database.

Software Stack — What Runs Today

• G-code interpreter (software/gcode_interpreter.py) — parses Chemical Cooker G-code: motion (G0/G1), dispense (D), heat (H), oven (O), microwave positive/negative (M106/M107), stir (S), wait (W), tool (T). v2 adds N, R, V, U, I commands.
• Controller (software/cooker_controller.py) — runs G-code in dry-run mode or against hardware stubs.
• Alchemy recipe loader (software/alchemy_recipe_loader.py) — loads JSON/CSV recipes, converts to G-code (positions, volumes, heat, wait).
• Serum Build Platform (platform/) — subscription + serial-key validation, lite Alchemy data (elements, methods, probabilities), recipe builder, outputs G-code. Legal foundation in platform/LEGAL_FOUNDATION.md.
• Simple Web UI (software/simple_ui.py) — upload or paste G-code, run dry-run, port 5000.

v2 Engineering Delta — What April 2026 Added

• Inline NIR + Raman spectroscopy with closed-loop endpoint control. Documented in blueprints/INLINE_SPECTROSCOPY_V2.md.
• CV pre-flight deck validation — computer-vision verification that the deck layout matches the loaded recipe before run-start. Documented in blueprints/VISION_AND_CV_V2.md.
• Dilithium-5 signed GMP audit trail — 21 CFR Part 11-ready cryptographic audit trail for FDA-grade compliance. Documented in blueprints/GMP_AUDIT_TRAIL_V2.md.
• CRI-ONE V20 PCIe 5.0 edge compute — one accelerator seat included in the v2 price. Documented in blueprints/AUTOPHI_V20_EDGE_V2.md.
• Acoustic droplet dispenser — 1 nL dispense capability for high-precision micro-volume work.
• Inert-atmosphere chamber — for oxygen-sensitive chemistry.
• UV cure module — on-deck UV curing.
• Heating extended to 180°C (was lower in v1).
• +5 G-code commands (N, R, V, U, I) documented in docs/GCODE_DIALECT_V2.md; implemented in software/cooker_v2_commands.py.
• 500+ disease database integrated — the same database the broader portfolio uses for disease-mechanism analysis.

Two Versions Side By Side

v2 specs govern on conflict.

What's in the Package

Software (the focus):

• software/cooker_controller.py — main G-code controller (dry / hardware).
• software/gcode_interpreter.py — G-code parser.
• software/alchemy_recipe_loader.py — recipe JSON/CSV ? G-code.
• software/cooker_v2_commands.py — v2 command implementations.
• software/simple_ui.py — web UI on port 5000.
• software/sample_recipe.gcode, software/sample_alchemy_recipe.json, software/sample_alchemy_recipe.csv — sample inputs.
• software/requirements.txt — pip requirements.

Serum Build Platform (subscription tier):

• platform/app/main.py — validate key, load lite Alchemy, build recipe, write G-code.
• platform/app/config.example.json — configuration template (set serial key per subscription).
• platform/lite_alchemy/ — elements, methods_lite, probabilities_lite (lite subset of Project 07's full Alchemy data).
• platform/subscription/ — serial-key + tier validation.
• platform/LEGAL_FOUNDATION.md — patents, compliance, buyer responsibilities.

Documentation and v2 references:

• docs/GCODE_DIALECT.md + docs/GCODE_DIALECT_V2.md — complete G-code reference.
• 26+ guide and reference files including FDA_APPLICATION_GENERATOR_GUIDE.md, FDA_RESPONSE_GENERATOR_GUIDE.md, FDA_FORM_PLATFORM_GUIDE.md, ALZHEIMERS_AUTOMATED_GUIDE.md, BLURAY_AND_ASPIRIN_GUIDE.md, DISEASE_IMPORT_GUIDE.md, 300_DISEASES_IMPORTED.md, AUTOMATED_FDA_MAKER_GUIDE.md, ENHANCEMENT_ROADMAP.md, REFERENCE_SYSTEM_GUIDE.md.

Hardware build (when ready) in blueprints/:

• BUILD_LATER.md — "software first; use this when ready to build."
• DESIGN_AND_SPECS.md + DESIGN_AND_SPECS_V2.md — full design specifications.
• BOM.md, BOM.csv — bill of materials.
• ASSEMBLY_STEPS.md — assembly procedures.
• WIRING_DIAGRAM.md, CALIBRATION_AND_RUNBOOKS.md, SAFETY_AND_COMPLIANCE.md.
• v2 references: INLINE_SPECTROSCOPY_V2.md, VISION_AND_CV_V2.md, GMP_AUDIT_TRAIL_V2.md, AUTOPHI_V20_EDGE_V2.md.

How to Run It Today (Software Only, No Hardware)

1. Install: pip install -r software/requirements.txt.
2. Dry-run G-code: python software/cooker_controller.py (sample G-code if no file given).
3. Serum Build Platform: copy platform/app/config.example.json ? platform/app/config.json, set serial key, run python platform/app/main.py ? outputs platform/app/output/serum_recipe.gcode.
4. Web UI: python software/simple_ui.py ? open http://127.0.0.1:5000, paste or upload G-code, click Run.
5. Recipe ? G-code without subscription: python software/alchemy_recipe_loader.py with a JSON or CSV recipe.

Relationship to Other Portfolio Projects

• Project 07 — Alchemy Probability Data. The full Alchemy element / method / probability database. The Chemical Cooker bundles the lite subset under platform/lite_alchemy/; full Alchemy is acquired separately.
• v2 CRI-ONE V20 PCIe 5.0 edge compute ties into the broader CRI-ONE compute family (Project 35 CRI-ONE Quantum PCIe 5.0); the v2 price includes one accelerator seat.
• 500+ disease database shared with the portfolio's broader disease-mechanism analyses (Projects 10 / 11 / 12 / 13 and the 300-disease research database).
• Project 17 — Small Microwave Nuclear Recycler is listed as a related sibling per the inventor's project metadata (different domain, similar scale-down architecture pattern).

How it's made

Chemical-Cooker Laboratory is the productisation of an integrated chemistry-automation platform built around a custom G-code dialect for chemistry rather than CNC. The G-code controller, parser, and recipe loader are written in Python; the Serum Build Platform adds subscription / serial-key validation, lite Alchemy data, and a recipe-builder app; the simple web UI provides browser-based dry-run access. The package's structure is explicitly software-first: all the value at first acquisition is in software/ and platform/; the hardware build documentation in blueprints/ is for when the buyer is ready to commit to a physical cooker.

v2 (April 2026) is a substantial engineering delta over v1 (February 2026). The closed-loop spectroscopy and CV pre-flight deck validation move the platform from open-loop dispensing to verified-and-monitored dispensing; the Dilithium-5 signed audit trail makes the platform 21 CFR Part 11-ready for FDA-grade GMP compliance; the CRI-ONE V20 PCIe 5.0 edge compute moves the inline-spectroscopy interpretation off general-purpose compute onto the inventor's own accelerator architecture; and the 500+ disease database integration ties Cooker outputs to the portfolio's disease-mechanism analysis work.

Why I made it

Conventional laboratory automation forces the user to commit to hardware before knowing whether the recipe will work. The robot arrives, the syringes are mounted, the firmware is configured, and only then does the chemist start designing recipes — learning what works and what doesn't through expensive failed runs on expensive hardware. The software-first inversion lets the recipe design happen in dry-run, on a developer's laptop, against a working interpreter and a working alchemy data set, before any hardware decision is made.

I built the Chemical Cooker because that inversion makes the platform genuinely accessible at the early-buyer stage. A research lab can subscribe to the Serum Build Platform, generate G-code recipes against lite Alchemy data, validate them in dry-run, and only commit to the hardware build (BOM, assembly, wiring, calibration) when the recipes are working. v2 then adds the FDA-grade compliance layer for when the lab needs to graduate from research to GMP production.

What it can do

Today, with software only: design chemistry recipes against lite Alchemy data, output G-code, validate in dry-run, run the Serum Build Platform with subscription + serial key, paste or upload G-code through the web UI for dry-run execution, and access the 500+ disease database (v2). The G-code dialect supports motion, dispense, heat, oven, microwave (positive and negative), stir, wait, tool changes, plus the v2-extended commands (N, R, V, U, I).

Tomorrow, when the buyer is ready to build hardware: full BOM, assembly steps, wiring diagram, calibration runbooks, safety and compliance documentation, plus the v2 hardware extensions (inline NIR + Raman, CV pre-flight deck validation, Dilithium-5 GMP audit trail, CRI-ONE V20 PCIe 5.0 edge compute, acoustic droplet dispenser, inert-atmosphere chamber, UV cure module, 180°C heating).

What this acquisition does not deliver: it does not include manufactured hardware. It does not include a chemistry licence in any jurisdiction. It does not include FDA approval for any specific recipe (the GMP audit-trail and FDA-application generators support the buyer's FDA filings, but the filings themselves remain the buyer's regulatory responsibility). It does not include the full Alchemy probability data — only the lite subset (full data is Project 07).

Why it's a fact

• The 16-chemical-cooker/ folder contents are inspectable on disk: software/ with all five Python modules and sample inputs, platform/ with the Serum Build app and lite Alchemy data, docs/ with G-code dialect references, blueprints/ with hardware design docs (v1 + v2), and 26+ top-level guide files.
• The v1 and v2 (, includes CRI-ONE V20 PCIe 5.0 accelerator seat) prices are stated in the inventor's README.md.
• The v2 engineering delta (inline NIR + Raman, CV pre-flight, Dilithium-5 GMP audit trail, CRI-ONE V20 edge compute, acoustic droplet, inert atmosphere, UV cure, 180°C, +5 G-code commands, 500+ disease database) is documented in the named v2 reference files in blueprints/ and docs/.
• The "software first" framing is explicit in the README and reproduced here verbatim.
• Per allinone.html Step-4: Project 16 = (the v1 heritage price). The v2 upgrade is a separate offering at the higher price point.
• The 500+ disease database integration ties to the broader portfolio's disease work (Projects 10 / 11 / 12 / 13 and related); the lite Alchemy subset ties to Project 07.

License Terms — What's Granted, What Isn't

The acquisition grants the buyer permission to make, build, and copy the deliverable. It does not transfer the underlying intellectual property:

• Granted with the acquisition: permission to run the software stack against the buyer's own recipes; permission to build hardware Cookers from the BOM and assembly documentation; permission to operate the Serum Build Platform under the subscription / serial-key model; permission to make copies of the design package and software for the buyer's research, R&D, GMP, and manufacturing use.
• Not transferred with the acquisition: the underlying G-code dialect IP, the Serum Build Platform IP, the lite Alchemy data's underlying full database (full Alchemy is Project 07), the v2 inline-spectroscopy / CV / Dilithium-5-audit / CRI-ONE-V20 IP, the 500+ disease database IP, the umbrella USPTO 19/540,453, trademarks, copyrights, or any rights to license or assign the IP onward to third parties. The intellectual property remains held by Christopher Gabriel Brown.
• The buyer's permission is to use the platform, not to own the rights behind the platform.

This framing applies uniformly across the inventor's portfolio. Buyers seeking IP assignment rather than make/build/copy permission should contact the inventor directly — that is a separate negotiation outside the standard storefront acquisition.

Software first. Hardware later. v1 heritage at ; v2 current at . Permission to make, build, and copy.