microsoft / microsoft/amplifier
ten-lane-highway skill + CLI: five measured gaps from a 19-cycle manager run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 261
- Avg merge
- 3h 28m
- Merged PRs (30d)
- 13
Description
Filed here because microsoft/amplifier-app-cli (where the built-in ten-lane-highway skill and amplifier tool invoke live) has issues disabled. Measured 2026-09-02/03 while a manager session drove ~24 real lanes through the skill (v1.0.0) and its scripts; earlier sessions on other repos corroborate.
- Refill is prose, not enforcement. Width decayed to 1/10 lanes for two hours and 0/10 for 32 minutes in a 23-day run while the watchdog announced it ten times; nothing restored it.
highway_status.shcomputes DEFICIT but nothing acts on it. Ask: the watchdog wake prompt should carry the deficit and the top ready items so a wake is a refill, not a report. - The dashboard claim is false. The skill says the todo tool is the live dashboard the user watches. Across three weeks the owner never referenced the todo board or HIGHWAY.md once; the only artifact they read was a plain-sentence return log. Ask: drop the claim; recommend an OWNER-RETURN-LOG.md.
- Interactive manager + headless watchdog wake double-launch. A watchdog wake (
amplifier run --resume) and the interactive session both ran the steady-state cycle within minutes and launched lanes for the same work item; only the work-tracker's atomic claim prevented duplicate work. Ask:launch_lane.shrefuses when the manifest already has a LIVE lane for the goal file or the tracker shows the item held. - Terminal-marker semantics. DONE on a branch whose tip equals its base is a false signal; running at deadline is stuck, never done; stuck outranks done. Ask: make the downgrade explicit in
verify_lane.sh's verdict. amplifier tool invokeemits notool:pre, so no hook (e.g. a file guard) can intercept a direct invocation. Ask: emit the same pre/post hook events as in-session tool calls, or document the bypass.
Note for the modes bundle: modes surface by bundle-root auto-discovery; a behavior's modes: include: block is currently informational.
Evidence: microsoft/amplifier-bundle-converge — docs/workflow/OWNER-RETURN-LOG.md, evaluations/turnkey/RESULT.md, modes/converge-manager.md.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with highway_status.sh, launch_lane.sh, and verify_lane.sh, then read the referenced OWNER-RETURN-LOG.md, RESULT.md, and converge-manager.md. Compare the watchdog and interactive amplifier run paths, and inspect amplifier tool invoke behavior against the requested hook semantics. Done means the five measured gaps have an implemented or documented resolution, including explicit terminal verdict behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell
- Domain
- cli, documentation, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100