Workflow rule: artifacts outlive the box - #21
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
nonrational
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A session that builds a reusable executable — a workflow script, a dispatch template — tends to leave it where it was born: the session directory, with a pointer in agent memory. Both die with the VM, so the next box re-derives the artifact from prose and repeats any mistakes the live runs had already fixed.
Motivation
This happened in practice today: a sweep orchestration script survived two live runs and accumulated two hard-won fixes, all in session state. The operator caught it ("memory isn't durable, it dies with a new exe box"). The durable home was the skill package all along; getting it there required exactly the steps the rule names — parameterizing machine- and repo-specific strings and scrubbing private names, since the destination repo is public.
Proposed Solution
One bullet under Iterative Working Style in
home/.agents/rules/workflow.md: reusable executables and templates get parameterized, scrubbed, and committed into the package they serve before the task ends; memory holds pointers to committed paths, never the artifact.Feedback
Placement is the main call: Iterative Working Style felt right since it's about how a task ends, but it could live under Git & PR Hygiene if you read it as a publishing rule. Also happy to tighten the wording — it's one sentence longer than the surrounding bullets.