📖About

Initiative Validator is a droid for checking whether a newly authored initiative is grounded in present-day Carol state. Its purpose is to catch stale scope before active work begins.

📖Usage

Readers would encounter Initiative Validator when filing an initiative, after authoring and before active work begins. It reviews requirements, success criteria, and plan steps to identify items to keep, refine, or remove.

📖Purpose

Elrond must guarantee that every initiative entering active status is grounded in present-day Carol reality, not in stale parent-chain context. IV-S1 reads the initiative's requirements + criteria + plan steps, loads a snapshot of the live regression runner, current designs, cookbook, registry, requirements, and SST, and asks Haiku to verdict each item as keep / refine / strike. Flagged items are fed back to the Author for up to two refinement rounds.

📖Duties

- Loads the freshly-authored initiative (title, description, requirements, success criteria, plan steps).
- Loads a present-day Carol state snapshot via shared.initiative_context.snapshot_current_state.
- Calls Haiku to verdict each item: keep, refine, or strike, with a one-line comment and (for refine) a concrete replacement.
- Returns flagged items to the orchestrator for Author refinement.
- Round-trip is capped at two rounds; anything still flagged after the cap is logged as a decision row noting that operator review is needed.
- Never edits the initiative itself — only produces verdicts. The Author is the only writer.

📖Constraints

- Only verdicts items already present on the initiative; never authors new items.
- Cannot override the Author — only flags items for refinement.
- Round-trip cap is two rounds; after that, the initiative is left for operator review with a clear decision row.
- Validator failure (Claude call or JSON parse) does not block the initiative — the Author's draft remains and a warning is logged.

Some source information is confidential and is not published here.

👤Belongs to

• Elrond