Adds a hard rule: workers MUST use the data provided in their task context. They MUST NOT fetch their own data from external sources unless explicitly told to.
Why
E2E delegation test revealed the #1 source of cross-worker inconsistency: a writer worker queried the Proxmox API directly instead of formatting the raw SSH data it was given, producing a report with fabricated node IPs, phantom VMs, and false 'online' statuses.
Changes
New Data Source Integrity section (hard rule, not recommendation)
Dispatch guidance with example showing explicit data-source instruction
Anti-pattern entry: workers fetching their own data sources
Orphan pre-merge file removed
Test Evidence
E2E test dispatched devops → writer → review. Review worker caught all discrepancies that this rule would prevent.
## What
Adds a hard rule: workers MUST use the data provided in their task context. They MUST NOT fetch their own data from external sources unless explicitly told to.
## Why
E2E delegation test revealed the #1 source of cross-worker inconsistency: a writer worker queried the Proxmox API directly instead of formatting the raw SSH data it was given, producing a report with fabricated node IPs, phantom VMs, and false 'online' statuses.
## Changes
- New **Data Source Integrity** section (hard rule, not recommendation)
- Dispatch guidance with example showing explicit data-source instruction
- Anti-pattern entry: workers fetching their own data sources
- Orphan pre-merge file removed
## Test Evidence
E2E test dispatched devops → writer → review. Review worker caught all discrepancies that this rule would prevent.
Workers MUST use provided input data, not fetch external sources.
Adds: Data Source Integrity section, dispatch guidance example,
anti-pattern entry. Root cause of e2e test discrepancies where
writer worker queried Proxmox API instead of using raw data.
jerome
merged commit 22eaaf4254 into master2026-07-12 18:09:16 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Adds a hard rule: workers MUST use the data provided in their task context. They MUST NOT fetch their own data from external sources unless explicitly told to.
Why
E2E delegation test revealed the #1 source of cross-worker inconsistency: a writer worker queried the Proxmox API directly instead of formatting the raw SSH data it was given, producing a report with fabricated node IPs, phantom VMs, and false 'online' statuses.
Changes
Test Evidence
E2E test dispatched devops → writer → review. Review worker caught all discrepancies that this rule would prevent.