FIELD NOTE / TIKTOK
Two agents edited the same config.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved TikTok edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
Two agents edited the same config.
Video caption
Two agents edited the same config. The missing control was shared intent. Shared decisions cross branches. #EricFieldNotes
Full written post / accessibility read
Fictional fleet: one agent broadens access for a customer migration, another changes the feature flag defaults. They work in separate branches, merge without a text conflict and pass their own tests. Together, they expose the feature to tenants the product owner never approved.
Separate checkouts prevent concurrent writes to one file. They do not guarantee that two patches satisfy the same source decision. The agent messages must carry the exact tenant, expiry and forbidden cohort. A supervisor should flag contradictory assumptions before an integrator merges.
Run protected allowed-and-denied tenant tests on the final merged build, not just each branch. Bind the report to its digest. In a disposable mutant, flip the default flag and confirm the gate turns red. The integrator needs a receipt explaining why the combined behavior preserves the customer agreement.
The rule: one owner defines product intent, agents isolate code, messages carry sourced constraints and a trusted gate judges the merged artifact. Do this because no number of clean branch merges proves the product's combined behavior.
#EricFieldNotes
Four-beat scene transcript
1. Two agents edited the same config.
Fictional fleet: one agent broadens access for a customer migration, another changes the feature flag defaults. They work in separate branches, merge without a text conflict and pass their own tests. Together, they expose the feature to tenants the product owner never approved.
Visual: The merge was clean. The product was not.
2. Worktrees did their job.
Separate checkouts prevent concurrent writes to one file. They do not guarantee that two patches satisfy the same source decision. The agent messages must carry the exact tenant, expiry and forbidden cohort. A supervisor should flag contradictory assumptions before an integrator merges.
Visual: The missing control was shared intent.
3. Test the combined artifact.
Run protected allowed-and-denied tenant tests on the final merged build, not just each branch. Bind the report to its digest. In a disposable mutant, flip the default flag and confirm the gate turns red. The integrator needs a receipt explaining why the combined behavior preserves the customer agreement.
Visual: The merge commit gets its own evidence.
4. Add traffic control after worktrees.
The rule: one owner defines product intent, agents isolate code, messages carry sourced constraints and a trusted gate judges the merged artifact. Do this because no number of clean branch merges proves the product's combined behavior.
Visual: Shared decisions cross branches.
Research and claim limits
- OpenAI Agents SDK/Codex orchestration example (S07)
- GitHub Docs: ruleset required status checks (S146)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.