--- source_hash: 57e6f7a78cea4cd8494ec66fc3c9083abb6cdc8715ec5660b64523ccd38c4c79 post: /posts/workflows/agentic-progressive-improvement --- # Context Pack: Agentic Progressive Improvement Reference for the August 2026 release account, version 0.1.0-rc.1. A bounded mid-session snag becomes an improve unit while the main seat continues the actual task. This is a written protocol plus optional local ledger tooling, not a complete nested runtime, unattended improvement loop, principle-capture replacement or design swarm. ## Verbatim excerpts > Uncertainty raises the tier. It is not a reason to choose the easier permission path. > The unit must retain an undo action that actually fits the change and its repository state. > Dispatch is preferred when the host supports it. Serial execution is the portable fallback. ## Roles, caps and return Orchestration seat keeps the real task, classifies risk, records a local ledger and assigns work. Improve agent runs the internal brainstorm and dispatches mechanical builders; it is not operator-facing for T0–T2. An optional auditor checks risk/scrub. Return a digest and a skim when visibility is required. At most 3 concurrent improve units per session; at most 2 retries for the same error class, then needs-operator. Improve agent uses the orchestration seat's model. Mechanical local builders are allowed only with headroom. Do not switch cloud vendors just to save cost. Exact public skim form: ↑ improve: · T# · · undo: Green T0 may stay silent only with ledger and undo; some T1 work can also return without an announcement within its explicit limits. Do not merge T0 and T1 into one unrestricted silent-hygiene tier. ## Every tier and floor matters - T0 session hygiene: local only, silent when green, ledger and undo story. - T1 task unblock: branch work, optional skim, auto-merge ONLY within strict explicit caps. - T2 tool inheritance: batch at a pause, human merge. - T3 method/rules: draft until approved, ask before promotion. - T4 red zone: ask, prepare only, no automatic mutation. Unsure means raise a tier. Seat rules, methodology and durable process are at least T3. Secrets, remotes, disk cleanup, sudo and public publication are T4. A second occurrence of the same pain class may promote T1→T2; a first one-off generally stays a T1 unblock rather than becoming a permanent new tool. Denylist categories: mass disk wipes, protected remotes, secret dumps, sudo without approval, public publication without scrub, push main, irreversible unattended actions. Scrub does not grant publication authority. T4 still prepares and asks. ## Run one unit and report honestly Classify; append building in the ledger; brief the improve agent with tier/snag/paths/denylist/inherited model; continue the real task; verify returned claims on disk when shipping matters, update ledger and show the skim when needed. T3/T4 return needs-operator with paths and never promote silently. Modes: dispatch for separate seats; serial_fallback for one seat following the stages without peer-review claims; partial names which legs used each route. The retained diagram's serial-fake wording means explicitly labelled serial fallback, not fabricated independence. The method does not waive host permissions. ## Optional CLI and distribution The documented api-improve commands are classify, append, brief, skim, tail and trail. Installation example: pip install -e ".[dev]" from the release checkout. Ledger default is XDG state under api-improve, overridden by API_IMPROVE_LEDGER. Trail is local or none. The RC account required no forge credentials. These are historical instructions; package/CLI behaviour has not been executed or independently verified here. The original account described an open MIT method on GitLab but supplied no concrete repository URL. Do not invent a current URL. The member kit is convenience packaging, not exclusive method IP: first-run pack, seat snippets, examples, scrubbed skill/prompts and tier card. MemberDownload slug agentic-progressive-improvement, version 0.1.0-rc.1; the version is stated in the body and registry, not frontmatter. A registry entry alone does not prove downloadable package availability. ## Method boundaries and retained teaching Solo brainstorm ends in a spec; brainstorming swarm tests a design and stops at a spec; build swarm implements an agreed design; this method handles a snag during ongoing work. Operator taste decisions, durable principle capture and unsettled designs belong elsewhere. All seven original fenced blocks and six illustration paths are retained, under /images/deep-dives/agentic-progressive-improvement/: g1-role-graph.jpg, g5-caps-chip.svg, g3-skim-card.svg, g2-tier-ladder.svg, g4-triangle.jpg, g6-sticky.jpg. They illustrate roles, caps, skim, tiers, method choice and the convenience-kit note. ## Retained configuration example ```md Outcome: One bounded improve unit with tier, ledger row, and undo story. Constraints: Denylist holds. T0 to T2 nested only. T3 ask before promote. T4 prepare only. Evidence: Ledger entry, skim line when required, green checks for T0/T1. Escalate: Stop when authority, judgment, or irreversible mutation is required. ```