Maintainer decision, 2026-07-30: rein-aharness is executor-worker's
real, live successor - no coulomb/executor-worker Forgejo repo will
be created. Local directory moved to
archive/260717-executor-worker-retired/ (timestamped to its actual
retirement commit date) to get it out of the active workstation
directory listing; git history preserved intact by the move.
the-custodian: TRSL applied per explicit maintainer confirmation
(superseding its prior Proprietary and Confidential license) - all ~90
repos now have TRSL.
executor-sandbox: local ~/executor-sandbox directory turned out to be
a stale, disconnected clone (unrelated git history, no origin remote
configured at all) - the real Forgejo repo has entirely different
content (a rein-aharness smoke-test target). Worked against a fresh
clone of the real repo instead: established INTENT.md/SCOPE.md from
its actual observed purpose and applied TRSL, committed/pushed
directly to coulomb/executor-sandbox.git.
executor-worker: confirmed retired per its own README - adopted into
agent-harness (2026-07-17), which was itself later renamed
rein-aharness (glas-harness ADR-001, 2026-07-26). No
coulomb/executor-worker or coulomb/agent-harness repo exists on
Forgejo; rein-aharness is already the live, deployed successor.
Whether to still create a Forgejo repo for the retired prototype's
history is left as an open question, not decided unilaterally.
history/260730-ExecutorRepos-ArchitectureFindings.md records the full
architecture map verified against each repo's own SCOPE/README/ADRs:
activity-core -> issue-core -> glas-harness (router) -> rein-aharness/
rein-openweights (concrete backends) -> llm-connect (adapter engine),
sand-boxer (isolation, consumed by glas-harness), kaizen-agentic
(personas/memory, "prepare" not "execute"). Flags phase-memory's
relationship to kaizen-agentic/agentic-resources as unconfirmed, and
agentic-resources' own SCOPE.md as still an unrefined auto-generated
placeholder.
