microsoft/amplifier-bundle-converge

microsoft/amplifier-bundle-converge

Description: Converge workflow bundle for the Amplifier project

Language: Python

License: MIT

Stars: 0

Forks: 0

Open issues: 0

Created: 2026-09-01T14:58:35Z

Pushed: 2026-09-03T06:32:21Z

Default branch: main

Fork: no

Archived: no

README:

Amplifier Converge

You define what must be true. It builds toward it — with you, over time.

Converge is a way of working above the level of tasks and code. You write down where a project is going and what must be true of it; the work of getting there is planned, run, and checked for you, and comes back to you only where a person is irreplaceable.

The three roles

• You — the intent steward. You set the direction and make the decisions

only a person can make: ratify a change to the direction, make an irreversible choice, check what only a person or a device can check, set priority or stop. Anything else that reaches you is a defect.

• The manager session — one long-running AI session that runs a project's

work on your behalf, for days or weeks. It owns the queue, plans the order, briefs and launches worker sessions, notices silence, verifies by its own re-run check rather than by a worker's account, and writes you a brief in plain sentences for your return.

• Worker sessions — many short-lived AI sessions, each taking one bounded

piece of work in its own copy of the code and returning with proof. Each piece ends one of three ways: done with proof; stuck, with the cause; needs your judgment.

You write the direction in two documents. A vision — the project as it will be when it is right, written as though already true. And contracts — the specific promises the project must keep, each short enough to read in a minute and precise enough to check against reality. Both are written for people.

A document begins as a draft and becomes locked when it says what it means, carries a real example of right and wrong, can be checked against reality, and you have read it and agreed. A locked document changes only by written proposal backed by evidence — a cost actually paid or a failure actually caught. Preference is not evidence. Nobody edits a locked document in place; the guard refuses.

The two halves

Direction — the vision and the contracts as one experience: what changed since you last read, whether each contract is kept, your questions on any paragraph, every proposal awaiting your word.

Operation — the manager session at work: your return brief, the plan, what is running against what waits on you, lanes running against lanes intended, evidence you can inspect, your limits, a place to drop feedback.

Both halves are the project's own truth, read from the repository. The app holds no data of its own.

Install

THE install path — the behavior (`--app`):

amplifier bundle add git+https://github.com/microsoft/amplifier-bundle-converge@main#subdirectory=behaviors/converge.yaml --app

This composes Converge's capability layer onto whatever bundle is already active: the four agents (protocol-authority, reconciler, negotiator, proposal-drafter), the five procedure skills, the hooks-candidate-guard hook (the guard that refuses edits to locked documents, on by default), the thin awareness context, and — via a behavior-includes-behavior include — the amplifier-work-tracker behavior that gives reconciler its work_* filing tools. Use this to add Converge to an existing workspace or session.

Full-workspace path — Converge as the primary bundle:

amplifier bundle add git+https://github.com/microsoft/amplifier-bundle-converge@main
amplifier bundle use converge

This composes the root bundle.md, which assembles on the lean anchors base and pulls in amplifier-work-tracker and the same behavior. Use this to run the seed-reconcile recipe end-to-end against a target repo.

> Host requirement. A recipe resolves its helpers only from the session it > runs in, so running Converge's recipe needs either Converge's own > full-workspace setup or a host session already on the lean anchors base.

What differs between the two paths (honestly)

| | --app behavior | bundle use converge (root) | |---|---|---| | 4 agents · 5 skills · guard hook · awareness | ✅ | ✅ | | Session base + everyday tools | supplied by whatever bundle is already active | ✅ the lean anchors base, pulled in by bundle.md | | seed-reconcile recipe runnable | only if the host is on the anchors base (the recipe's read-only intake step is anchors:explorer) | ✅ | | work-tracker present (reconciler's work_* filing) | ✅ the behavior includes the work-tracker behavior, so reconciler gets work_* filing on this path too | ✅ pulled in by bundle.md | | Agents' "no delegate / no skills / no shell" rules | behavioral — agent body instructions + explicit tools: blocks (per-role structural spawn policy is an upstream feature request) | behavioral (same) |

Both paths give the four agents, five skills, guard hook, awareness context, and work-tracker filing. The root path additionally supplies the base — so for end-to-end recipe runs against a target repo, prefer bundle use converge. For lightweight composition onto a session that already has its own base, the --app behavior is the quick path. Neither path imposes any session-wide spawn: policy: a live probe (2026-09-02) showed a composed spawn.exclude_tools strips tools from every spawned sub-agent in every session — unacceptable collateral for a composable bundle, so it is deliberately absent everywhere.

What ships

• agents/protocol-authority.md — the carrier of the ratified rules. Ask it any

interpretive question ("does this conform? am I allowed?").

• agents/reconciler.md — the ratchet: it derives the conformance ledger

from a repo's locked contracts, re-checks it after every change, catches drift in both directions, and files what it finds. The one agent that writes; it never interrupts you synchronously.

• agents/negotiator.md — turns investigation evidence into decision-level

minutes: options, a recommendation, and the one decision you must make. Read-only; returns needs rather than re-routing.

• agents/proposal-drafter.md — authors a proposal beside a locked document

(the target line · the exact change · real evidence · what does not change · the place for your word) and stops. Never edits the locked file, never ratifies.

• skills/ —...