- Windows
- Python 3
- an
ESP32-C3board - a data-capable USB cable
Install esptool:
py -m pip install esptoolConnect the board and identify the serial port in Device Manager, for example:
COM3COM5
The examples below use COM3.
From the repository root:
py scripts/flash_firmware.py COM3Default flash layout:
0x0->bootloader.bin0x8000->partitions.bin0xe000->boot_app0.bin0x10000->firmware.bin
After flashing and reset:
py scripts/read_board_report.py COM3 --expect-mode logiqa_batch_compiled_probe --expect-artifact-sha256 626a1bfcc0a86585db82130744094ee4512eaaead8b4d9f1dba07175c010719dMode note:
- this readback checks one default single-batch report (
logiqa_batch_compiled_probe) - the published
642aggregate summary is reported aslogiqa_batch_compiled_probe_aggregated
This reads JSON from the board report partition.
The expected default report is:
Core fields:
artifact_nameartifact_sha256evaluation_modelogiqa_compiled_probefree_heap_bytesmin_free_heap_bytesartifact_crc32
Task-specific fields:
linear_gpu_probe_sampleslinear_gpu_probe_correctlinear_gpu_probe_expected_matchlinear_gpu_probe_host_full_matchlinear_gpu_probe_first_scores
The repository publishes the full board proof separately:
Important scope note:
- the default firmware reproduces one published fixed batch board report
- the full
LogiQA 642board proof is the aggregate over the included11raw board batches - those raw board reports are published under ../results/board_proof/raw
Flash the published MCU open-input firmware:
py scripts/flash_open_input_firmware.py COM3Run the open-input board evaluation:
py scripts/run_mcu_open_input_demo.py --port COM3Expected output file:
- ../results/open_input_demo/mcu_open_input_demo.json
- ../results/open_input_demo/mcu_open_input_board_report.json
Expected acceptance fields:
summary.exact_match_rate = 1.0summary.nonempty_rate = 1.0summary.stability_probe.stability_rate = 1.0summary.gates.all_pass = true
The repository also publishes a local verification helper for the public-safe experiment and document bundle:
python3 scripts/verify_public_bundle.pyThis checks:
- required mechanism and experiment docs exist
- generated experiment summaries match their manifest hashes
- the current surface row agrees with the published research manifest
Use:
- ../results/research_line/current_host_surface_manifest.json
- ../results/experiments/main_table.json
- ../results/experiments/ablations.json
This lets you compare:
- frozen parent
- exact no-trunk ablation
- same-parent contextual surfaces
- current host-side accepted surface
- board proof line
Use sha256sums.txt in the repository root to verify:
- documentation files
- scripts
- firmware binaries
- result JSON files
Maintainers working inside the full monorepo can refresh the public-safe experiment bundle with:
python3 scripts/run_public_logiqa_controls.py
python3 scripts/run_public_causal_sequence.py
python3 scripts/run_public_open_input_demo.py
py scripts/run_mcu_open_input_demo.py --port COM3
python3 scripts/export_block_inventory.py
python3 scripts/build_public_experiment_tables.py
python3 scripts/verify_public_bundle.pyThis path depends on the private workspace artifacts outside github_demo, so it is a maintainer path rather than a standalone public reproduction path.
run_public_logiqa_controls.py now regenerates:
- route-disabled, topology-removal, and depth-one current-surface controls
- target-only diagnostic controls
- retrieval-only and lexical-only classic baselines
- same-parent trained linear-readout control
- same-parent trained BitFit option-bias control
- same-parent trained LoRA-style hash-delta control
- same-parent trained low-rank adapter baseline
- same-parent trainable-budget-matched LoRA-style baseline
- same-parent trainable-budget-matched low-rank adapter baseline
- same-parent low-rank adapter-style controls
run_public_causal_sequence.py now regenerates:
- forward-addition three-family causal checkpoints
- order-swap three-family checkpoints
- reverse-removal checkpoints from the current surface
run_public_open_input_demo.py now regenerates:
- the host-side structured open-input exact-match report
- the host-side runtime proxy report
run_mcu_open_input_demo.py now regenerates:
- the board-side MCU open-input micro-loop exact-match report
- split-level and stability evidence for the published MCU taskset
For deeper reference, see: