Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 14913@bnt-lap001 Assistant-Session: add7ef69-b901-4756-9a67-34cf1125d96f
2.2 KiB
Decision 2026-10-12: unattended publication of reality checkpoints
Decided by: the founder (Bernd Worsch), in session, 2026-10-12.
Context: ASSEMBLY-WP-0010, research/ScenarioBandMethod.md § 6.
Decision
- Reality checkpoints are scheduled by activity-core on railiance01
(definitions
assembly-checkpoint-*) and executed by rein-aharness (approachassembly-checkpoint), following the org recurring-automations playbook. They are not run by cloud routines or workstation cron. - Data comes from deterministic fetchers (web-fetcher) with provenance. llm-connect is used only to draft an assessment from fetched data. An assessment containing numbers that are not in the data is rejected.
- rein-aharness may commit and push to
assembly-economicsorigin unattended, limited to paths undercheckpoints/, fast-forward only. On rejection it rebases once (only if all unpublished commits stay withincheckpoints/), and never forces. This mirrors the Freedom Intelligence brief publication grant (FI decision 2026-09-22).
Consequences
- The publish grant widens what an unattended executor writes to origin. It
is recorded on the security close-down checklist
(
the-custodian/docs/security-close-down-checklist.md) for review at close-down. - The approach runs on rein-aharness legacy (profile-absent) routing, which
is allowed until 2026-12-31 (
AGENT_HARNESS_LEGACY_APPROACHES_UNTIL). A governed execution profile is needed before then (ASSEMBLY-WP-0010-T05).
Addendum 2026-10-13: execution declaration approved
The founder approved checkpoints/EXECUTION_DECLARATION.md in session on
2026-10-13. It is the per-definition declaration for leaving legacy,
profile-absent routing (rein-aharness docs/legacy-runtime-inventory.md,
step 2). It covers inputs, code, write paths (checkpoints/ only), network
egress (the hosts in checkpoints/sources.json and llm-connect), model and
credential routes, commit and publication policy (unchanged from this
decision), and rollback. The choice between a tenant-owned blueprint and a
Glas profile, and the location of the path-scoped publish grant, are left to
rein-aharness and glas-harness (ASSEMBLY-WP-0014-T01).