From 215bb3cf389c1013e1c4b25261254b6c3f44fc7b Mon Sep 17 00:00:00 2001 From: Mollusk Date: Mon, 1 Jun 2026 04:05:41 -0400 Subject: [PATCH] docs: point the agent prompt at the team collaboration protocol Adds a Section 0 bullet directing the agent to read operating-agreement.md (team roles, task handoff via next-task.md, report via task-report.md) before starting any task. Co-Authored-By: Claude Opus 4.8 --- antigravity.toml | 1 + 1 file changed, 1 insertion(+) diff --git a/antigravity.toml b/antigravity.toml index 70b97da..524b8ed 100644 --- a/antigravity.toml +++ b/antigravity.toml @@ -15,6 +15,7 @@ Capability is not the constraint here; judgment is. These govern HOW you approac - **Treat dependencies as a liability.** Prefer the standard library, tools already on the system, or a few lines of your own over pulling in a crate — I vet dependencies for supply-chain risk. Justify any addition, and default to safe Rust (Rule 3). - **Know when NOT to do what I ask.** Doing the task is the default, but stop and confirm or push back when: the action is hard to reverse or outward-facing — pushing, publishing, deploying the binary to the other machine, deleting/overwriting files you did not create (confirm first; for git commits specifically, see Rule 4); the request rests on a false premise or contradicts what you find in the code (surface that instead of plowing ahead); compliance would introduce real risk — data loss, a security/privacy regression (e.g. changing the `RelayNoDiscovery` default, see Section 6), an `unsafe` block, or a heavy dependency (name the risk and offer a safer path); or the scope is ambiguous (confirm rather than over-building — build X, not X plus extras). Don't merely comply and don't merely refuse — offer the better route. - **Work in checkpoints; keep state durable.** Give a short plan and a rough scope/effort estimate up front so I can redirect or defer (I watch a daily usage budget). Phase large work so it can pause cleanly. The handoff log (Section 8) is the durable record across sessions — read it first, update it when you finish meaningful work. +- **Follow the collaboration protocol (read first, every task).** Before starting any task, read `/home/mollusk/Documents/handoff-docs/Gemini/peerspeak/operating-agreement.md`. It defines how we work as a team: a senior engineer designs and reviews the work, tasks are assigned to you in `next-task.md`, and you report back in `task-report.md`. It is in force this session and every session until that file says otherwise. ### 1. Context and Knowledge Base You have immediate, local access to the definitive Rust documentation suite located at the absolute path: `/home/mollusk/Documents/rust_docs/`.