本文へ移動
cccskills
無料GitHub で公開

argumentative-lineage

Track the full Toulmin epistemic ancestry of every claim produced by a multi-agent swarm. Each agent output is tagged with an argument chain (claim / data / warrant / relationship) derived from SwarmTracer spans and LineageEdge records, so operators can zoom into any sub-claim and see precisely which agents asserted it, what triggered each assertion, and how contradictions propagated or were synthesised away. The SwarmTracer pattern — wrapping the SwarmAgentExecutor to capture spans, record messages, and build a lineage graph — is the concrete runtime substrate. Argumentative lineage lifts that graph into the Toulmin vocabulary so reasoning provenance is both machine-queryable and human-interpretable.

インストール方法を見る

含まれるファイル(13)

  • SKILL.md8.2 KB
  • affordance-scorecard.json841 B
  • agents/default-agent.md2.4 KB
  • agents/INDEX.md171 B
  • CHANGELOG.md315 B
  • diagrams/01_flowchart_decision-points.md2.2 KB
  • diagrams/INDEX.md203 B
  • examples/01_worked_example.md3.6 KB
  • examples/INDEX.md181 B
  • references/digest-with-zoom.md5.9 KB
  • references/INDEX.md381 B
  • references/swarm-tracer-implementation.md4.7 KB
  • references/toulmin-argument-structure.md5.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Argumentative Lineage

When to Use

  • You are running a WinDAGs swarm (or any multi-agent discourse topology) and need to audit why the final synthesis reached a particular conclusion — not just what it said.
  • An operator or reviewer asks "which agent first claimed X, and what triggered it?" — i.e., they need reasoning provenance, not just output.
  • You are building a swarm where conflicting agent claims must be traceable: legal analysis, security review, medical triage, policy evaluation, or any domain where "show your work" is a compliance or trust requirement.

NOT for:

  • Single-agent, single-turn outputs where there is no discourse graph to traverse.
  • Data pipeline lineage (column-to-column provenance) — use data-lineage-tracker instead.
  • Debugging swarm execution failures or hangs — use dag-execution-tracer or dag-failure-analyzer.

Core Concepts

SwarmSpan — One agent processing one triggering message. Recorded by SwarmTracer.wrapExecutor(). Carries: spanId, agentId, skillId, triggerMessageId, producedMessageIds, durationMs, promptHash, outputHash, discourse[], status. Every span is the unit of argumentative work.

LineageEdge — A directed edge fromMessageId → toMessageId through agentId and spanId, optionally labelled with a SwarmDiscourse relationship (supports, contradicts, qualifies, synthesises). The lineage graph is the raw substrate; the Toulmin layer annotates it with claim / data / warrant semantics.

Argument Chain — The output of SwarmTracer.getArgumentChain(messageId): an ordered sequence of { messageId, agent, act, relationship, thesis } tuples from the seed message to the target, extracted by walking traceLineage() and filtering for messages that carry discourse metadata. This is the machine-readable form of Toulmin lineage.

Toulmin Annotation Layer — Maps SwarmDiscourse fields onto Toulmin roles:

  • act: "assert" + relationship: "supports" → Data (grounds for an upstream claim)
  • act: "assert" + relationship: "none" on the seed → Claim (root thesis)
  • act: "question" / "challenge" → surfaces the Warrant (implicit bridge being probed)
  • act: "synthesise" → Backing or resolution of a qualifier / rebuttal branch
  • relationship: "contradicts" → Rebuttal candidate requiring resolution or qualification

Digest-with-Zoom — A two-level presentation pattern: (1) a one-line digest per agent output showing [agent] —[relationship]→ thesis for rapid scanning, and (2) a zoom view for any sub-claim that expands the full six-element Toulmin breakdown and traces lineage back to the seed. Enables operators to stay at altitude until a specific claim needs scrutiny.

Implementation Pattern

// 1. Instantiate tracer before swarm execution
const tracer = new SwarmTracer('my-swarm-name');

// 2. Wrap the agent executor — all spans captured automatically
const tracedExecutor = tracer.wrapExecutor(baseAgentExecutor);

// 3. Run the swarm, routing every published message through recordMessage()
const result = await executeSwarm(config, {
  agentExecutor: tracedExecutor,
  onMessage: (msg) => tracer.recordMessage(msg),
});

// 4. Finalize to get the complete SwarmTrace
const trace = tracer.finalize(result.convergenceReason, config.agents);

// 5. Annotate argument chain for any terminal message
function annotateArgumentChain(tracer, messageId) {
  const chain = tracer.getArgumentChain(messageId);
  // chain is Array<{ messageId, agent, act, relationship, thesis }>

  return chain.map((node, i) => {
    const toulminRole =
      i === 0                              ? 'Claim'
      : node.relationship === 'supports'   ? 'Data'
      : node.relationship === 'contradicts'? 'Rebuttal'
      : node.act === 'synthesise'          ? 'Backing/Resolution'
      : node.act === 'question'            ? 'Warrant (probed)'
      :                                      'Qualifier';

    return { ...node, toulminRole };
  });
}

// 6. Digest-with-zoom: render a scannable one-liner per agent output
function digestWithZoom(trace, targetMessageId) {
  const chain = annotateArgumentChain(tracer, targetMessageId);

  // DIGEST — one line per node
  const digest = chain.map(n =>
    `[${n.agent}] —${n.relationship}→ "${n.thesis}" (${n.toulminRole})`
  ).join('\n');

  // ZOOM — full Toulmin expansion of the target message
  const claim   = chain.find(n => n.toulminRole === 'Claim');
  const data    = chain.filter(n => n.toulminRole === 'Data');
  const warrant = chain.find(n => n.toulminRole === 'Warrant (probed)');
  const backing = chain.filter(n => n.toulminRole === 'Backing/Resolution');
  const rebuttal = chain.filter(n => n.toulminRole === 'Rebuttal');

  return { digest, zoom: { claim, data, warrant, backing, rebuttal } };
}

// 7. Contradiction audit — find unresolved rebuttals
function unresolvedContradictions(trace) {
  const contradictions = tracer.findContradictions();
  const synthesisIds = new Set(
    trace.messages
      .filter(m => m.discourse?.act === 'synthesise')
      .flatMap(m => tracer.impactAnalysis(m.id).map(d => d.id))
  );
  return contradictions.filter(c => !synthesisIds.has(c.message.id));
}

Key method signatures from swarm-tracer.ts:

  • new SwarmTracer(swarmName: string, traceId?: string)
  • tracer.wrapExecutor(executor: (agent, triggeringMessage, allMessages) => Promise<publications[]>)
  • tracer.recordMessage(message: SwarmMessage): void
  • tracer.finalize(convergenceReason: string, agents: SwarmAgent[]): SwarmTrace
  • tracer.traceLineage(messageId: string): SwarmMessage[] — ancestors in causal order, seed first
  • tracer.getArgumentChain(messageId: string): Array<{ messageId, agent, act, relationship, thesis }>
  • tracer.findContradictions(): Array<{ message, contradicts, thesis }>
  • tracer.impactAnalysis(messageId: string): SwarmMessage[] — downstream messages

SwarmTrace.stats carries contradictionCount, synthesisCount, maxLineageDepth, discourseRelationshipCounts — use these for a fast epistemic health summary before diving into individual chains.

Key References

  1. Toulmin, S. (1958). The Uses of Argument. Cambridge University Press. — Foundational six-element model (Claim / Data / Warrant / Backing / Qualifier / Rebuttal) that this skill projects onto swarm discourse graphs.

  2. workgroup-ai/packages/core/src/topologies/swarm-tracer.ts — Source implementation. SwarmTracer, SwarmSpan, LineageEdge, SwarmTrace, SwarmTraceStats interfaces and all query methods cited above live here. Read before extending.

  3. Dung, P.M. (1995). "On the Acceptability of Arguments and its Fundamental Role in Nonmonotonic Reasoning, Logic Programming and n-Person Games." Artificial Intelligence 77(2): 321–357. — Argumentation frameworks; relevant when modelling contradicts edges as attack relations and synthesise edges as defeat/reinstatement.

  4. windags/skills/toulmin-argument-analysis/SKILL.md — Companion skill for single-argument Toulmin analysis. Use argumentative-lineage when the argument spans multiple agent turns; use toulmin-argument-analysis when auditing a single agent's output in isolation.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Apply crisis decision-making research to agent routing, uncertainty triage, and coordination failure analysis in time-pressured systems. Use when diagnosing handoff failures, analytical paralysis, or expert judgment under incomplete information. NOT for routine coding, simple CRUD design, or static single-agent tasks with complete information.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Apply cognitive task analysis to expert work that depends on perceptual cues, branching judgment, and recurring monitoring loops. Use when decomposing expert capability into agent structure, simulation design, or validation interviews. NOT for ordinary step-by-step SOP capture or simple pipelines with no tacit cue layer.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

curiositech のスキルをすべて見る

このスキルの問題を報告する