docs(research): scope-correct 1B swarm-tools research-patch - #86
Merged
Conversation
Rewrite 2026-05-21-swarm-tools-research.md to the corrected 1B scope. The first version mis-scoped the input spec as an execution target (corrupted research prompt, caught at review 2026-05-21). The real 1B scope is the swarm/agent tools deep-dive + AGENT.MD / anti-SLOP discipline; the spec is a documentation example only. - Kept §3 (Prometheus/Atlas resolution, AIF-Handoff landscape, AI-SLOP boundary, AGENT.MD prior-art, ecosystem/billing) + §8 (triggers). - Dropped §4-§7 (spec defect analysis, approach comparison, execution recommendation + maintainer execution decision, spec-format amendments); §3 -> §8 numbering jump documented in a top note. - Reworded §1/§3.5/§9/§10/§11 to corrected scope; §9 records the scope correction as the dominant T15/T-ST-SCOPE self-application finding. - Superseded full text backed up gitignored; spec-execution working files quarantined to gitignored outputs/_out-of-1B-scope/ (+README), not deleted (real target-project value, deletion irreversible). Prior-art: skipped — research-patch (docs only), scope-correction of an existing patch, no new capability or dependency introduced.
artyhoo
added a commit
that referenced
this pull request
May 21, 2026
…h from chore/ssot branch (#92) * docs(research): fix fabricated citations stranded off main in 1B swarm-tools patch PR #86 landed 2026-05-21-swarm-tools-research.md in its uncorrected form. Two fabricated citations + one wrong DeepWiki URL + two over-precise claims were fixed afterwards on branch chore/ssot-karpathy-skills-ref (commits 1db3c46, 243bd59) and never reached main. This brings only those fixes: - §3.6 DeepWiki URL: oh-my-opencode → oh-my-openagent (typo'd repo slug) - §3.8 arXiv:2408.14007: "~1-in-5 demonstrably inaccurate" (not in paper) → "~13.5% below human-written quality (86.5% equivalent-or-superior)" - §3.9 + §10 GitHub 2,500-repo study: removed fabricated quantitative figures ("100–150-line top band", "10–15% improvement", "~4%") — source is qualitative; reworded to the study's actual qualitative finding - §3.6 handoff_push_plan mischaracterisation: accept_existing_plan event is the plan_ready trigger; handoff_push_plan is a complementary content update - C1 star-count, C2 Max-5x detail, C3 model-config URL: minor accuracy Leaving fabricated citations on main contradicts the project's own anti-fabrication discipline (ai-laziness-traps T3, citation-content gap). Content-only correction to an existing research-patch; no capability change. Prior-art: skipped — docs-only correction of fabricated citations in an existing research-patch, no new capability or dependency. * docs(research): land citation-content-vs-presence coverage-gap patch Records the methodology gap exposed by the swarm-tools fabricated-citation incident (preceding commit): principle 08 and the §1.7 backward-check verify a citation is *present* (URL/SSOT-ID attached), not that the cited source *contains* the claim. Form satisfiable while substance absent — #discipline-theatre at the citation-truthfulness layer, operational shape of ai-laziness-traps T3. Stranded on chore/ssot-karpathy-skills-ref (commit c0ce764); genuinely absent from main. Records incident 1/3 toward a promotion trigger; proposes a session-bound AI-agnostic verifier (no paid LLM in CI per no-paid-llm-in-ci). Append-only research-patch; proposes no maintainer-owned edit. Prior-art: skipped — docs-only research-patch recording a methodology gap, no new capability or dependency.
artyhoo
added a commit
that referenced
this pull request
May 29, 2026
docs(ssot): row #86 superset-sh/superset (REJECT/KEEP-NARROW/REFERENCE)
This was referenced May 30, 2026
Merged
artyhoo
added a commit
that referenced
this pull request
May 31, 2026
…brella done.md (#307) Closes the companion-reuse-deep-dive umbrella tail (PRs #248-251 already merged): - SSOT: 3 new append-only rows #88 (aif-handoff autoQueueMode LOGIC, ADOPT VOCABULARY + REFERENCE), #89 (omo session-plan-affinity, ADOPT VOCABULARY), #90 (Superpowers brainstorming scope-assessment, ADOPT VOCABULARY) — content copied from the merged R-phase patches; bare-ID column per principle-08 loader. #88 verdict-column normalized to clean `ADOPT VOCABULARY` with the faceted `+ REFERENCE` detail moved into the rationale column (principle-11 F2 convention, matches faceted rows #86/#87). - SSOT #67: additive note appended to «Trigger to revisit» only; REJECT verdict for the full Kanban runtime unchanged. - Resolved [next-available-slot] placeholders in the 3 source patches → #88/#89/#90. Devin (Sub-wave C) creates no row — its 2 descriptive placeholder mentions left as-is. - done.md written per CLAUDE.md umbrella-closure schema (Final PR #251). Verified: principle suite 153 pass / 4 skip; markdownlint clean. Prior-art: skipped — doc-only edit (SSOT register rows + umbrella done.md + research-patch placeholder resolution); no new capability, dependency, or code.
artyhoo
added a commit
that referenced
this pull request
May 31, 2026
…и версии) (#309) Продолжение хроники с места обрыва (v1/v3 ~22 мая, v2 до «большого переезда»): - Чужой меч в руке: мост к рантайму aif-handoff (#289/290/293/296/298/299) + superset REJECT/KEEP-NARROW/REFERENCE (SSOT #86) + N7-догфуд worktree (SSOT #65) - Распорядитель над распорядителями: /meta-orchestrator (#239-245) + inflight-check (#303) - Застава, что не выдержала испытания: recommendation-laziness — FP=84.2% → снято, оставлены H1 + ловушка T20 (#206/207/210/211/212/215) - Сторожа стерегут сторожей: Stryker-порча (#183), git.ts 0 тестов → 486 строк - v1: догоняющие главы (Wave 10, staging-ствол, аудит памяти, worktree dual-channel #297/300/301) со сносками [^6]-[^13] на первоисточники; v2: догоняющая Часть XIV (переезд+двор+память) Все falsifiable-утверждения сверены с git/research-patches/SSOT (T3-протокол). Примечание: ~468 строк pre-push верны для .husky/pre-push (bash, до миграции, история 468/476) — не путать с pre-push.ts (TS-порт, 447); строки 6/439 — историч. факт-чек, оставлены как есть. Prior-art: skipped — docs/narrative chronicle edit, no new capability
Merged
7 tasks
artyhoo
added a commit
that referenced
this pull request
May 31, 2026
…→ brainstorm-resolve → resume) (#315) Brainstorm output for the next phase on top of the merged dispatch (#312/#313): aif works autonomously (async batch, autoMode ON), parks only genuine forks; the maintainer resolves accumulated questions per-umbrella in one chat (work doesn't stop), answers flow back, aif finishes. Decisions in §7. Key design points: - 3 layers, max reuse: aif auto-work + fork-challenge triage (REUSE ask-question-reminder.sh discipline + aif auto-review); Telegram notify (REUSE, 0 code); 2 thin scripts cli/questions.ts + cli/answer.ts + a chat (BUILD). - Trust in aif = tunable dial, calibrated empirically; loop identical at any setting. - Auto-resolve of clear questions done by the in-chat resolution agent under the maintainer's fork-challenge hook (near-free), not aif's opaque review. - Superset-agnostic core (SSOT #86); Superset auto-open per-umbrella chat = opt-in fast-follow after a verify-first spike. no-paid-LLM clean. - 2 verify-first spikes: aif resume mechanism; fork-challenge hook in superset-chat. - Prerequisite: aif project clone must gitignore .ai-factory/ (branch-isolation). Prior-art: skipped — design-doc only (R/brainstorm deliverable), no code/dependency; BFR §3 search for "pull review-questions into a chat + push answers" goes in the I-phase kickoff.
7 tasks
artyhoo
added a commit
that referenced
this pull request
May 31, 2026
…rdicts for tracing-knowledge-lineages / when-stuck / preserving-productive-tensions + 5 SSOT rows (#92-#96) (#321) Single-session R-phase per .claude/orchestrator-prompts/companion-capability-survey/ kickoff.md + companion-capability-survey-meta-launch/kickoff.md. Surveys 11 Superpowers/Superset/aif-handoff capabilities not previously in SSOT against the /meta-orchestrator pipeline stages. Net additions: - docs/meta-factory/research-patches/2026-06-01-companion-capability-survey.md - prior-art-evaluations.md rows #92-#96 (4 ADOPT VOCABULARY + 1 REJECT) - #55 Last reviewed bumped to 2026-06-01 (writing-skills TDD-for-docs; verdict unchanged at ADAPT) - #86 Trigger to revisit sharpened (Superset Automations + MCP start_agent_session are a separate surface from the worktree-substrate #86 originally rejected) T-CCS-B fired: kickoff §2 claimed 'Superset cron — DeepWiki found NONE'; this survey verified Automations + RRule DO exist per docs.superset.sh/automations. Slack-agent precedent for Superset was the other §2 seed claim — NOT confirmed against source; dropped INCONCLUSIVE. No code changes. No new deps. Verdicts are recommendations per reviewer-discipline.md §2 — maintainer decides per-row adoption. Prior-art: skipped — research-patch + SSOT additive rows + Last-reviewed/Trigger sharpening on #55/#86. Not a capability commit per CLAUDE.md definition (no new explicit package.json dep; no ≥50 LOC under new packages/core/<dir>/; no ≥80 LOC under packages/). All edits are append-only or §3-step-1 in-place updates to prior-art-evaluations.md. Co-authored-by: Mastra Code (anthropic/claude-opus-4-7) <noreply@mastra.ai>
artyhoo
added a commit
that referenced
this pull request
May 31, 2026
…#99 multi-device (#324) DeepWiki re-survey (maintainer runs CC through Superset). Corrects the WebSearch-only false-negative in survey row #10 (Apache Superset != superset.sh): Slack-agent is real. Adds the operator-vs-shipped two-axis frame to #86 so REJECT is not misread as "operator may not use Superset". #99 = multi-device deviceId dispatch (REFERENCE, not built today). Survey patch §9 correction appended. Prior-art: skipped — append-only SSOT correction + research-patch correction note; no new capability, no dependency, no code.
artyhoo
added a commit
that referenced
this pull request
May 31, 2026
…ped) (#325) Distilled from the 2026-06-01 companion-capability survey + the Superset verdict-misread it surfaced (#86 REJECT read as "operator may not use"). Names the operator-axis (use companions maximally, ADOPT on real gap) vs shipped-axis (agnostic core + graceful degradation, install.sh --companions optional seam), the closes-a-gap filter, and the use-before-build priority. Maintainer-handoff edit (explicit "сделай лёгкий шаг" 2026-06-01). Prior-art: skipped — doc convention synthesis pointing to existing rules (BFR + dual-implementation §3); no new capability, no dependency, no code.
artyhoo
added a commit
that referenced
this pull request
Jun 1, 2026
…lt.md §1.1 (#326) Doc-authority correction: BFR is Authoritative-for "relationship to upstream tools + default verdict", which is the doctrine's scope; CLAUDE.md owns only the per-commit gate. PR #325 placement was a #contradicting-authority-claims slip. CLAUDE.md reduced to a one-line pointer (also removes always-on bloat); BFR §1.1 adds own-stack-first (criterion zero) + two axes + mechanical cost=capability-commit gate. §1.7: forward-check applied — doctrine relocated to its Authoritative-for home at .claude/rules/build-first-reuse-default.md:32 (doc-authority-hierarchy.md §4 #contradicting-authority-claims fix), CLAUDE.md reduced to pointer at CLAUDE.md:32 (removes always-on bloat per rule-enforcement-channel-selection); backward-check sweep — dual-implementation-discipline §3 still owns operator/shipped axis cross-ref at .claude/rules/build-first-reuse-default.md:40 (not duplicated), prior-art #86/#98/#99 cited unchanged. Prior-art: skipped — doc relocation to correct authoritative home + refinement; no new capability, no dependency, no code.
This was referenced Jun 1, 2026
artyhoo
added a commit
that referenced
this pull request
Jun 1, 2026
…з верстака (#336) * docs(meta-factory): project-history-book — главы за 31 мая–1 июня (все три версии) Три новые части в каждой из трёх версий, покрывают PR #310–#333: - Мост ожил (runtime-bridge): REST-починка E2E (#313), aif сам написал cli/questions.ts (#318), PARK-примитив (#332, SSOT #100). - Две оси спутника: операторская vs поставляемая, own-stack-first, поправка Superset SSOT #86 (#324→#326). - Ценз верстака: SubagentStart-инъекция устава (#330), F1 frontmatter dual-channel (#331), F2 CC Routines /fire (#333). v1 — техническая со сносками [^14-16]; v2/v3 — литпересказ без тех-деталей, v3 несёт storm-line. Эпилоги + футеры обновлены до 2026-06-01. * docs(book): PARK SSOT #100→#109 — догнать renumber из #337 (yield #100 → PR #328)
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.
Step 1B (swarm-tools-research) research-patch, corrected scope.
In scope: swarm/agent tools deep-dive (Prometheus/Atlas resolved =
code-yeongyu/oh-my-openagentagents; landscape vs AIF Handoff, complement not compete), AI-SLOP-vs-docstring + mechanical-detection boundary, evidence-based AGENT.MD template (docstring MODERATE, anti-SLOP positive-framed), ecosystem/Anthropic-infra/billing verification (Agent-SDK monthly credit effective 2026-06-15; GH-Actions@claude= metered API → stays DEFER under no-paid-llm-in-ci), Phase-10/Swarm-readiness triggers.Out of scope (corrected): the input
semantic-dedup-contractsspec is a documentation EXAMPLE only — no execution plan/approach/runtime analysis. Mis-scoped first draft removed; superseded text + target-project working files quarantined gitignored.Principle tests 10 (research-patch annotation) + 13 (s17) green. Single doc file; no capability artifact.
Prior-art: skipped — research-patch documenting prior-art findings, introduces no new capability artifact