docs: bring the README, runbook, glossary and ADR notes up to date
Some checks failed
validation / verify (push) Failing after 11s
Some checks failed
validation / verify (push) Failing after 11s
The README now covers the router, Change requests, overlay Skills, Jev's uses and the current layout. VALIDATION.md no longer points at the removed root Terraform. ADR-0004 and ADR-0007 gain dated "As built" notes; ADR-0007's says which uses of Jev send Deliverable content. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -9,6 +9,8 @@ How to give the solution architect agent safe, read-only access to Google Cloud'
|
||||
- **Content excluded.** Tools that return data content are excluded even though they are read-only: Cloud SQL `execute_sql_readonly`, Cloud Storage `read_object`/`read_text`/`list_objects`, and generic Kubernetes reads that can return Secrets (`get_k8s_resource`, `describe_k8s_resource`).
|
||||
- **Permission per Execution.** Tools that read your environment (`cloud_read`) run only after the user grants permission in that Execution. Pre-approved Executions deny it unless the caller passes `allow_cloud_read=true`.
|
||||
|
||||
- **Replies are checked.** When Jev is configured, a server's reply that reads as instructions to the agent, as opposed to information, is withheld from the Specialist and logged (`JEV_GUARDRAIL`). Without Jev, replies pass through.
|
||||
|
||||
These are defence in depth. Enforce read-only access in Google Cloud as well.
|
||||
|
||||
## Set up a project the agent may read
|
||||
|
||||
Reference in New Issue
Block a user