measuring how much intent survives to ship
ZeroVector is an Amplifier bundle that treats the road from intent to artifact as a chain of handoffs — and reframes the whole problem as translation loss, not craftsmanship.
So the first job is to define fidelity precisely enough to measure it.
The overall score is the arithmetic mean of five lens scores —
sum(lens_scores) / len(lens_scores) — and the bundle
ships instrumented, not aspirational.
If it’s this concrete, what exactly was broken before?
Each step reinterprets the last — designer reads PM, engineer reads designer. The linear pipeline had no way to measure how much of the original intent survived.
The problem isn’t any one stage — it’s the chain itself.
“Every handoff loses information. The final artifact is a degraded version of the original intent.”
ZeroVector replaces the linear discover→specify→build→review→ship pipeline with a single convergence engine driven by a crew of five agents.
Collapsing the chain is what makes measured fidelity possible — here’s how the loop runs.
Five lenses score the artifact; the loop finds the lowest-scoring lens and sends it to that lens’s dedicated agent to close the gap.
Targeting the weakest lens is only half the loop — when does it stop?
A while-loop continues while fidelity_score < target_fidelity
and breaks when it clears the target — a stopping condition calibrated
per domain so “done” is provable, not declared.
A measured stopping point is what turns fidelity into a dial.
Each lens score is clamped to [0,1]; the artifact reports
CONVERGED only when overall fidelity reaches the target —
otherwise NEEDS_WORK. “Is the intent intact?” now has a number.
Optimizing translation loss — not just quality — is the whole point.
If every handoff degrades intent, the win isn’t polishing each stage — it’s making the degradation visible and driving it toward zero.
Data as of: HEAD commit 2812b2c, dated 2026-07-01 (ZeroVector v0.3.0).
Repository: michaeljabbour/amplifier-bundle-zerovector (cloned to /tmp/zerovector-src). Thin Amplifier bundle depending on github.com/microsoft/amplifier-foundation@main; credits Zero-Vector Design by Erika Flowers.
Feature status: Active — v0.3.0 fidelity convergence architecture rewrite.
Commands run:
grep -rn 'def test_' tests/ --include='*.py' | wc -l → 626; find tests/ -name 'test_*.py' | wc -l → 17.grep -c 'def test_' → 148 in tests/modes/test_crew_domain_modes.py.sed -n '30,36p;85p' modules/tool-fidelity-state/.../__init__.py.sed -n '24p' module + fidelity-framework.md domain table (lines 71–78) + recipe line 32.sed -n '152,154p' recipes/fidelity-convergence.yaml (while / max 8 / break_when).sed -n '13,23p' context/zerovector-principles.md; sed -n '13p;29,32p' skills/fidelity-framework.md.ls agents/ modes/ recipes/ → 5 agents, 6 modes, 6 recipes.git log --format='%an <%ae>' | sort | uniq -c → 64 commits, Michael J. Jabbour.Gaps: README self-describes “two Python modules” while three module dirs exist on disk (tool-fidelity-state 198, hooks-fidelity-reporter 388, hooks-crew-gate 186 LOC) — an internal repo doc inconsistency, reported not resolved. Not every mode/recipe file’s full contents were read.
Primary contributor: Michael J. Jabbour — 64 of 64 commits (100%).