{"version":"1.0.0-rc1","updated_at":"2026-07-10","public":true,"gated":false,"checkout_enabled":true,"products_purchasable":true,"agent_pay_status":"live","products_x402_enabled":90,"products_x402_disabled":0,"vault_x402_enabled":true,"purpose":"Reduce refund risk by making every product harder to misunderstand: exact deliverables, explicit non-inclusions, honest compatibility, fit/not-fit guidance, and pre-purchase self-checks for both humans and AI agents.","support_email":"support@signalharness.ai","suite_defaults":{"what_you_buy":"A structured set of plain-text Markdown and JSON files you download and keep. You use them with your own AI tools (Claude, ChatGPT, MCP-based agents, or any LLM assistant) or entirely manually. This is a document system - not software, not an app, not a plugin, not a hosted service.","formats":"Markdown (.md) and JSON (.json), plain text, tool-agnostic, human- and agent-readable.","delivery":"Digital file delivery after purchase through Polar benefits. No physical goods.","not_included":["No software, app, executable, or code that runs by itself","No hosted service, account, login, or cloud dashboard","No live integrations: Zapier/Make items are written blueprint descriptions, not built Zaps or scenarios","No API access, API keys, credentials, or third-party subscriptions","No custom setup, done-for-you implementation, or human consulting hours","No AI model access - you bring your own Claude/ChatGPT/LLM subscription or local model","No payment processing of any kind inside the products","No guaranteed business results: no sales, income, traffic, ranking, or performance promises - outcomes depend on your execution and market"],"setup_required":"Self-serve: download, unzip into a new folder, read QUICK-START.md, and supply your own business/agent facts where the templates ask for them. Quick starts are designed for about 10 minutes; full implementation is typically 1-2 hours of your own working time.","required_user_inputs":"Your own facts: business details, agent stack details, or content/product specifics, depending on the kit. Templates contain clearly-marked input slots; nothing fills them for you.","human_compatibility":"Written for operators who can read instructions and edit plain-text files. No programming required for the core paths; advanced integration paths assume comfort with your own agent tooling.","agent_compatibility":"Every product ships machine-readable metadata, agent instructions, and JSON schemas an AI agent can parse, compare, and apply. Agents can inspect the catalog free at /agent/ before any purchase.","tool_compatibility_reality":"Names in compatible_systems mean the files WORK WITH those tools - you can paste, attach, or reference them there. It does not mean prebuilt integrations: nothing auto-installs into Claude, ChatGPT, Zapier, Make, Notion, or GitHub.","buyer_expectations":["Expect structured documents, checklists, schemas, and worked examples - not a turnkey machine","Expect to spend your own working time applying them; the products organize and de-risk that work, they do not remove it","Expect plain-text quality: no video course, no community, no live workshops unless a product explicitly lists them","Expect honest scope: every product page lists what is included; if it is not listed, it is not included"],"success_depends_on":["You actually applying the SOPs/templates to your real work","The quality of the inputs and facts you provide","Your own AI tool access and its capabilities","Consistency over weeks, not a one-time read"],"support_scope":{"contact":"support@signalharness.ai","included":["Delivery/download problems (highest priority)","Which product/tier fits my situation questions","Install, integration, and rollback questions","License questions","Refund requests under the 14-day policy"],"not_included":["Logging into your accounts or systems","Custom implementation or consulting","Debugging your unrelated tooling","Business strategy engagements"],"first_step":"Contact support BEFORE requesting a refund - delivery, file, and fit problems are usually fixable within one business day."},"license_scope":"Single-Operator license by default: everything you MAKE with the products is 100% yours (commercial use included, no attribution); the product FILES themselves may not be resold, redistributed, shared publicly, or repackaged into a competing product. Full terms: docs/license.md and licenses.json.","update_scope":"A one-time purchase includes the product version bought plus fixes to that version. SignalHarness Vault monthly or annual recurring access provides the current Vault catalog while the subscription remains active.","pre_purchase_questions":["Am I comfortable working in plain-text Markdown/JSON files?","Do I have my own AI assistant access (Claude, ChatGPT, or similar) or am I happy to use the manual paths?","Do I have 1-2 hours to implement, not just read?","Have I read the included/not-included lists for this exact product?","Do I understand this is a document system, not software or a service?"],"refund_policy_pointer":"/refund-policy/ - published policy; requests follow the applicable Polar process and approval is not guaranteed."},"products":{"agent-context-engineering-os":{"kind":"document operating system (methods, budgets, policies, audits)","human_summary":"A written system for deciding what goes into an AI agent's context window: selection framework, token budgets, compaction policies, and audit worksheets.","included_reality":"Context-Budgets/, Compaction-Policies/, Context-Audits/, Retrieval-Rules/ folders with JSON reference instances plus the standard instruction/integration/upgrade architecture.","best_for":["Engineers and operators running long-horizon or RAG-backed agents","Teams whose agents degrade as context grows","Orchestrator agents applying written context policy"],"not_for":["Buyers expecting software that manages context automatically","Casual chat users without an agent stack","Anyone wanting a hosted memory service"],"limitations":["'OS' means a document operating system - files and methods, not running software","You must apply budgets/policies inside your own agent framework","No vector database or retrieval infrastructure is included"],"refund_risk_flags":["name_implies_software","requires_own_agent_stack"],"pre_purchase_questions":["Do I have an agent or RAG stack where I can apply written context policies?"]},"agent-tool-use-permission-matrix":{"kind":"policy kit (risk ladder, matrices, machine-readable contracts)","human_summary":"A written permission system for agent tool use: risk tiers, deny-by-default matrices, allowlist/blocklist policies, and an audit-log schema.","included_reality":"Permission-Matrices/, Risk-Tiers/, Worked-Matrices/ folders with a machine-readable matrix contract and audit schema plus the standard architecture.","best_for":["Operators giving agents access to real tools","Safety leads who need written, reviewable permission policy","Agents enforcing a documented matrix"],"not_for":["Buyers expecting runtime enforcement software","Stacks with no tool-using agents","Anyone wanting an off switch they never have to configure"],"limitations":["Enforcement happens in YOUR runtime - this kit defines the policy, your stack applies it","No code hooks or middleware included"],"refund_risk_flags":["policy_not_enforcement_software","requires_own_agent_stack"],"pre_purchase_questions":["Can my agent framework actually honor an allow/deny matrix I define?"]},"agent-memory-governance-kit":{"kind":"governance kit (classification model, retention schedules, scorecard)","human_summary":"A written governance system for what agents may remember: memory classification, a binding never-store list, retention schedules, and audit scorecards.","included_reality":"Memory-Policies/, Retention-Schedules/, Memory-Audits/ folders with the MCM-4 method and MHS-100 scorecard plus the standard architecture.","best_for":["Teams running agents with persistent memory","Operators who need a defensible written memory policy","Reviewer agents auditing memory stores"],"not_for":["Buyers expecting software that deletes memories automatically","Agents with no persistence layer","Anyone seeking legal compliance certification"],"limitations":["Policies govern; your platform executes - retention/deletion is applied by your stack","Not legal advice and not a compliance certification"],"refund_risk_flags":["policy_not_enforcement_software","not_legal_advice"],"pre_purchase_questions":["Does my agent actually persist memory that needs governing?"]},"agent-error-recovery-playbook":{"kind":"playbook (failure taxonomy, recovery ladders, escalation rules)","human_summary":"A written failure-recovery system for multi-step agents: 13-class failure taxonomy with detection signatures, decision tree, repair paths, and safe retry policy.","included_reality":"Failure-Catalog/, Recovery-Ladders/, Escalation-Rules/ folders in Markdown + JSON plus the standard architecture.","best_for":["Operators of multi-step or unattended agents","Engineers formalizing retry/escalation behavior","Orchestrators that follow written recovery ladders"],"not_for":["Buyers expecting automatic self-healing software","Single-prompt casual use","Teams unwilling to wire escalation to a human"],"limitations":["Detection signatures are written patterns your stack must check - nothing monitors your agents by itself","Retry logic must be implemented in your workflow tool or agent code"],"refund_risk_flags":["playbook_not_monitoring_software","requires_own_agent_stack"],"pre_purchase_questions":["Where in my stack would written recovery ladders actually get applied?"]},"agentic-workflow-compiler":{"kind":"method kit (workflow spec schema, compilation passes, validation checklists)","human_summary":"A written method for turning fuzzy business workflows into precise, agent-executable specs: six compilation passes, a workflow-spec JSON schema, and machine-checkable validation checklists.","included_reality":"Workflow-Specs/, Compilation-Rules/, Worked-Compilations/ folders with a complete compiled reference instance plus the standard architecture.","best_for":["Operations leads specifying workflows for agents","Agent builders who need unambiguous specs","Teams translating SOPs into agent tasks"],"not_for":["Buyers expecting a software compiler that emits running code","Teams with no workflows to formalize","Anyone expecting drag-and-drop automation building"],"limitations":["'Compiler' names the six-pass writing METHOD - it is documents and schemas, not a code tool","Execution still happens in your agent framework or workflow tool"],"refund_risk_flags":["name_implies_software","method_not_executable"],"pre_purchase_questions":["Am I ready to write specs by hand using a rigorous method, rather than generate them with a tool?"]},"prompt-harness-builder-kit":{"kind":"template + prompt-engineering kit (10 finished harnesses, templates, gates, rubrics)","human_summary":"Converts 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.","included_reality":"Prompt-Harnesses/ (10), Templates/, Quality-Gates/, Retry-Logic/, Scoring-Rubrics/, Failure-Examples/, Before-After-Examples/, 14-document Integrations/ pack, 5 Upgrade-Modules/, plus samples and launch copy.","best_for":["Anyone whose AI output quality is inconsistent","Operators letting agents run prompts semi-unattended with QA","Claude/ChatGPT power users who reuse prompts"],"not_for":["Buyers wanting one-click prompt magic with zero structure","Users unwilling to define inputs and pass/fail criteria","Teams expecting built Zapier automations (blueprints are descriptions only)"],"limitations":["Harness quality gates are applied by you or your AI in-session - nothing scores outputs autonomously","The Zapier/Make folders are blueprint descriptions to build from, not importable automations"],"refund_risk_flags":["blueprints_not_built_automations"],"pre_purchase_questions":["Am I willing to define required inputs and a pass/fail gate for my important prompts?"]},"ai-agent-permission-safety-gate-kit":{"kind":"safety kit (permission tiers, approval checkpoints, rollback playbooks)","human_summary":"A written safety system for agents acting on your behalf: permission tiers, human-approval checkpoint patterns, risk classification, do-not-touch boundaries, and rollback playbooks.","included_reality":"Safety-Gates/ (5), Checklists/, Rollback/, incident log templates, and agent instruction blocks plus the standard architecture.","best_for":["Operators running agents with real-world access","Small agencies deploying agents for clients","Anyone formalizing when an agent must stop and ask"],"not_for":["Buyers expecting sandboxing or enforcement software","Pure-chat users whose AI never acts on anything","Anyone treating written gates as a substitute for platform security"],"limitations":["Gates work when you and your agents follow them - this kit cannot technically prevent an agent from acting","Platform-level security remains your platform's job"],"refund_risk_flags":["policy_not_enforcement_software"],"pre_purchase_questions":["Will I actually configure my agents to honor written approval checkpoints?"]},"ai-output-quality-control-scorecard-system":{"kind":"scorecard system (rubrics, gates, review SOPs)","human_summary":"A 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.","included_reality":"Scorecards/ (7), SOPs/, rubric library, escalation rules, before/after examples plus the standard architecture.","best_for":["Agencies and teams reviewing AI deliverables","Operators adding a QA step before anything ships","Agents running self-review against anchored rubrics"],"not_for":["Buyers expecting automated grading software","Anyone unwilling to define what 'good' means for their work","Teams looking for a hosted review dashboard"],"limitations":["Scoring is done by you or your AI applying the rubrics - no autonomous scoring engine is included","'System' means an organized document system, not an application"],"refund_risk_flags":["name_implies_software","scoring_requires_your_ai_or_you"],"pre_purchase_questions":["Do I produce enough AI output that a written QA gate would pay for itself?"]},"digital-product-factory-os":{"kind":"document operating system (stage-gated pipeline: validate/spec/build/QA/launch/iterate)","human_summary":"A 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.","included_reality":"SOPs/ (4), Templates/ (6), Checklists/, worksheets and QA gates plus the standard architecture.","best_for":["Digital creators shipping products with AI help","Solo builders who need a kill/proceed discipline","Agencies productizing services"],"not_for":["Buyers expecting products to be generated for them","Anyone seeking income promises - none are made","People who will not kill weak ideas at the gates"],"limitations":["The pipeline structures YOUR product work; it does not produce or sell products by itself","Business results depend on your idea, execution, and market - explicitly not guaranteed"],"refund_risk_flags":["name_implies_software","outcome_depends_on_buyer_execution"],"pre_purchase_questions":["Am I prepared to validate and possibly kill my idea at stage gates before building?"]},"marketplace-listing-conversion-kit":{"kind":"template kit (listing structures, title/description harnesses, QA scorecard)","human_summary":"Templates and harnesses for writing better marketplace listings: structure templates by marketplace type, title/description harnesses, image/preview checklist, listing QA scorecard, and revision workflow.","included_reality":"Templates/ (6), Checklists/ (3), Prompts/, Examples/, listing QA scorecard plus the standard architecture.","best_for":["Digital product and template sellers","Small e-commerce operators improving listings","Agents drafting listings for human review"],"not_for":["Buyers expecting ranking or sales promises - none are made","Anyone expecting marketplace API integrations or auto-posting","Physical-retail-only sellers (examples skew digital)"],"limitations":["Conversion depends on your product, pricing, and marketplace - the kit improves the listing craft only","No marketplace accounts, APIs, or posting automation included"],"refund_risk_flags":["outcome_depends_on_buyer_execution","no_platform_integration"],"pre_purchase_questions":["Do I have live or planned listings I can rewrite with these templates this week?"]},"creator-content-factory-ai-agent-os":{"kind":"document operating system (content pipeline SOPs, harnesses, repurposing matrix)","human_summary":"A content production system for creators working with AI: pipeline SOPs, idea-to-post harnesses, repurposing matrix, platform-format templates, QA scorecards, and a weekly cadence planner.","included_reality":"SOPs/ (3), Templates/ (3), Prompts/ (4), Checklists/, repurposing matrix and cadence planner plus the standard architecture.","best_for":["Content creators and newsletter writers using AI","Solo brands formalizing a weekly cadence","Agents drafting content inside a defined pipeline"],"not_for":["Buyers expecting audience-growth promises - none are made","Anyone expecting auto-posting or scheduler integrations","Creators who want fully hands-off content"],"limitations":["Publishing, scheduling, and platform accounts remain yours - no integrations included","'OS' means an organized document system, not an app"],"refund_risk_flags":["name_implies_software","outcome_depends_on_buyer_execution","no_platform_integration"],"pre_purchase_questions":["Will I commit to a weekly cadence the planner can structure?"]},"local-business-ai-marketing-os":{"kind":"document operating system (weekly cadence SOPs, harnesses, response templates)","human_summary":"A marketing operating rhythm for local businesses using AI: weekly cadence SOPs, content harnesses for local posts/offers/replies, review-request workflows, reputation-response templates, and a monthly planning worksheet.","included_reality":"SOPs/ (3), Prompts/ (6), Templates/ (3), Checklists/ (2), Examples/ plus the standard architecture.","best_for":["Local service business owners doing their own marketing with AI","Solo operators and small agencies serving local clients","Beginners - this is the most beginner-friendly kit"],"not_for":["Buyers expecting customer or revenue promises - none are made","Anyone expecting ad-platform integrations or auto-posting","Businesses unwilling to post consistently"],"limitations":["Marketing results depend on your offer, consistency, and market - explicitly not guaranteed","No Google/Meta/review-platform integrations; you post via your own accounts"],"refund_risk_flags":["name_implies_software","outcome_depends_on_buyer_execution","no_platform_integration"],"pre_purchase_questions":["Can I commit roughly 2 hours a week to run the cadence?"]},"agent-evaluation-harness-suite":{"kind":"evaluation kit (task suites, graders, regression gates, run records)","human_summary":"A written evaluation system for agents: task-suite/run-record/gate-config JSON schemas, six anchored rubric families, written regression gates, and worked evaluations.","included_reality":"Task-Suites/, Graders/ (7), Regression-Gates/, Run-Records/, Worked-Evaluations/ folders plus the standard architecture.","best_for":["Engineers and QA leads evaluating agent quality","Teams gating releases on written regression checks","Evaluator agents applying anchored rubrics"],"not_for":["Buyers expecting an eval runner or benchmark software","Teams with no agent to evaluate","Anyone expecting hosted dashboards or leaderboards"],"limitations":["You run evaluations with your own models/agents and record results in the provided schemas - no runner code is included","'Harness Suite' is a document+schema suite, not an application"],"refund_risk_flags":["name_implies_software","requires_own_agent_stack"],"pre_purchase_questions":["Do I have an agent and the time to actually run structured evals against it?"]},"agent-prompt-injection-defense-kit":{"kind":"defensive security kit (trust taxonomy, quarantine policies, detection heuristics, regression suites)","human_summary":"Defensive patterns against prompt injection: a content trust ladder, instruction hierarchy model, untrusted-content policies, detection heuristics, and regression test suites.","included_reality":"Trust-Taxonomies/, Quarantine-Policies/, Detection-Heuristics/ (5), Regression-Suites/, Worked-Defenses/ folders plus the standard architecture.","best_for":["Engineers hardening agents that read untrusted content","Security reviewers writing agent trust policy","Operators adding written injection defenses and tests"],"not_for":["Buyers expecting a security product that blocks attacks automatically","Anyone wanting a security guarantee - none exists, from anyone","Offensive security use (defensive only)"],"limitations":["Defense-in-depth guidance and tests, NOT a guarantee: no defense stops all injections","Your stack must apply the policies; heuristics are written patterns, not a scanner service"],"refund_risk_flags":["no_security_guarantee","policy_not_enforcement_software"],"pre_purchase_questions":["Do my agents process untrusted content (web, email, files) where written defenses and regression tests would apply?"]},"agent-audit-trail-generator":{"kind":"schema + method kit (action taxonomy, entry schemas, integrity and redaction rules)","human_summary":"A written audit-trail standard for agent actions: an 8-class action taxonomy, per-class JSON entry schemas, append-only integrity rules (tamper-evident, honestly not tamper-proof), redaction rules, and sampling plans.","included_reality":"Audit-Schemas/ (4), Sampling-Plans/, Worked-Trails/ folders plus the standard architecture.","best_for":["Operators who must show what their agents did","Compliance leads defining audit requirements","Reviewer agents writing entries against a fixed schema"],"not_for":["Buyers expecting logging software or a dashboard - 'Generator' names the schema system, not a tool","Teams that will not wire logging into their stack","Anyone needing certified compliance tooling"],"limitations":["Your agents/stack write the log entries; the kit defines WHAT to write and HOW to keep it reviewable","Tamper-EVIDENT by design and honestly documented as not tamper-PROOF"],"refund_risk_flags":["name_implies_software","requires_own_agent_stack","not_legal_advice"],"pre_purchase_questions":["Can my agent framework emit structured log entries I define?"]},"agent-safety-case-builder":{"kind":"governance kit (claim-argument-evidence safety cases, evidence registry, review records)","human_summary":"A written safety-case system for agent deployments: claim-argument-evidence framing, safety-case and evidence-registry JSON schemas, hazard analysis, and review records.","included_reality":"Safety-Cases/, Evidence-Registry/ (4), Review-Records/, Worked-Safety-Cases/ folders plus the standard architecture.","best_for":["Safety leads and engineering managers justifying agent deployments","Teams that need a reviewable written safety argument","Compliance reviewer agents checking evidence links"],"not_for":["Buyers expecting automated safety verification","Casual single-agent hobby use","Anyone treating a safety case as a legal shield by itself"],"limitations":["A safety case is an argument backed by YOUR evidence - the kit structures it, you substantiate it","Not a certification, audit service, or legal advice"],"refund_risk_flags":["method_not_executable","not_legal_advice"],"pre_purchase_questions":["Do I have a deployment decision that genuinely needs a written safety argument?"]},"agent-runtime-incident-response-kit":{"kind":"operations kit (incident classes, containment ladders, kill-switch procedures, postmortems)","human_summary":"A written incident-response system for agent operations: severity model, containment ladders, kill-switch procedures, incident-record and postmortem JSON schemas, and tabletop exercises.","included_reality":"Incident-Classes/, Containment-Ladders/ (3), Kill-Switch-Procedures/, Postmortems/, Worked-Incidents/ folders plus the standard architecture.","best_for":["Operators and on-call engineers running agents in production","Teams rehearsing containment before they need it","Supervisor agents following written containment ladders"],"not_for":["Buyers expecting monitoring/alerting software or an emergency service","Stacks with no runtime agents","Anyone expecting the kit to stop incidents by itself"],"limitations":["Procedures work when rehearsed and wired to YOUR stop controls - the kit includes no monitoring or paging software","Kill-switch procedures document how to use the controls your platform already has"],"refund_risk_flags":["playbook_not_monitoring_software","requires_own_agent_stack"],"pre_purchase_questions":["Does my platform expose stop/disable controls these procedures can point at?"]},"agent-skill-packaging-kit":{"kind":"packaging kit (manifest standards, trigger specs, test packs, checklists)","human_summary":"A written standard for packaging agent skills: manifest standard with reference JSON, instruction file standard, trigger specs, test packs, and packaging checklists.","included_reality":"Manifest-Standards/, Trigger-Specs/, Test-Packs/, Packaging-Checklists/, Worked-Packages/ folders plus the standard architecture.","best_for":["Developers packaging skills for agent platforms","Teams standardizing skill quality before distribution","Builder agents assembling skill packages against a standard"],"not_for":["Buyers expecting a packaging CLI or build tool","Anyone expecting marketplace submission or approval - none is promised","Non-builders with no skills to package"],"limitations":["Standards and tests are applied by you/your agents - no build tooling is included","Platform acceptance always depends on the platform, not this kit"],"refund_risk_flags":["method_not_executable","no_marketplace_approval_promise"],"pre_purchase_questions":["Am I building skills for a platform where a written packaging standard raises quality?"]},"mcp-server-description-optimizer":{"kind":"method kit (description contract, quality rubric, failure catalog, rewrite harness)","human_summary":"A written method for improving MCP server/tool descriptions so agents select tools correctly: five-clause description contract, anchored quality rubric, selection-failure catalog with matched fixes, and before/after rewrites.","included_reality":"Description-Rubrics/ (4), Failure-Catalog/ (3), Test-Harnesses/, Rewrites/ folders plus the standard architecture.","best_for":["MCP server developers whose tools get mis-selected","Agent platform teams maintaining tool surfaces","Dev agents applying the contract to description rewrites"],"not_for":["Buyers expecting a linter or code tool - 'Optimizer' names the method","Anyone without MCP servers or tool descriptions to improve","Teams expecting model behavior guarantees"],"limitations":["Selection outcomes still depend on the client model - the method improves the description side you control","Test harnesses are written procedures you run with your own agents"],"refund_risk_flags":["name_implies_software","outcome_depends_on_model_behavior"],"pre_purchase_questions":["Do I own MCP tool descriptions I can rewrite and re-test this week?"]},"gpt-assistant-productization-kit":{"kind":"productization kit (pipeline with exit gates, charter standard, config specs, guardrail checks)","human_summary":"A written pipeline for turning a prompt-based assistant into a shippable product: productization pipeline with exit gates, charter standard with mandatory nevers, configuration specs, knowledge packaging, guardrail checks, and listing readiness.","included_reality":"Config-Specs/ (3), Knowledge-Packaging/, Guardrail-Checks/ (4), Listing-Readiness/, Worked-Productization/ folders plus the standard architecture.","best_for":["Assistant builders shipping GPTs/assistants to real users","Agencies delivering client assistants against a checklist","Review agents checking configs against the standard"],"not_for":["Buyers expecting store approval or distribution promises","Anyone expecting the kit to build the assistant for them","Teams without an assistant concept to productize"],"limitations":["Platform store policies and approvals are outside anyone's control - readiness improves your side only","Configuration is applied by you in your platform account"],"refund_risk_flags":["no_marketplace_approval_promise","outcome_depends_on_buyer_execution"],"pre_purchase_questions":["Do I have an assistant concept ready to take through exit gates?"]},"agent-marketplace-listing-kit":{"kind":"listing standard kit (dual-reader listing schema, claim-evidence maps, worked listings)","human_summary":"A 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.","included_reality":"Listing-Schemas/, Claim-Evidence-Maps/ (3), Worked-Listings/, Checklists/ (3) folders plus the standard architecture.","best_for":["Sellers preparing products for agent-mediated buying","Marketplace operators defining listing standards","Seller agents generating listings against the schema"],"not_for":["Buyers expecting live marketplace integrations or traffic","Anyone expecting sales promises - none are made","Sellers with nothing to list"],"limitations":["The standard improves listing trustworthiness; discovery and sales depend on your channels","No marketplace accounts or APIs included"],"refund_risk_flags":["outcome_depends_on_buyer_execution","no_platform_integration"],"pre_purchase_questions":["Do I sell (or plan to sell) products that agents will evaluate on a buyer's behalf?"]},"agent-license-access-control-kit":{"kind":"rights kit (license record schema, entitlement rules, verification checks)","human_summary":"A written license/entitlement system for agent-native products: agent-readable license record schema with reference instance, entitlement lifecycle rules, and verification checks.","included_reality":"License-Records/, Entitlement-Rules/ (3), Verification-Checks/, Worked-Lifecycle/ folders plus the standard architecture.","best_for":["Digital sellers defining machine-readable license records","Multi-agent operators verifying entitlements in writing","Consuming agents checking license records against rules"],"not_for":["Buyers expecting DRM, license servers, or copy protection software","Anyone expecting legal enforcement services","Sellers without products to license"],"limitations":["Defines and verifies WRITTEN license records - it cannot technically prevent copying (no DRM exists in plain files)","Not legal advice; consult counsel for enforceable terms in your jurisdiction"],"refund_risk_flags":["policy_not_enforcement_software","not_legal_advice"],"pre_purchase_questions":["Do I need machine-readable license records, as opposed to technical copy protection?"]},"agent-commerce-trust-layer":{"kind":"trust framework kit (verification checklists, claim-evidence, dispute records, reputation schemas)","human_summary":"A written trust framework for agent-mediated commerce: seller verification standard, claim-evidence discipline, dispute record schemas, and reputation schemas - the suite's capstone governance layer.","included_reality":"Verification-Checklists/ (3+), Claim-Evidence/ (3), Dispute-Records/ (4), Reputation-Schemas/, Worked-Trust-Profiles/ folders plus the standard architecture.","best_for":["Marketplace operators designing trust rails","Buying/seller agents applying written verification standards","Agent-commerce builders needing a trust vocabulary"],"not_for":["Buyers expecting a live reputation network or escrow service","Anyone expecting fraud prevention software","Casual sellers without agent-commerce ambitions"],"limitations":["'Layer' is a document framework - there is no hosted network, API, or reputation database","Trust outcomes depend on all parties actually adopting the standards"],"refund_risk_flags":["name_implies_software","adoption_dependent"],"pre_purchase_questions":["Am I building or governing agent commerce where a written trust standard gets adopted?"]},"multi-agent-role-charter-kit":{"kind":"coordination kit (role-authority contracts, authority maps, escalation matrices)","human_summary":"A written role system for multi-agent setups: role-authority contracts, authority maps with one-owner-per-decision arithmetic, escalation matrices, and worked charters.","included_reality":"Role-Charters/, Authority-Maps/ (3), Escalation-Matrices/ (3), Worked-Charters/, Checklists/ (3) folders plus the standard architecture.","best_for":["Operators running two or more coordinating agents","Orchestrator builders defining who may decide what","Agent-organization designers"],"not_for":["Single-agent or single-chat users","Buyers expecting an orchestration framework or runtime","Anyone expecting agents to self-organize from the documents alone"],"limitations":["Charters take effect when loaded into YOUR agents' instructions - no runtime is included","Multi-agent coordination still requires your orchestration tooling"],"refund_risk_flags":["requires_own_agent_stack","method_not_executable"],"pre_purchase_questions":["Do I actually run multiple agents whose authority needs defining?"]},"agent-handoff-protocol-kit":{"kind":"coordination kit (handoff envelopes, acceptance tests, worked handoffs)","human_summary":"A written protocol for work passing between agents (or agents and humans): handoff envelopes covering context/authority/open-risks/acceptance/disposition, acceptance tests, and the acceptance-transfers-ownership rule.","included_reality":"Handoff-Envelopes/ (4), Acceptance-Tests/ (4), Worked-Handoffs/, Checklists/ (3) folders plus the standard architecture.","best_for":["Multi-agent operators with real handoffs","Human-in-the-loop teams formalizing acceptance","Sending/receiving agents applying envelope structure"],"not_for":["Single-agent workflows with nothing to hand off","Buyers expecting a message bus or queue software","Teams unwilling to define acceptance criteria"],"limitations":["Envelopes are structured documents your agents exchange through YOUR channels - no transport included","Value appears only where handoffs actually occur"],"refund_risk_flags":["requires_own_agent_stack","method_not_executable"],"pre_purchase_questions":["Where in my workflow does work change hands today?"]},"agent-deployment-readiness-checklist-system":{"kind":"checklist system (evidence-gated readiness gates, sign-off records)","human_summary":"An evidence-gated go/no-go system for agent deployments: capability/safety/rollback/monitoring/ownership gate families, evidence-required checklists, and sign-off records.","included_reality":"Readiness-Gates/, Evidence-Requirements/ (3), Sign-Off-Records/, Worked-Readiness/, Checklists/ (5) folders plus the standard architecture.","best_for":["Engineering managers gating agent launches","Reviewer agents verifying evidence completeness","Teams that want auditable go/no-go decisions"],"not_for":["Buyers expecting automated testing or CI tooling","Hobby deployments where a checklist feels heavier than the stakes","Anyone signing off without gathering the evidence"],"limitations":["Gates are as strong as the evidence YOU attach - the system structures the decision, you substantiate it","'System' means an organized checklist system, not software"],"refund_risk_flags":["name_implies_software","method_not_executable"],"pre_purchase_questions":["Do I have deployments where an evidence-backed go/no-go would change decisions?"]},"agent-procurement-policy-pack":{"kind":"policy pack (procurement contracts, budget rules, vendor rubrics, purchase records)","human_summary":"Written procurement policy for agents that evaluate or buy on your behalf: budget/vendor/evaluation/approval/record policy contracts, delegation ladders with spend limits, and purchase records.","included_reality":"Procurement-Policies/, Budget-Rules/ (3), Vendor-Rubrics/, Purchase-Records/, Worked-Procurement/ folders plus the standard architecture.","best_for":["Operators delegating vendor evaluation to agents","Finance leads bounding agent spending authority in writing","Procurement agents applying documented rubrics"],"not_for":["Buyers expecting agents to safely buy things today - autonomous purchasing is not enabled by this pack or this store","Anyone expecting payment integrations","Teams with no delegated evaluation or buying"],"limitations":["Policy only: it does not connect to payment rails and does not authorize any agent to spend money","Spending enforcement lives in your payment controls, not in documents"],"refund_risk_flags":["policy_not_enforcement_software","no_payment_integration"],"pre_purchase_questions":["Am I bounding agent recommendations/evaluations, understanding no purchasing rail is included?"]}},"bundles":{"what_a_bundle_is":"A bundle is a one-time purchase of the listed products' files at the stated tier, priced below buying them separately. Nothing beyond the listed products is included.","not_included":["No products beyond those listed in the bundle definition","No future products added later ('Complete' names the suite as of this catalog version)","No subscription benefits: bundles are one-time purchases, not vault memberships","No lifetime premium updates beyond the purchased versions plus their fixes"],"fit_rule":"A bundle fits when at least two of its products independently pass your fit check; buying a bundle for one product usually costs more than buying that product alone."},"subscription_clarity":"SignalHarness Vault monthly and annual recurring access is active through Polar. x402 monthly and annual access uses separate prepaid renewable terms; each renewal requires a new payment and no wallet is charged automatically. Public discovery remains free and ungated.","refund_prevention":{"read_before_buying":["Read the product's included/not-included lists - if a capability is not listed, it is not included","Check the free sample (sample_url) before purchasing - every product has one","Confirm the skill level and setup time match your reality","If you are unsure about fit, email support@signalharness.ai BEFORE buying - pre-sales fit questions are covered support"],"self_check_questions":["Have I read what this product is NOT?","Have I opened the free sample?","Do I have the tools listed under required inputs (my own AI access, my own accounts)?","Do I have implementation time this week, not just reading time?","Am I buying a document system on purpose - not software, not a service, not done-for-you work?"],"contact_before_refund":"Email support@signalharness.ai before requesting a refund. Delivery failures, corrupted files, wrong-tier purchases, and most fit confusion are fixable - usually within one business day. Refund requests remain available under the 14-day policy either way.","escalation_steps":["1. Check the product's FAQ.md and QUICK-START.md (most setup questions are answered there)","2. Check Integration/ for the compatibility matrix, known conflicts, and rollback guide","3. Email support@signalharness.ai with your order reference and what did not match","4. Support responds within 1 business day (delivery issues prioritized) with a fix, a replacement, or refund processing - your choice where a defect is confirmed"]}}