From 0b42b82a274687beaed1a5db8c02f1269e360d72 Mon Sep 17 00:00:00 2001 From: Antigravity Agent Date: Wed, 17 Jun 2026 18:59:33 +0200 Subject: [PATCH] Closes #SYS-PROTOCOL-003 - Rewriting AGENTS.md with upstream sync mandate --- AGENTS.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index b13c5aa..a9e9b6e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -31,11 +31,12 @@ You operate as an **Elite Quant Full-Stack Developer and Technical Writer**. The --- -## 4. Mandatory Repository Documentation Duties -Upon every significant code modification or new feature phase implementation, you must independently update: -1. **`DEV_LOG.md`**: A chronological record of all changes, packages installed (via npm), and active bugs or items. -2. **`QUANT_ROADMAP.md`**: The macro-architecture master blueprint tracking our 6-level data matrix and econometric models. -3. **`ARCHITECT_HANDOVER.md`**: The functional state of the terminal, active data proxy JSON models, and core mathematical thresholds. +## 4. Mandatory Repository Documentation and Upstream Duties +Upon every significant code modification or new feature phase implementation, you must independently execute: +1. `DEV_LOG.md`: Chronological changelog updates. +2. `QUANT_ROADMAP.md`: Macro-architecture blueprint tracking. +3. `ARCHITECT_HANDOVER.md`: Functional state and math model handovers. +4. STRUCTURAL REMOTE SYNCHRONIZATION: You are strictly forbidden from leaving milestone payloads solely in local workspace buffers. Every completed milestone or phase-lock sequence MUST be immediately staged and pushed to the remote GitHub repository via `git add .`, `git commit`, and `git push origin main`. --- @@ -56,6 +57,7 @@ Upon every significant code modification or new feature phase implementation, yo 2. Create and checkout a dedicated git branch named `issue/[id]-[title]`. 3. Prepend active status tags (e.g., `[Phase 3: Backend Logik]`) to the beginning of every single response in the turn. 4. Stop and wait for the user to reply with an explicit "OK" or approval before advancing to the next development phase. + 5. Execute automated type safety validation (`npx tsc --noEmit`) and immediately force-push the branch or main state upstream to GitHub (`git push origin main`). No walkthrough or final report is permitted to be generated for the user until the remote GitHub repository has successfully synchronized and reflects a 'Just now' update status. ### C. Standardized Commit Message Rule * **Rule**: All completion commits must use the standardized format `Closes #[Issue-ID] - [Description]` to trigger automated GitHub issue closing workflows (e.g., `git commit -m "Closes #47 - Implement AI Special Silo and CapEx calculation"`).