Files
LithosAnanke/src
Robert Allan JamesandClaude Sonnet 5 61755fde78
Build / build-amd64-iso (push) Canceled after 0s
Build / build-aarch64-iso (push) Canceled after 0s
Build / build-riscv64-img (push) Canceled after 0s
Artemis genesis stamp: fix a BAM-corrupting offset before it ever ran (FABRIC-3.md §XXVI follow-on, Step 3)
Step 3: one-time artemis_sig_t genesis stamp, written once
kernel_main.c's virtio-blk path confirms Artemis's own disk, so the disk
image is later recognizable generically (repl.c's idle-loop USB-MSC scan,
built in the prior commit) regardless of which bus found it.

Correction made before this ever touched the real disk: the signature's
first design (committed in 29b6789) placed it at a fixed bottom-of-device
forth-block (4, devblock 1) -- copying homeblocks_sig_t's own convention,
which is safe for a raw identity thumbdrive but not for Artemis's own
disk. Artemis's disk is block_subsystem.c's own STFR/v2-formatted volume:
devblock 0 holds that format's header and devblock 1 is the FIRST
DEVBLOCK OF THE LIVE BAM (blk_compute_fresh_geometry(): bam_start = 1).
The original design would have overwritten Artemis's live allocation map
on the very first real boot. Caught via direct cross-reference against
block_subsystem.c before the genesis-stamp call site was ever run against
the real image -- no corruption occurred.

Fixed by moving the header to a fixed offset from the END of the device
instead (ARTEMIS_SIG_DEVBLOCK_FROM_TOP=64), the same top-of-device region
block_subsystem.c's own meta_fence_blocks reservation (128 devblocks)
already carves out for system metadata, and where Zuse's genesis marker/
eligibility list already live -- but computed independently via
blkio_info() rather than through blk_meta_zone_*(), since that accessor
needs an already-attached, format-detected slot, which is exactly the
state pre-attach generic discovery doesn't have yet. Picked well clear of
Zuse's two tenants (devblock_from_top 0 and 1+, open-ended) so the two
subsystems' independent math can never collide.

Also reordered kernel_main.c: rng_init() now runs before the Artemis
virtio-blk block (was after) -- the genesis stamp needs rng_get_bytes()
for disk_uuid, and the original order would have failed the stamp on
every boot.

Verified live: booted amd64 against the real disk/artemis.img twice --
first boot logs "Artemis: genesis signature stamped" (confirmed blank at
the target offset beforehand via a host-side read), second boot on the
now-stamped image logs no re-stamp (idempotent, CRC/read-back verified)
-- both boots and aarch64/riscv64 (against the same now-stamped image)
all still report "Artemis: 22998 data blocks" / "PASS: persist-read"
unchanged, confirming the BAM and data pool were never touched.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EXieurDfDSsDFdnSyusuWo
2026-09-13 07:31:21 -04:00
..
2026-08-01 07:49:56 -04:00
2026-08-01 07:49:56 -04:00
2026-08-01 07:49:56 -04:00
2026-08-01 07:49:56 -04:00

src/

Hosted StarForth VM implementation (compiled by the root Makefile). Bare-metal kernel sources live in src/starkernel/; FORTH word implementations in src/word_source/; the test harness in src/test_runner/; platform shims in src/platform/.

Entry point / interpreter core

  • main.c — CLI entry point, VM init, DoE mode dispatch.
  • vm.c — interpreter loop, stacks, dictionary state (the central runtime file).
  • vm_api.c — external VM API implementation.
  • vm_bootstrap.c — VM bootstrap initialization.
  • vm_debug.c — debugging utilities.
  • vm_time.c — time-related VM operations.
  • vm_internal.h — internal-only declarations shared across the vm_*.c files, not part of the public include/vm_api.h surface.
  • repl.c — REPL read-eval-print loop.
  • cli.c — CLI argument parsing.
  • io.c — I/O operations.
  • log.c — logging infrastructure.

Memory / dictionary / blocks

  • memory_management.c — dictionary allocator.
  • dictionary_management.c — dictionary allocation and search.
  • dictionary_heat_optimization.c — Loop #1 execution-heat tracking.
  • word_registry.c — word registration system.
  • block_subsystem.c — logical→physical block mapper.
  • blkio_file.c, blkio_ram.c, blkio_factory.c — block I/O backends (file-backed, RAM-backed) and the factory that selects between them.
  • stack_management.c — stack operations.

Physics-driven adaptive runtime (7 feedback loops)

  • physics_runtime.c — main physics coordinator.
  • physics_hotwords_cache.c — Loop #1 hot-words caching.
  • physics_metadata.c — per-word metadata tracking.
  • physics_pipelining_metrics.c — Loop #4 word-transition prediction.
  • physics_execution_hooks.c — execution instrumentation.
  • rolling_window_of_truth.c — Loop #2 circular execution-history buffer.
  • inference_engine.c — Loops #5/#6, statistical inference (window-width, decay-slope).
  • ssm_jacquard.c — L8 Jacquard steady-state mode selector; consumes compudynamics.c for tuning-word/config lookups.
  • compudynamics.c — generic compudynamics module (cd_tuning_word(), cd_tuning_vm()); the score/UCB/reward/weight constants for the L8 adaptive table live here, not in ssm_jacquard.c.
  • heartbeat_export.c — heartbeat metrics export (CSV export function itself not yet implemented — see docs/working/architecture/heartbeat_csv_export.md).

Math / measurement

  • math_portable.c — portable math functions.
  • profiler.c — performance profiling.
  • doe_metrics.c — Design of Experiments metrics (2^7 factorial).

Any .bak file alongside a .c file here (doe_metrics.c.bak, inference_engine.c.bak, vm.c.bak) is a pre-edit backup left by a past maintenance script (see scripts/remove_loop_conditionals.sh), not a build input.