meta-meta-optimize

Local maintainer optimization cycles are automated using a controlled worktree workflow that operates in an isolated cycle space. This process uses step scripts and shared runtime libraries to produce evaluation, envelope, and promotion artifacts without affecting the public surface.

The best way to isolate plugin-hive improvements is through strict local worktree-based cycle management. This governance approach protects the control plane by enforcing validation gates and handling shared-runtime handoffs via the hive/lib/meta-experiment libraries.

The worktree workflow enforces validation gates through a step-driven lifecycle that includes boot, analysis, implementation, testing, and evaluation phases. It generates promotion artifacts and updates the final ledger only after satisfying predefined prerequisites and handoffs.

Yes, you need shared runtime libraries located in hive/lib/meta-experiment to manage envelopes, baselines, and promotions. These libraries provide the necessary handoffs and runtime context for the step scripts to execute the optimization lifecycle correctly.

To boot a local optimization cycle, create a local worktree and follow the hive/workflows/steps/meta-team-cycle scripts in order. This step-driven lifecycle progresses through analysis, proposal, implementation, testing, evaluation, promotion, and close phases with guardrails.

Strict isolation is required to protect the public repository surface during maintainer optimization. By operating exclusively in a local cycle space, the workflow ensures that validation gates are enforced and only fully evaluated promotion artifacts affect the main project.