Skip to main content

22 · Advantages, costs and evidence

The pack provides reusable instructions, canonical task records, scoped learning and independently configured collaborators. These mechanisms can reduce repeated setup and lost context. They do not guarantee better model output, safe parallel work or increasing capability on every iteration.

What the mechanisms provide​

  • Continuity: canonical KBD identity, journal revisions and derived waypoints let a later session recover recorded position. Recovery still needs the actual source, task owner and outstanding obligations.
  • Learning: the scoped writer keeps a durable queue and learning log; role delivery and Codex digest limits reduce accidental context spread. Queued, remotely accepted and later recalled lessons have different proof requirements.
  • Delivery ownership: signed immutable generations, target receipts and selected projections permit bounded verification and rollback. A valid manifest alone does not prove every harness loaded the new artifact.
  • Review separation: completed-phase review can use a distinct model and fresh context. The actual route must be evidenced; aliases, a fresh context or a sycophancy screen cannot prove that every critique is independent or correct.
  • Bounded execution: loop ceilings, explicit permissions and process budgets constrain selected workflows. Hitting a ceiling is a stopping outcome, not proof that the goal was achieved.

Costs and limits​

Native tools, optional services, model configuration and imported repositories each add maintenance work. Their versions and supported platforms are independent. A skills-only installation needs less infrastructure than a full native-service profile; the latter requires Bash 4 or later and component-specific platform support. Exec and liter API service templates currently have a narrower platform scope than their binaries.

The workflow also needs deliberate ownership. Isolated worktrees help separate edits but cannot resolve conflicting goals, ambiguous authority or an unauthorized cross-project message. Model budgets, service failures and durable recovery require operator decisions when the recorded contracts cannot resolve them.

Measure improvements against comparable completed deliveries and real installed paths. Prior incident anecdotes, source inspection, historical module totals and healthy endpoints are narrower evidence than current product acceptance. Use team models and budgets, service operations and local validation to assess the scope actually needed.

Previous: 21 · Contributing · Next: 23 · Glossary and sources