Skip to content

v0.13.0 — experimental campaigns, increment 1: format, extension rule, migration-campaign

Choose a tag to compare

@a-lottes a-lottes released this 30 Sep 17:24
· 180 commits to main since this release
a779faa

One loop ships here: campaign-core, increment 1 of 3, released through PR #67. Experimental.

Added

  • Campaigns, a second way of working next to the feature loop: one measurable goal that you approve, a budget, stop rules and a rollback path, run in iterations until the goal is reached or a rule halts it. You start one by hand, by naming the campaign file and the plugin folder in your prompt.
  • migration-campaign, the first kind: move code to its replacement in reversible slices, with a fresh, independent Parity Verifier checking each slice and a stop whenever a slice that was green turns red.
  • A format and a contract for new kinds (templates/campaign.md, campaigns/README.md, and a section in CONTRIBUTING.md): a new kind is one new file, never an edit to an agent or a skill.

Changed

  • README, project status and the repo layout describe campaigns and their limits. Every project without a .spark/campaigns/ folder sees identical behavior to before: no skill, agent, slash command or template contract changed.

Fixed

  • Nothing — this release adds capability, it does not correct a defect.

Honestly, what's not proven yet:

  • The need for campaigns is anticipated, not observed. Effectiveness is unmeasured. It was tested in scratch repositories, not on a real project, and only one kind exists.
  • Budgets and stop rules are followed by the agent, not enforced by Core (enforcement is the optional aspark-guard's concern).
  • Measured in QA: a kind with a missing key was reported as malformed in 13 of 19 sessions, so that check is best effort. The stop rule for a change spanning two slices was not triggered on a real diff; two other stop rules were tested only on planted history, and the budget rule on a prepared state. Nothing detects an edit to an already-approved campaign, and overlapping slice paths are not flagged.
  • The ten ceremonies have no campaign logic yet; the migration kind's standing rule for ordinary features is inert until a later increment adds routing. Increment 3 (project-local kinds) needs a constitution amendment first.

Full detail: docs/status.md.

Full trail: .spark/campaign-core/ · Full Changelog: v0.12.0...v0.13.0