Repository navigation
docs: write up an agentic development harness as RFC-003 - #103
Merged
Merged
Conversation
arthware-dev
force-pushed
the
docs/agentic-harness-rfc
branch
from
September 20, 2026 14:25
3dc836a to
71864fa
Compare
macOS has no container, so isolation cannot be borrowed from the OS and has to be built in the framework. Records what each macOS mechanism actually isolates, what blocks an agent in this repo today, and a cost-ordered path: a lane contract, APFS snapshot and restore, a lease on the shared lanes, instance namespacing, and an instance that says whether it is development or production. That last one inverts today's default. Development happens on a laptop whose instance is the Simpsons demo, where an agent may destroy and reinstall at will; production is a different Mac holding a real family's data. Nothing reports which one an agent is standing in, so care gets applied uniformly: too slow where it is pointless, and unreliable where it is the only safeguard. The rig already has half the mechanism in `.stack/.test-instance`. Two premises were measured rather than assumed: `cp -c -R` clones 200MB in 0.00s on APFS, and OrbStack's daemon socket is per user, which makes a second macOS account a real isolation axis.
arthware-dev
force-pushed
the
docs/agentic-harness-rfc
branch
from
September 21, 2026 11:43
71864fa to
614df36
Compare
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
1 participant
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.
Summary
project_states()reporting another instance's containers as its own,_refresh_coretouching the shared bot runner, and shared lanes coordinated by courtesy.Two premises were measured rather than assumed:
cp -c -Rclones 200MB in 0.00s on APFS, and OrbStack's daemon socket is per user (~/.orbstack/run/docker.sock), which makes a second macOS account a real isolation axis.No code, and no decision taken. It ends on three open questions, the sharpest being whether the demo rig should stay the daily-use instance it is today, since it is currently both the family's data and the test target, which is why care substitutes for isolation.