Skip to content

feat(idea-spark): quality gauntlet upgrades + run-state navigator + SKILL.md slimdown#12

Open
fistyee wants to merge 1 commit into
mainfrom
idea-spark-gauntlet-navigator
Open

feat(idea-spark): quality gauntlet upgrades + run-state navigator + SKILL.md slimdown#12
fistyee wants to merge 1 commit into
mainfrom
idea-spark-gauntlet-navigator

Conversation

@fistyee

@fistyee fistyee commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

One squashed commit upgrading the idea-spark skill on three fronts, validated on real runs.

Effectiveness

  • Dual-channel collision check (Phase 3.1). Signature channel: candidate's own signature_terms[] @ 10-month window (was 6). NEW alias channel: alias_terms[] — other communities' names for the same mechanism, produced from parametric knowledge at Phase 2.2 — @ 48-month window. This closes a lexical blind spot window-widening can't: a real run's "goal-image conditioned scorer" had 2023-24 near-ancestors published as "goal-conditioned success detectors", invisible to both the topical Phase 0 queries and the candidate-vocabulary signature terms. Hits carry a collision_channel tag; the audit is instructed not to age-discount alias-channel threats. Backstop: a new parametric_family_concern soft signal (family name + query vocabulary, never paper cites) flows into Phase 4 reviewer_concerns as a "run a scoop-check on X first" flag.
  • 5th audit check + the single audited kill-switch exception. falsification_structure_check audits the falsification paragraph's structure (minimal experiment / outcome metric + direction / ONE load-bearing variable / non-tautological negative control) — previously demanded at generation but never audited, and unrepairable due to the kill-switch. Now repairable through one gated door: a scope=falsification revision target applies via a dedicated rewrite_falsification op; the merger verifies audit authorization (--critique), stamps falsification_rewritten, and a bounded single-check re-audit must pass before Phase 4. kill_switch_integrity re-bases the byte-identity anchor at Phase 3.3 on that path; compute_budget stays sealed under every op and scope.
  • Bounded internal retry before abandon. Phase 2.1's sibling sampling is random, so a single abandon often reflects an unlucky draw. The run now archives the failed attempt under attempt_1/, marks .retry_used, and regenerates Phase 2.1+2.2 once with the failed audit + selection as negative constraints. The one-shot guarantee bars asking the user, not internal regeneration.

Efficiency

  • next subcommand (scripts/next_step.py): a read-only run-state navigator that inspects the run dir and prints exactly one next step (a verbatim bash command, or an LLM sub-agent spec with prompt/inputs/output paths). It encodes the full phase graph — fulltext gate, citation gate (run inline), abandon-retry and falsification re-audit branches, per-path Phase 4 flags — so the host loop degenerates to next → do it → next.
  • SKILL.md 69KB → 29KB (~17k → ~7k tokens): design rationale moved to references/design-notes.md, installation to references/setup.md; SKILL.md is now the operational runbook only.
  • Fewer round-trips: default Phase 0 flow passes --queries up front (skips the rc=10 intent sentinel); Phase 2.1+2.2 run in ONE isolated context writing both output files (both generation-side; the adversarial pairs 3.2/3.3 and 4.fill/4.1.5 stay separate); per-paper pattern tagging is delegated to a cheap/fast model; ≥600s timeout guidance documented for the retrieval steps.

Usability

  • add_user_ref subcommand: deterministic dedup-merge of title/ID user references into user_refs.json, avoiding a host Write-tool read-before-overwrite failure observed in a live run.

Testing

43 checks: merger authorization paths (unauthorized/authorized/double-rewrite/compute_budget refusal), kill-switch validator chains (advance / revise / audited-rewrite / tamper detection), stub dual-channel retrieval (windows, per-channel queries, cross-channel dedup + tagging), next state-machine walkthrough on a real completed run plus synthetic retry/re-audit/terminal branches, add_user_ref edge cases; all 5 validators regression-pass on a pre-change run.

🤖 Generated with Claude Code

…KILL.md slimdown

Effectiveness:
- Dual-channel collision (3.1): signature_terms @10mo (was 6mo) for
  contemporaneous scoops + NEW alias_terms @48mo — Phase 2.2 emits other
  communities' names for the same mechanism from parametric knowledge,
  closing the lexical blind spot windows can't (renamed ancestors, e.g.
  "goal-conditioned success detector" vs "goal-image conditioned scorer").
  Hits carry a collision_channel tag; audit told not to age-discount alias
  threats. Backstop: audit's parametric_family_concern soft signal (family
  name + query vocabulary, never paper cites) lifts into Phase 4
  reviewer_concerns as a "scoop-check X first" flag.
- 5th audit check falsification_structure_check + the single audited
  kill-switch exception: scope=falsification revision targets apply via a
  dedicated rewrite_falsification op — merger verifies audit authorization
  (--critique), stamps falsification_rewritten, requires a bounded
  single-check re-audit; kill_switch_integrity re-bases the byte-identity
  anchor at 3.3 on that path; compute_budget stays sealed.
- Bounded internal retry before abandon: archive attempt_1/, re-run Phase
  2.1+2.2 once with the failed audit as negative constraints (one-shot
  guarantee bars asking the user, not internal regeneration).

Efficiency:
- NEW `next` subcommand (scripts/next_step.py): read-only run-state
  navigator that prints exactly the next step (bash command or sub-agent
  spec), encoding the full phase graph incl. gates and retry/re-audit
  branches; host loop becomes next -> do -> next.
- SKILL.md 69KB -> 29KB: design rationale moved to references/
  design-notes.md, install steps to references/setup.md; operational
  runbook only.
- Default Phase 0 flow passes --queries up front (skips the rc=10 intent
  sentinel round-trip); Phase 2.1+2.2 run in ONE isolated context (both
  generation-side; adversarial pairs stay separate); pattern tagging
  delegated to a cheap/fast model; timeout guidance (>=600s) documented.

Usability:
- NEW add_user_ref subcommand: deterministic dedup-merge of title/ID user
  refs into user_refs.json — avoids the host Write-tool
  read-before-overwrite failure observed in a live run.

Tested: 43 checks across merger authorization paths, kill-switch validator
chains (advance/revise/rewrite/tamper), dual-channel stub retrieval, next
state-machine walkthrough on a real run dir + synthetic branches,
add_user_ref edge cases; validators regression-pass on a pre-change run.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@microsoft-github-policy-service

Copy link
Copy Markdown

@fistyee please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

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