Skip to content

implementing: require planned probes before dependent implementation #36

Description

@teslamint

Problem

Cogvault's PDF plan required a real Poppler probe before U2 implementation. The probe ran during U5 instead.
Host-specific output behavior invalidated the initial implementation and required a late deviation.

Requested change

Make implementation-time probes enforceable at their named phase in planning and implementing workflows.

Acceptance criteria

  • Give each required probe an owning unit, command or procedure, expected observation, and evidence location.
  • Require its evidence before dependent implementation starts.
  • Record unavailable prerequisites as blocked or use a fallback already allowed by the approved plan.
  • Route contradictory observations through the existing plan-change process before dependent code changes.
  • Do not accept a later proof-phase run as evidence that the earlier gate ran on time.
  • Add workflow regression coverage for missing, failed, contradictory, and successful probe evidence.

Evidence and scope

Compound-loop owns the reusable phase gate. Preserve current approval and evidence mechanisms instead of adding a separate execution framework.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions