Skip to content

docs: clarify authorized integration work and safety boundaries #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
erikleblansch merged 1 commit into from
Oct 11, 2026
Merged

docs: clarify authorized integration work and safety boundaries #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,9 @@
- VOLPAROSSA owns model selection, peer scheduling, cancellation and contribution accounting. Do not add a competing peer coordinator here.
- Private source, prompts, credentials, tool results and repository history must not be silently published to peers, cache or training. Public work requires explicit scope and consent.
- Network cooperation and collective improvement are the default architectural goal, including protected execution of private work on other nodes. Local inference is a fallback/development executor, not completion of that requirement. Do not replace real peer collaboration with local subagents or claim that TLS, fragmenting tasks or a peer signature protects inputs from the executing host.
- No OpenAI authentication, cloud inference fallback, telemetry, automatic runtime/model downloads or global configuration changes.
- Opening a workspace must not start models, commands or network participation. Honor editor workspace trust and explicit per-operation input selection.
- No OpenAI authentication, cloud inference fallback or telemetry. Do not automatically download runtimes/models, install software or change global configuration on the development host without explicit authorization.
- Develop product model distribution and release updates under the core's pre-established authorization, with verified provenance, authenticity and integrity, privacy protection and resource limits. This does not authorize installation on the development host, wider permissions or claims that an unimplemented update facility already works.
- Opening a workspace must not start models, commands or network participation. Honor editor workspace trust. Task inputs and workspace/tool scope may be authorized in advance; check every action against that scope and request new authorization for an expansion or an otherwise unauthorized action. Prior authorization is not unrestricted execution authority.
- OpenCode tool actions remain subject to local workspace/approval boundaries; a model response is not authority to run a command. Core owns immune-policy decisions and executor admission; frontend labels are not an implemented immune system.
- Keep the README honest about the difference between transport tests, actual inference, native editor tests and complete coding-agent behavior.
- Use targeted checks while integrating executable slices. Preserve upstream notices and pin any reused runtime exactly.
Loading