Files
LithosAnanake/docs/working/architecture
Robert Allan JamesandClaude Opus 5 7597a9ccd4 Add Artemis compudynamics implementation plan; add stress campaign fixture
The 30-replicate Artemis surface-stress campaign ran across all three
architectures: 30 reps x 50 trials x 3 arches = 4500 trials, zero failures.
The block_words.c stale-pointer cache-aliasing fix holds at scale.

Adds ART-STRESS-CAMPAIGN (block 4174) plus ART-STRESS-REP rep-tagging in
the CSV header/summary emitters, so a multi-replicate run is distinguishable
in the serial log. Campaign auto-invoke is left enabled in block 4170 for
now; Makefile.starkernel's QEMU boot deadlines stay at 12h to accommodate
long-running experiments.

Adds docs/working/architecture/ARTEMIS-COMPUDYNAMICS-IMPLEMENTATION-PLAN-20260802.md,
which documents the real gap this campaign exposed: block heat and message
heat do not decay at all. ART-TICK has zero call sites anywhere in the tree,
and HERMES-TICK has zero C call sites -- every caller is Hera poking it by
hand. BLK-HEAT@/MSG-HEAT@ read a number nothing ages, so blocks never reap
by cooling and message TTL never expires on its own.

The plan mirrors word-level physics as the reference model: lazy decay at
each access point against vm->heartbeat.tick_count, plus a bounded
background sweep with a resumable cursor (the existing answer to "sweeping
22,998 blocks per tick is too expensive"). Phase 1 Artemis, Phase 2 Hermes,
Phase 3 K participation deferred behind the Logical BAM.

The plan's preamble also records a wrong turn taken while investigating:
chasing VM-fleet heat instead of block heat, and building synthetic
Hera-driven VM-EXEC calls to force a physics reading -- which TRIPOD.md
prohibits outright. That work was reverted; the record is kept so it isn't
repeated.

Status: plan approved in shape, NOT final and NOT started. Six open
questions need answers and further design discussion is pending.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-02 21:49:16 -04:00
..

docs/working/architecture/

Living system-design documentation: physics engine, HAL, heartbeat, pipelining, word-ACL, adaptive systems, getting-started, and dated design/finding notes for individual VM subsystems. This is the working-tier source material that docs/formal/scraps/architecture/ is generated from.

  • 03-architecture/ — Core architecture reference: OVERVIEW.md, plus adaptive-systems/, hal/, heartbeat-system/, physics-engine/, pipelining/, word-acl/ subtrees. Has its own README.md.
  • getting-started/ — New-user and developer setup guides (DEVELOPER.md, INSTALL.adoc, QUICKSTART.adoc, quick-start/). Has its own README.md.
  • architecture-internals/INIT_SYSTEM.adoc, MESSAGING.adoc.
  • build-and-tooling/BUILD_OPTIONS.adoc, DOCUMENTATION_README.adoc, INIT_TOOLS.adoc.
  • doxygen/DOXYGEN_QUICK_REFERENCE.adoc, DOXYGEN_STYLE_GUIDE.adoc.
  • MAMA_FORTH_SUPERVISOR_ARCHITECTURE.adoc — Mama VM supervisor design.
  • PHYSICS_CONE_OF_INFLUENCE_DESIGN.adoc, PHYSICS_CONTROL_SYSTEM_DESIGN.adoc, PHYSICS_SIGNAL_MAP.adoc — physics-engine control-system design notes.
  • VM_FORMALIZATION_PLAN.adoc — plan for Isabelle/HOL VM formalization.
  • heartbeat_csv_export.md — heartbeat CSV export design (implementation status tracked in .claude/CLAUDE.md).
  • Dated design/finding notes for the Tripod VMs: ARTEMIS-BAM-ACCEPTANCE-*, ARTEMIS-BLOCK-PHYSICS-DESIGN-*, ARTEMIS-FREEMAP-CAPSULE-RESERVATION-GAP-*, CAPSULE-BLOCK-PERSISTENCE-BOUNDARY-FINDING-*, CAPSULE-LOADER-DEFINITIONS-ONLY-DESIGN-*, HERMES-MESSAGE-BLOCK-STORAGE-DESIGN-*, HERMES-MESSAGE-CHANNEL-PHYSICS-DESIGN-*, K-PUSH-DICTIONARY-SHADOWING-BUG-*, VM-FLEET-ATTRACTOR-DESIGN-*, VM-PHYSICS-DYNAMIC-FLEET-DESIGN-*.

See also