recall

To find previous solutions for a recurring drover error, you can search historical project ticket history using a keyword query. The recall process walks registered drover project boards and returns ranked matches containing verified Actual solution blocks.

An error fingerprint is a deterministic identifier derived from error structure used for exact debugging matches. You need it when a keyword query is insufficient and you require precise root cause recall across registered project boards.

Retrieve verified fixes by executing a recall-search with the --fingerprint flag using your deterministic error fingerprint. This searches project registries and returns ranked results with explicit verification labeling for Actual solution blocks.

Yes, you can include unverified projected solutions when searching drover project boards by opting in with the --include-projected flag. This surfaces both authoritative verified fixes and unverified Projected-only hypotheses in the ranked results.

Yes, cross-project solution recall works across all registered drover boards simultaneously by walking every project registry. It surfaces past matches with verified Actual solution blocks so you can apply proven fixes again.