atdd 0.2.4__tar.gz → 0.2.6__tar.gz

{atdd-0.2.4/src/atdd.egg-info → atdd-0.2.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atdd
-Version: 0.2.4
+Version: 0.2.6
 Summary: ATDD Platform - Acceptance Test Driven Development toolkit
 License: MIT
 Requires-Python: >=3.10
@@ -129,16 +129,44 @@ sync:
     # - qwen      # Uncomment to sync QWEN.md
 ```
 
-### ATDD Gate
+**Multi-agent setup:** To use multiple agents with consistent rules, enable them all in config and run sync:
 
-Verify agents have loaded ATDD rules before starting work:
+```yaml
+sync:
+  agents:
+    - claude
+    - codex
+    - gemini
+    - qwen
+```
 
 ```bash
-atdd gate                  # Show gate verification info
-atdd gate --json           # Output as JSON for programmatic use
+atdd sync  # Creates/updates CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md
 ```
 
-Example output:
+### ATDD Gate (Bootstrap Protocol)
+
+Agents often skip instruction files. The gate solves this by injecting rules via mandatory tool output.
+
+**Protocol:**
+
+1. Run this command first:
+   ```bash
+   atdd gate
+   ```
+
+2. Agent must paste output and confirm:
+   - Which file(s) were loaded
+   - The reported hash
+   - The key constraints
+
+3. If files are missing/unsynced:
+   ```bash
+   atdd sync
+   atdd gate  # Re-verify
+   ```
+
+**Example output:**
 ```
 ============================================================
 ATDD Gate Verification
@@ -157,9 +185,12 @@ Before starting work, confirm you have loaded these rules.
 ------------------------------------------------------------
 ```
 
-Agents should confirm at the start of each session:
-- Which ATDD file(s) they loaded
-- The key constraints they will follow
+**Why this works:**
+- Gate output is mandatory tool output - agent can't ignore it
+- Proves which ATDD files were actually loaded
+- Forces consistency across all agents
+
+**Rule:** If ATDD rules matter, start with `atdd gate`. No gate = no guarantees.
 
 ### Validation
 

{atdd-0.2.4 → atdd-0.2.6}/README.md

@@ -115,16 +115,44 @@ sync:
     # - qwen      # Uncomment to sync QWEN.md
 ```
 
-### ATDD Gate
+**Multi-agent setup:** To use multiple agents with consistent rules, enable them all in config and run sync:
 
-Verify agents have loaded ATDD rules before starting work:
+```yaml
+sync:
+  agents:
+    - claude
+    - codex
+    - gemini
+    - qwen
+```
 
 ```bash
-atdd gate                  # Show gate verification info
-atdd gate --json           # Output as JSON for programmatic use
+atdd sync  # Creates/updates CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md
 ```
 
-Example output:
+### ATDD Gate (Bootstrap Protocol)
+
+Agents often skip instruction files. The gate solves this by injecting rules via mandatory tool output.
+
+**Protocol:**
+
+1. Run this command first:
+   ```bash
+   atdd gate
+   ```
+
+2. Agent must paste output and confirm:
+   - Which file(s) were loaded
+   - The reported hash
+   - The key constraints
+
+3. If files are missing/unsynced:
+   ```bash
+   atdd sync
+   atdd gate  # Re-verify
+   ```
+
+**Example output:**
 ```
 ============================================================
 ATDD Gate Verification
@@ -143,9 +171,12 @@ Before starting work, confirm you have loaded these rules.
 ------------------------------------------------------------
 ```
 
-Agents should confirm at the start of each session:
-- Which ATDD file(s) they loaded
-- The key constraints they will follow
+**Why this works:**
+- Gate output is mandatory tool output - agent can't ignore it
+- Proves which ATDD files were actually loaded
+- Forces consistency across all agents
+
+**Rule:** If ATDD rules matter, start with `atdd gate`. No gate = no guarantees.
 
 ### Validation
 

{atdd-0.2.4 → atdd-0.2.6}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "atdd"
-version = "0.2.4"
+version = "0.2.6"
 description = "ATDD Platform - Acceptance Test Driven Development toolkit"
 requires-python = ">=3.10"
 readme = "README.md"

{atdd-0.2.4 → atdd-0.2.6}/src/atdd/coach/templates/ATDD.md

@@ -4,20 +4,41 @@ missions:
   validate_phase_transitions: "Phase transitions and quality gates per conventions and schemas"
   required: true
 
-# ATDD Gate (REQUIRED before any work)
-# =====================================
-# Before starting ANY task, you MUST confirm you have loaded these rules.
-# Provide this confirmation at the start of your first response:
+# =============================================================================
+# ATDD AGENT BOOTSTRAP PROTOCOL (REQUIRED)
+# =============================================================================
 #
-#   ## ATDD Gate Confirmation
-#   - **File loaded:** CLAUDE.md (or AGENTS.md, etc.)
-#   - **Key constraints:**
-#     1. No ad-hoc tests - follow ATDD conventions
-#     2. Domain layer NEVER imports from other layers
-#     3. Phase transitions require quality gates
+# Problem: Agents often skip instruction files and work without ATDD context.
+# Solution: Coercive context - inject rules via mandatory tool output.
 #
-# If you cannot provide this confirmation, STOP and reload the rules.
-# Run `atdd gate` to verify the expected values.
+# PROTOCOL:
+# ---------
+# 1. Run this command FIRST:
+#
+#    atdd gate
+#
+# 2. Paste the output and confirm:
+#    - Which file(s) were loaded
+#    - The reported hash
+#    - The key ATDD constraints
+#
+# 3. If output shows missing/unsynced files, run:
+#
+#    atdd sync
+#
+#    Then re-run: atdd gate
+#
+# WHY THIS WORKS:
+# - Gate output is mandatory tool output - agent can't ignore it
+# - Proves which ATDD files were actually loaded
+# - Forces consistency across all agents
+#
+# FAILURE MODE:
+# - If agent skips the gate: STOP and run atdd gate again
+# - Don't proceed until gate confirmation is posted
+#
+# RULE: If ATDD rules matter, start with `atdd gate`. No gate = no guarantees.
+# =============================================================================
 
 manifest:
   - trains: "plan/_trains.yaml"

{atdd-0.2.4 → atdd-0.2.6/src/atdd.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atdd
-Version: 0.2.4
+Version: 0.2.6
 Summary: ATDD Platform - Acceptance Test Driven Development toolkit
 License: MIT
 Requires-Python: >=3.10
@@ -129,16 +129,44 @@ sync:
     # - qwen      # Uncomment to sync QWEN.md
 ```
 
-### ATDD Gate
+**Multi-agent setup:** To use multiple agents with consistent rules, enable them all in config and run sync:
 
-Verify agents have loaded ATDD rules before starting work:
+```yaml
+sync:
+  agents:
+    - claude
+    - codex
+    - gemini
+    - qwen
+```
 
 ```bash
-atdd gate                  # Show gate verification info
-atdd gate --json           # Output as JSON for programmatic use
+atdd sync  # Creates/updates CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md
 ```
 
-Example output:
+### ATDD Gate (Bootstrap Protocol)
+
+Agents often skip instruction files. The gate solves this by injecting rules via mandatory tool output.
+
+**Protocol:**
+
+1. Run this command first:
+   ```bash
+   atdd gate
+   ```
+
+2. Agent must paste output and confirm:
+   - Which file(s) were loaded
+   - The reported hash
+   - The key constraints
+
+3. If files are missing/unsynced:
+   ```bash
+   atdd sync
+   atdd gate  # Re-verify
+   ```
+
+**Example output:**
 ```
 ============================================================
 ATDD Gate Verification
@@ -157,9 +185,12 @@ Before starting work, confirm you have loaded these rules.
 ------------------------------------------------------------
 ```
 
-Agents should confirm at the start of each session:
-- Which ATDD file(s) they loaded
-- The key constraints they will follow
+**Why this works:**
+- Gate output is mandatory tool output - agent can't ignore it
+- Proves which ATDD files were actually loaded
+- Forces consistency across all agents
+
+**Rule:** If ATDD rules matter, start with `atdd gate`. No gate = no guarantees.
 
 ### Validation