[recipes] panning-for-gold: update to v3.0.0 - #481
Draft
jaredirish wants to merge 4 commits into
Draft
Conversation
Five months of production lessons folded into the merged v2.0.0 recipe, in the same voice and phase structure: - Stage 0 Open Brain pre-load (context dossier before extraction, capped query budget, graceful degradation when OB1 is sparse) - Deadline Audit (literal quote / inferred-from-anchor / extrapolation, stops the skill from inventing urgency a transcript never established) - Gap Detection (missed threads, unmentioned prior context, WAITING_FOR) - Hardened speaker consolidation: a zero-labels presence check, a diarizer-speaker-ceiling rule, and a mandatory biographical- attribution quiz for any claim that could get projected onto the wrong speaker - Advisory-only dedup on writeback (a guard that blocks is worse than one that lets a duplicate through) - companion_recipes now links both directions with flywheel-retrieval All additive on top of the merged version, nothing removed or contradicted. Scrubbed of personal names, client names, and file paths per the repo's existing checklist.
|
Hey @jaredirish — welcome to Open Brain Source! 👋 Thanks for submitting your first PR. The automated review will run shortly and check things like metadata, folder structure, and README completeness. If anything needs fixing, the review comment will tell you exactly what. Once the automated checks pass, a human admin will review for quality and clarity. Expect a response within a few days. If you have questions, check out CONTRIBUTING.md or open an issue. |
- Wrap fenced code blocks with blank lines (MD031, 3 spots) - Drop companion_recipes from metadata.json — not in this repo's .github/metadata.schema.json (additionalProperties: false), so it would fail schema validation - Replace the flywheel-retrieval markdown links (4 spots) with plain prose — that recipe was never actually merged upstream, only exists in a local unmerged checkout, so the relative links were dead
Code review caught this: the prior fix commit correctly removed dead links to a nonexistent "flywheel-retrieval" recipe (that name only ever existed in a local unmerged checkout), but overcorrected by degrading them to unlinked prose. recipes/live-retrieval/ is already merged upstream (PR NateBJones-Projects#128) and is exactly the companion this recipe was describing. Repointed all 4 references to it.
Small technical flowchart (126KB, well under the repo's 1MB binary limit) matching the process's own dot graph 1:1. Embedded right after "What It Does" so it's visible before the reader hits the step-by-step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the
panning-for-goldrecipe (merged previously) with five months of production lessons, folded into the existing v2.0.0 structure rather than a rewrite. All additive, nothing removed or contradicted.New in v3.0.0:
What Changed
recipes/panning-for-gold/panning-for-gold.skill.md2.0.0→3.0.0recipes/panning-for-gold/metadata.jsonrecipes/panning-for-gold/README.mdValidation
metadata.jsonvalidated against.github/metadata.schema.jsondirectly (not justjson.load) — the schema isadditionalProperties: false, which caught acompanion_recipesfield I'd initially added, pointed at aflywheel-retrievalrecipe that turns out was never actually merged upstream (only exists in my own local unmerged checkout). Removed the field, but the first fix over-corrected and degraded the corresponding links to unlinked prose instead of noticingrecipes/live-retrieval/(merged, PR [recipes] Live Retrieval: ambient Open Brain context surfacing #128) was the actual companion recipe under a different name. A follow-up commit repoints all 4 references to it.markdownlint-cli2against this repo's actual.github/.markdownlint.jsoncconfig (not the tool's defaults) — clean.upstream/mainto confirm this branch changes onlyrecipes/panning-for-gold/*.Testing
Each capability in this update (Stage 0 pre-load, deadline audit, gap detection, the speaker-consolidation edge cases, advisory-only dedup) is a rule the underlying skill has been running under in production on my own Open Brain instance for the past ~5 months — the Lessons Log inside
panning-for-gold.skill.mddocuments the specific production incident each rule traces back to, dated as it happened. This PR anonymizes and packages that live skill; it is not a from-scratch draft.Requires: an Open Brain MCP connection (
search_thoughts,capture_thought,list_thoughts) and an AI coding tool that supports skills/system prompts (Claude Code or similar). No paid services required beyond what the original v2.0.0 recipe already listed.Marked as draft, opening for maintainer review before marking ready.
Generated with Claude Code