The Framework
Delta Syncing
In Agile, a change of plan requires a Pivot Meeting, re-estimation, re-briefing the team, and a cascading update across every developer's understanding. In AS2, it's a single Manifest update. The rest is automatic.
Agile pivot
- 1.Schedule a pivot meeting
- 2.Re-estimate the affected work
- 3.Brief every developer individually
- 4.Update tickets, backlogs, docs
- 5.Wait for the next sprint to absorb the change
AS2 Delta Sync
- 1.Architect updates the Manifest
- 2.Orchestrator diffs old vs new
- 3.Affected agents receive the delta
- 4.Code refactored within minutes
- 5.Orchestrator validates and merges
How it works
Manifest update
The Architect updates the affected Manifest to reflect the new requirements. This is the only manual change required. Everything downstream is automatic.
For a major pivot, multiple Manifests may need updating. But each update is a precise, structured document — not a verbal briefing to 10 people.
Orchestrator diffs
The AI Orchestrator automatically compares the old Manifest with the new one and generates a precise change delta — exactly which inputs, outputs, or logic constraints changed.
The diff is machine-readable, so agents can consume it directly without any human translation or re-explanation.
Agent notification
Each affected Operator's agent receives a targeted notification: "The contract has changed. Here is the diff. Update the logic accordingly."
No meeting required. The agent receives the same structured information that would previously require a 30-minute sync call.
Code refactored + re-validated
The agent refactors the code to match the new Manifest within minutes. The Orchestrator then runs the full validation pipeline — adversarial audit, contract check, and assembly — before merging.
The refactored Shard goes through the same quality gate as any new Shard. Pivots don't bypass the safety net.
When to use Delta Syncing
API contract changed
A downstream service changed its response shape. Update the affected Manifests — agents refactor.
Feature scope reduced
A feature was descoped mid-sprint. Update the Manifest, agents remove the unnecessary code.
New technical constraint added
Security team mandated a new pattern. Update every affected Manifest. Agents adopt it.
Requirements clarified
A vague requirement became specific after user testing. Tighten the Manifest; agents align.
Key insight
Pivots are expensive in Agile because knowledge lives in people's heads. In AS2, knowledge lives in the Manifest. A Manifest update is the only pivot cost — and it takes minutes, not a sprint.