Skip to content

[Bug]: Intermittent failure to lock spec, create either PLAN.MD or BLUEPRINT.MD #54

Open

Description

@TommyC81

Description

Spec lock and other status variable are not consistently updated in the project documentation. This leads to intermittent check failures when delegating; Spec is not locked, BLUEPRINT.MD does not exist, and/or PLAN.MD does not exist. Sometimes the agent recovers, sometimes it doesn't. Sometimes it attributes failure to using the worn executor agent, and re-launches with a lower level executor agent.

Steps to Reproduce

Use the framework v.0.2.7.

Expected Behavior

Artifacts are consistently updated, And specs locked. Ensuring steady progress.

In case of failure, verification of documentation is launched (including review of CHRONICLE) to determine whether a documentation failure exists), and the process self-recovers.

Actual Behavior

See above.

Environment

Windows 10
Opencode 1.2.6
Goopspec 0.2.7

Additional Context

A more robust tracking solution would be great - this is however an intermittent theme over different frameworks, they forget or miss project documentation updates and things go out of sync.

Activity

  1. TommyC81 commented on Feb 18, 2026

    @TommyC81
    Author

    I want to add this additional, and intermittent, failure to proceed as well (I don't use the memory system, so naturally don't expect it to be a problem...):

    I cannot proceed to code edits yet because the mandatory bootstrap failed at the required memory step.
    I ran goop_state, read SPEC.md and BLUEPRINT.md, loaded executor-core, and attempted memory initialization (goop_setup status/init/verify), but every memory_search/memory_note call still returns: “Memory system is not initialized. Run goop_setup first.”

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions