Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Enforce side-effect isolation mechanically in agent-documentation experiments
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
Treat always-loaded repository instructions as a routing budget, but evaluate changes only in an environment that mechanically enforces the trial envelope. Keep bootstrap guidance small, route to domain documentation when the task requires it, and preserve safety, migration, authorization, and integration rules that the task set does not exercise. Block mutation tools and prohibited history/status commands at the environment boundary rather than relying on prompt instructions alone. Applicability and limits: task-balanced isolated runs can compare correctness and context cost for bounded maintenance work. If inherited instructions or tools cause writes outside the protocol, the run is evidence about harness leakage, not a clean estimate of the documentation intervention. Do not generalize bounded repair results to architecture, incidents, or long-running work.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review