beo-explore

Purpose

Lock feature requirements.

Primary owned decision

Produce or repair locked CONTEXT.md requirements before design or implementation.

Ownership predicate

• Feature intake starts and CONTEXT.md is absent.
• Required requirements, constraints, compatibility, non-goals, or acceptance criteria are missing.
• New explicit user clarification contradicts locked requirements.
• A missing answer can materially change user-visible scope, acceptance criteria, non-goals, or constraints.
• The work is not merely a design-style choice or an implementation detail inside locked requirements; those belong to beo-plan.

Writable surfaces

• .beads/artifacts/<feature_slug>/CONTEXT.md while locking or repairing requirements.
• Invalidate current approval-record.json and clear approval/readiness mirrors when requirement edits make approval stale.
• Shared state/handoff fields allowed by beo-reference → skill-contract-common.md.