Skip to content

Self-describing boot identify schema and FO contract ratchet for multi-workflow discovery - #551

Closed
clkao wants to merge 4 commits into
mainfrom
boot-identify-multi-workflow-llm-retry-friction
Closed

Self-describing boot identify schema and FO contract ratchet for multi-workflow discovery#551
clkao wants to merge 4 commits into
mainfrom
boot-identify-multi-workflow-llm-retry-friction

Conversation

@clkao

@clkao clkao commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Self-describing boot identify JSON schema and First Officer contract ratchet to eliminate LLM duplicate CLI retry loop on multi-workflow discovery.

What changed

  • Append schema, status: "complete", result: "multiple_workflows", terminal: true, workflow_count, and next_action: "select_workflow" to many-workflow --boot --identify --json output.
  • Ratchet «state.boot» effect/done-when and «interaction.boundary» greet line in first-officer-shared-core.md so multi-workflow boot discovery is terminal and greets with workflow selection.
  • Update command-reference.md to describe the multi-workflow multiple_workflows discovery record.
  • Add Go tests in boot_identify_test.go and fo_function_reference_invariant_test.go.

Evidence

  • go test ./... and go test ./... -race passed cleanly.
  • go test ./internal/status and go test ./internal/contractlint passed.

32

@clkao
clkao force-pushed the boot-identify-multi-workflow-llm-retry-friction branch from e359a1a to e588ca4 Compare July 22, 2026 08:49
@clkao

clkao commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator Author

Superseded by #584, which rebases the validated argv-ledger and self-describing boot candidate onto current main without force-pushing this historical branch.

@clkao clkao closed this Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant