← All decision guidesBundle-selection guide

Which SignalHarness Bundle Fits My Use Case?

Compare the nine canonical bundles by buyer profile, workflow coverage, included products, and when individual products are a better fit.

Short answer

Choose the narrowest bundle whose included products match the workflow you will actually implement. Use Agent Operator Core for prompt, output-quality, and safety-gate basics; the Wave 1 or Wave 2 stacks for infrastructure or trust and safety; the packaging, commerce, or multi-agent packs for those specialist workflows; and the broader business or complete-suite bundles only when their full membership is relevant.

Decision criteria

  • The workflow and buyer profile each bundle is designed to cover
  • Which included products the buyer will actually implement
  • Whether a specialist bundle or individual product is sufficient
  • Canonical one-time price and exact membership
Supported comparison and selection points
Decision dimensionDecision guidance
Core operator workflowAgent Operator Core covers prompt harnesses, output review, and permission/safety gates.
Specialist infrastructureWave 1 covers context, memory, permissions, workflow, and recovery; Wave 2 covers evaluation, defensive handling, evidence, safety cases, and incident response.
Specialist distribution and operationsPackaging Studio, Agent Commerce Stack, and Multi-Agent Operations Pack target different downstream workflows.
Broad coverageBusiness OS Bundle, Complete Vault, and Complete Agent-Native Suite fit buyers who genuinely need their wider exact membership.

Relevant products

  • Prompt Harness Builder KitConverts loose prompts into reusable 'harnesses' with defined inputs, output contracts, quality gates, retry logic, and scoring rubrics; includes 10 finished harnesses and blank/worked templates.
  • AI Output Quality-Control Scorecard SystemA quality-control system for AI output: scorecards by content type, a 0-5 rubric library, pass/fail gate definitions, review workflow SOPs, and agent self-review instructions.
  • Agent Memory Governance KitA written governance system for what agents may remember: memory classification, a binding never-store list, retention schedules, and audit scorecards.
  • Agent Evaluation Harness SuiteA written evaluation system for agents: task-suite/run-record/gate-config JSON schemas, six anchored rubric families, written regression gates, and worked evaluations.
  • Agent Skill Packaging KitA written standard for packaging agent skills: manifest standard with reference JSON, instruction file standard, trigger specs, test packs, and packaging checklists.
  • Agent Marketplace Listing KitA written listing standard for products sold to both humans AND buying agents: dual-reader listing structure, agent-readable listing schema with a self-applied reference instance, and claim-evidence maps.
  • Multi-Agent Role Charter KitA written role system for multi-agent setups: role-authority contracts, authority maps with one-owner-per-decision arithmetic, escalation matrices, and worked charters.
  • Digital Product Factory OSA stage-gated pipeline for building digital products with AI assistance: idea validation worksheet, product spec harness, build SOPs, QA gates, launch checklist, and pricing worksheet.

Relevant bundles

  • Agent Operator Core BundleAgent operators, Claude Code users, MCP builders, automation builders.
  • Business OS BundleBusiness owners and creators who want full systems, not single tools.
  • Complete VaultOperators building a full agent-assisted business stack.
  • Wave 1 Agent Infrastructure StackAgent operators, agent-platform engineers, and orchestrator agents adopting the full Wave 1 infrastructure layer.
  • Wave 2 Agent Trust & Safety StackAgent operators, safety leads, and agent-platform engineers adopting the full Wave 2 trust-and-safety layer; orchestrator agents assembling evidence-backed deployment cases.
  • Agent Packaging StudioBuilders and builder agents packaging capabilities into installable skills, well-described MCP servers, and listing-ready assistants.
  • Agent Commerce StackSellers, marketplace operators, and buying-agent operators adopting the full agent-commerce grammar.
  • Multi-Agent Operations PackOperators and architects running two or more agents that share artifacts, boundaries, and bad days.
  • Complete Agent-Native SuiteOperators building the complete agent-native operation; existing bundles remain valid - this supersedes nothing.

Compatibility and limitations

These products are document, template, schema, policy, or checklist systems used with the buyer's own tools. Review each canonical product page and the compatibility guide before choosing.

  • A bundle does not add capabilities, integrations, services, or guarantees beyond its included canonical products.
  • Individual products are a better fit when only one or two narrow systems are needed.