{"name":"Sustineri Intelligence Marketplace","description":"Source-grounded BOI analytical services sold per run over x402. Every result cites exact spans of supplied text; unreleased services cannot be executed.","version":"1.0.0","provider":{"organization":"Sustineri Consulting Group, LLC","url":"https://sustineri-x402.onrender.com"},"documentationUrl":"https://sustineri-x402.onrender.com/llms.txt","supportedInterfaces":[],"capabilities":{"streaming":false,"pushNotifications":false,"stateTransitionHistory":false},"defaultInputModes":["application/json"],"defaultOutputModes":["application/json"],"skills":[{"id":"SUST-CONTEXT-GAP-001","name":"Context Gap Check","description":"Work backward from the requested decision. Name missing prerequisites, distinguish unknowns from assumptions, and explain which conclusion each gap blocks. Do not reconstruct unknown facts as truth.","tags":["Context architecture","x402"],"examples":["An expansion plan has a location and launch date but no budget or staffing capacity."]},{"id":"SUST-TRANSCRIPT-MAP-001","name":"BOI Transcript Map","description":"Apply source → attributed units → speaker confidence → semantic types → entities → topic clusters → relationships → provenance → dependency layers → bridge gaps → supplied canon reconciliation → actions and routing. Preserve context and competing accounts. Never treat speech-pattern attribution as confirmed identity. Report canon reconciliation as not performed if no canon is supplied.","tags":["Context architecture","x402"],"examples":["Two unlabeled speakers give different launch dates and one promises to send a lease."]},{"id":"SUST-CONTEXT-LINEAGE-001","name":"Answer Lineage Trace","description":"Decompose a submitted answer into claims, premises, transformations, and conclusions. Reconstruct only the trace supported by the supplied artifacts. A plausible chain is not evidence of how an earlier model actually reasoned.","tags":["Context architecture","x402"],"examples":["A recommendation cites a budget spreadsheet but provides no link between the numbers and its conclusion."]},{"id":"SUST-DEPENDENCY-ORDER-001","name":"Dependency Order Check","description":"Find the order in which prerequisites must be established before a decision can be justified. Model depends_on edges, distinguish temporal sequence from logical dependency, and preserve cycles as blockers rather than pretending the plan can be sorted.","tags":["Context architecture","x402"],"examples":["A launch requires licensing; licensing requires premises; the premises contract requires funding."]},{"id":"SUST-REPLICATION-CHECK-001","name":"Replication Drift Check","description":"Compare two supplied runs or builds against supplied acceptance criteria. Separate appearance match from behavior match. Trace drift to missing context, changed constraints, or unsupported transformations; leave causes tentative unless demonstrated.","tags":["Context architecture","x402"],"examples":["Two client maps look alike but only one retains the source of each decision."]},{"id":"SUST-INFORMATION-FLOW-001","name":"Information Flow Check","description":"Evaluate the legibility and movement of supplied information using the founder's feng shui principle: what enters, where it belongs, what obstructs it, and how the reader finds the next action. Do not claim an accessibility audit without rendered UI evidence.","tags":["Context architecture","x402"],"examples":["A dashboard mixes internal notes, client requests, approval decisions, and completed work in one list."]},{"id":"SUST-WORKFLOW-FRICTION-001","name":"Workflow Friction Check","description":"Map work intake, movement, handoffs, returns, and closure. Distinguish observed failures from suspected causes. Propose a repair sequence tied to each failure; do not invent processing times or savings.","tags":["Operations","x402"],"examples":["Requests enter an inbox but nobody owns them and completion is never returned."]},{"id":"SUST-CLOSURE-CHECK-001","name":"Has the Loop Closed?","description":"Evaluate each work item against initiation, acceptance, execution, verification, downstream return, and owner acknowledgement. A sent handoff is not a closed loop. State exactly which closure evidence is missing.","tags":["Operations","x402"],"examples":["A contractor says a fix was deployed, but the owner has not tested the live page."]},{"id":"SUST-HANDOFF-CONTRACT-001","name":"Handoff Contract Builder","description":"Convert supplied work into DESTINATION, TYPE, WORKSTREAM, TASK, OUTPUT, VERIFY contracts. Identify dependencies and acceptance criteria. Unknown authority, recipient, or owner must remain unknown; do not send the handoff.","tags":["Operations","x402"],"examples":["An owner needs Claude to refine a microsite while preserving approved logo provenance."]},{"id":"SUST-AUTHORITY-BOUNDARY-001","name":"Authority Boundary Check","description":"Compare proposed agent actions against supplied permissions and standing authorizations. Distinguish reading, drafting, modifying, sending, spending, and publishing. Never infer authority from mere technical capability.","tags":["Operations","x402"],"examples":["An agent can draft an email but the owner requires review before sending."]},{"id":"SUST-WORK-PROPAGATION-001","name":"Work Propagation Map","description":"Trace how a supplied change propagates across people, records, workflows, and outputs. Separate direct dependencies from speculative effects. Identify downstream writeback and verification, with no external writes.","tags":["Operations","x402"],"examples":["A CE course ID changes and must reach registration, certificates, reporting, and public listings."]},{"id":"SUST-RETURN-FEEDBACK-001","name":"Return Feedback Reconciler","description":"Compare a worker or model return against the original instruction, supplied canon, and acceptance criteria. Preserve corrections, unresolved conditions, and evidence. Never treat an APPROVE WITH CONDITIONS return as unconditional approval.","tags":["Operations","x402"],"examples":["A website return says approved but includes an unresolved owner logo-verification condition."]},{"id":"SUST-OPPORTUNITY-FIT-001","name":"Opportunity Fit Check","description":"Match a supplied opportunity's explicit requirements against documented business facts. Use MET, NOT_MET, or UNKNOWN, name required proof, and separate eligibility from competitiveness. No award prediction or live search.","tags":["Opportunity","x402"],"examples":["A solicitation requires a certification that the company profile mentions but does not document."]},{"id":"SUST-PROCUREMENT-CHAIN-001","name":"Procurement Delivery Chain","description":"Map supplied appropriation, program, agency, procurement, award, and delivery records into a chain. Label appropriated funds separately from open procurements and actual awards. Missing official records are gaps, not inferred opportunities.","tags":["Opportunity","x402"],"examples":["A budget funds a program but no solicitation or award record is supplied."]},{"id":"SUST-MARKET-ENTRY-001","name":"Founder Market Entry Map","description":"Build a dependency map for a founder entering a supplied market: customer, positioning, location, operating model, licensing facts, startup inputs, and timing. No current licensing or market claim without supplied dated sources.","tags":["Opportunity","x402"],"examples":["A stylist is moving states and needs a private-room service model before signing a lease."]},{"id":"SUST-DECISION-COUNTERCASE-001","name":"Decision Countercase","description":"Build the strongest source-supported case against a proposed decision and name what evidence would change the recommendation. Keep adversarial hypotheses distinct from documented problems; do not invent competitors or costs.","tags":["Opportunity","x402"],"examples":["A founder wants a new location while current operations already show unresolved capacity constraints."]},{"id":"SUST-ROLE-LOAD-001","name":"Load-Bearing Role Map","description":"Identify who holds critical knowledge, invisible coordination, and single-person dependencies from supplied work records. Do not diagnose people or infer employee intent. Proposed role changes require owner review.","tags":["People and workforce","x402"],"examples":["One coordinator handles all exceptions while job descriptions mention only routine scheduling."]},{"id":"SUST-PEOPLE404-001","name":"People 404 Positioning Map","description":"Separate skill gaps from role, authority, process, workload, and system-design gaps. Propose stabilize, upskill, reposition, or redesign pathways with reasons and a 30/60/90 sequence. Do not rank personal worth or make employment decisions.","tags":["People and workforce","x402"],"examples":["A team is asked to train harder while lacking permission to complete its assigned work."]},{"id":"SUST-KNOWLEDGE-CONTINUITY-001","name":"Knowledge Continuity Check","description":"Map tacit knowledge and exception handling at risk of being lost. Generate capture questions, teach-back exercises, and transfer evidence. A stored document alone is not a successful knowledge transfer.","tags":["People and workforce","x402"],"examples":["A retiring specialist knows which exceptions break a process, but the SOP covers only normal cases."]},{"id":"SUST-HUMAN-AI-WORK-001","name":"Human and AI Work Design","description":"Evaluate supplied tasks for human judgment, AI support, redesign, and approval needs. Map context requirements and failure recovery. Never assume that automatable means appropriate to automate.","tags":["People and workforce","x402"],"examples":["An intake assistant can extract records but the final client recommendation requires professional judgment."]},{"id":"SUST-CLAIM-FILE-GAP-001","name":"Claim File Gap Check","description":"Inventory submitted claim documents, factual chronology, invoice/payment distinctions, and competing accounts. Name missing proof. Do not decide coverage, liability, legal deadlines, amounts legally owed, or representation strategy. Do not invent calculations; any arithmetic must be supplied or separately computed.","tags":["Document integrity","x402"],"examples":["An invoice and payment receipt exist but vendor correspondence describes a different balance."]},{"id":"SUST-CANON-RECONCILE-001","name":"Canon Reconciliation Check","description":"Compare a proposed update with explicitly supplied canonical records. Identify duplicates, superseded facts, contradictions, scope changes, and downstream updates. Canon cannot be inferred from an old conversation summary. No overwrite or writeback.","tags":["Document integrity","x402"],"examples":["A new brief uses an old contact address while the canonical routing record has been updated."]},{"id":"SUST-SOURCING-COMPARE-001","name":"Sourcing Comparison","description":"Compare supplied supplier offers on specification, quantity, currency, quote date, shipping terms, lead time, and missing landed-cost inputs. Missing shipping, duty, or exchange rates makes delivered cost unknown. No supplier certification, discovery, ordering, or cheapest claim across incomplete quotes.","tags":["Sourcing","x402"],"examples":["Two quotes use different shipping terms and one omits destination freight."]},{"id":"SUST-SUPPLY-DEPENDENCY-001","name":"Supply Dependency Map","description":"Map supplied materials, suppliers, lead times, substitutions, production, and delivery dependencies. Identify concentration and single-point failure from actual records. Alternatives are hypotheses until qualified; do not invent lead times or supplier reliability.","tags":["Sourcing","x402"],"examples":["A launch depends on one supplier's packaging while no alternate has been qualified."]},{"id":"SUST-EVIDENCE-CONFLICT-001","name":"Evidence Conflict Resolver","description":"Compare conflicting supplied records without collapsing them into one story. Identify what each source supports, where they diverge, which source has stronger provenance, and what evidence would resolve the conflict. Do not declare a winner when the supplied record does not justify one.","tags":["Evidence intelligence","x402"],"examples":["Two dated records report different completion dates for the same work item."]},{"id":"SUST-SOURCE-FRESHNESS-001","name":"Source Freshness Gate","description":"Check whether supplied sources are current enough for the requested decision. Separate stale, undated, superseded, and time-insensitive evidence. Do not infer that an older source is wrong merely because it is old.","tags":["Evidence intelligence","x402"],"examples":["A launch decision relies on a policy copy from last year and a current contract."]},{"id":"SUST-CLAIM-PROOF-MATRIX-001","name":"Claim-to-Proof Matrix","description":"Map each material claim to the exact supplied proof that supports, weakens, or leaves it unresolved. Keep first-person accounts, documentary evidence, and agent interpretation distinct. Do not promote repetition into corroboration.","tags":["Evidence intelligence","x402"],"examples":["A project brief contains ten claims but only six have attached records."]},{"id":"SUST-ASSUMPTION-EXPOSURE-001","name":"Assumption Exposure Map","description":"Expose assumptions embedded in a plan or recommendation. Separate stated facts from hidden premises and show which conclusions fail if an assumption is false. Do not convert assumptions into facts.","tags":["Evidence intelligence","x402"],"examples":["A staffing plan assumes every role can be filled before launch without evidence."]},{"id":"SUST-DECISION-RIGHTS-001","name":"Decision Rights Map","description":"Map supplied roles, approvals, and authority into who proposes, approves, executes, verifies, and receives each decision. Unknown rights remain unknown. Never infer authority from job title alone.","tags":["Governance","x402"],"examples":["A project lists owners but does not say who can approve spending or publication."]},{"id":"SUST-POLICY-WORKFLOW-001","name":"Policy-to-Workflow Translator","description":"Translate supplied policy language into operational checkpoints, required records, approval gates, and exception paths. Preserve policy wording as source evidence and label workflow design as interpretation.","tags":["Governance","x402"],"examples":["A privacy policy requires consent but the intake workflow has no consent checkpoint."]},{"id":"SUST-EXCEPTION-GOVERNANCE-001","name":"Exception Governance Check","description":"Identify where a supplied workflow handles exceptions, who may authorize deviation, what must be recorded, and how the normal path resumes. Do not treat undocumented workarounds as approved policy.","tags":["Governance","x402"],"examples":["A team routinely bypasses the normal intake path for urgent requests."]},{"id":"SUST-AUDIT-TRAIL-001","name":"Audit Trail Completeness Check","description":"Assess whether a supplied decision or workflow leaves enough evidence to reconstruct who did what, when, under what authority, and with what verification. Do not claim regulatory compliance from record completeness alone.","tags":["Governance","x402"],"examples":["A deployment log shows the change but not who approved it or who verified production."]},{"id":"SUST-CLIENT-INTAKE-GAP-001","name":"Client Intake Gap Map","description":"Map a client's stated goal to the information required to start work safely and efficiently. Separate nice-to-have context from true blockers. Do not invent client facts to fill missing intake fields.","tags":["Client delivery","x402"],"examples":["A client wants a market entry plan but has not supplied budget, timing, or target customer."]},{"id":"SUST-SCOPE-DRIFT-001","name":"Scope Drift Detector","description":"Compare the original supplied scope with later requests, decisions, and deliverables. Classify additions, substitutions, clarifications, and contradictions without assuming every change is improper.","tags":["Client delivery","x402"],"examples":["A website engagement expands from five pages to include a portal and automation."]},{"id":"SUST-DELIVERABLE-ACCEPTANCE-001","name":"Deliverable Acceptance Check","description":"Compare a delivered output against explicit acceptance criteria and owner feedback. Distinguish complete, conditionally accepted, rejected, and unverified elements. Delivery alone is not acceptance.","tags":["Client delivery","x402"],"examples":["A client says the draft is close but asks for two corrections before approval."]},{"id":"SUST-CLIENT-DEPENDENCY-001","name":"Client Dependency Map","description":"Identify client-provided inputs, approvals, access, and decisions that downstream work depends on. Separate provider blockers from client blockers and show the next unblocked work.","tags":["Client delivery","x402"],"examples":["A project is waiting on client credentials, but research and copy review can continue."]},{"id":"SUST-OFFER-ARCHITECTURE-001","name":"Offer Architecture Check","description":"Evaluate a supplied offer for problem, buyer, outcome, scope, boundaries, evidence, handoff, and completion logic. Do not invent demand, conversion rates, or market size.","tags":["Commercial systems","x402"],"examples":["A consulting offer names activities and price but not the buyer outcome or completion condition."]},{"id":"SUST-BUYER-FRICTION-001","name":"Buyer Friction Map","description":"Trace a supplied buyer journey from discovery through purchase and delivery. Identify documented uncertainty, unnecessary steps, broken handoffs, and missing trust evidence. Do not invent customer behavior.","tags":["Commercial systems","x402"],"examples":["A buyer must email twice before learning price and still cannot tell what happens after payment."]},{"id":"SUST-REVENUE-LEAKAGE-001","name":"Revenue Leakage Map","description":"Map supplied revenue events, missed billing triggers, incomplete follow-up, unpriced work, and failed handoffs. Do not calculate losses without supplied amounts and do not label unknown amounts as lost revenue.","tags":["Commercial systems","x402"],"examples":["Completed add-on work appears in project notes but never reaches invoicing."]},{"id":"SUST-REFERRAL-CHAIN-001","name":"Referral Chain Map","description":"Map supplied referral sources, introductions, routing, attribution, and follow-up obligations. Separate referral evidence from assumed influence and identify where attribution or return communication breaks.","tags":["Commercial systems","x402"],"examples":["A partner sends leads by text, but the business does not record source or report outcomes back."]},{"id":"SUST-PROPERTY-CONDITION-001","name":"Property Condition Evidence Map","description":"Organize supplied property-condition observations, photos described in text, repair records, dates, and reported changes into a factual condition map. Do not diagnose causes, determine coverage, or make engineering conclusions.","tags":["Property and assets","x402"],"examples":["A ceiling stain appears in several dated records but the repair history is incomplete."]},{"id":"SUST-MAINTENANCE-ESCALATION-001","name":"Maintenance Escalation Map","description":"Trace supplied maintenance reports from first notice through acknowledgement, inspection, repair, verification, and recurrence. Identify missed escalation points without assigning legal liability.","tags":["Property and assets","x402"],"examples":["A tenant reported a leak twice before an inspection was scheduled."]},{"id":"SUST-VENDOR-COORDINATION-001","name":"Vendor Coordination Check","description":"Map supplied vendor scopes, appointments, dependencies, owner approvals, access needs, and completion evidence. Flag overlaps, gaps, and sequencing conflicts without evaluating professional competence.","tags":["Property and assets","x402"],"examples":["A roofer and interior contractor are scheduled, but neither scope says who verifies the leak is resolved."]},{"id":"SUST-ASSET-HANDOFF-001","name":"Asset Handoff Map","description":"Build a handoff record for an asset moving between owners, managers, operators, or vendors. Track keys, access, records, open work, money-state evidence, responsibilities, and acceptance. Do not transfer authority or funds.","tags":["Property and assets","x402"],"examples":["A property manager is taking over while repairs, tenant communication, and records are still open."]},{"id":"SUST-COURSE-EVIDENCE-001","name":"Course Evidence Alignment Check","description":"Compare supplied course objectives, instructional content, activities, and assessments to determine whether each objective has evidence of being taught and evaluated. Do not claim accreditation or regulator approval.","tags":["Learning and credentials","x402"],"examples":["A course objective promises ethics decision practice, but the assessment only checks definitions."]},{"id":"SUST-ASSESSMENT-INTEGRITY-001","name":"Assessment Integrity Check","description":"Review supplied assessments for objective coverage, answerability from taught material, ambiguity, duplication, and evidence of scoring rules. Do not certify psychometric validity without appropriate data.","tags":["Learning and credentials","x402"],"examples":["A quiz contains duplicate questions and two items not covered in the lesson."]},{"id":"SUST-TRAINING-TRANSFER-001","name":"Training Transfer Map","description":"Map how supplied training is expected to move into real work through practice, supervision, job aids, feedback, and proof of application. A completed class alone is not evidence of behavior change.","tags":["Learning and credentials","x402"],"examples":["Employees complete training but have no practice period or manager verification afterward."]},{"id":"SUST-CREDENTIAL-READINESS-001","name":"Credential Readiness Map","description":"Compare supplied credential requirements against documented prerequisites, training, experience, examinations, applications, fees, and evidence. Use MET, NOT_MET, or UNKNOWN only when supported by the supplied records; do not state current law without a dated source.","tags":["Learning and credentials","x402"],"examples":["An applicant has training certificates but no supplied proof of the required experience hours."]},{"id":"SUST-RESEARCH-DECOMPOSE-001","name":"Research Question Decomposer","description":"Break a supplied research question into answerable subquestions, evidence requirements, dependencies, and decision relevance. Do not answer missing research from memory or invent sources.","tags":["Research intelligence","x402"],"examples":["A founder asks whether to enter a market but the question mixes demand, licensing, cost, and positioning."]},{"id":"SUST-SOURCE-COVERAGE-001","name":"Source Coverage Map","description":"Map which parts of a decision are covered by supplied sources and which remain unsupported. Distinguish duplicate evidence from genuinely independent coverage.","tags":["Research intelligence","x402"],"examples":["Five articles support market demand, but none address operating cost or regulatory requirements."]},{"id":"SUST-EVIDENCE-SATURATION-001","name":"Evidence Saturation Check","description":"Evaluate whether additional supplied evidence is adding new decision-relevant information or repeating what is already known. Do not claim statistical saturation from qualitative records alone.","tags":["Research intelligence","x402"],"examples":["A team has collected twenty interviews and wants to know whether the last five added anything new."]},{"id":"SUST-CONTRADICTION-CLUSTER-001","name":"Contradiction Cluster Map","description":"Group supplied contradictions by topic, source, date, and dependency so reviewers can see whether conflicts are isolated or systemic. Preserve each competing account.","tags":["Research intelligence","x402"],"examples":["Project records contain several different launch dates, owners, and scope descriptions."]},{"id":"SUST-DECISION-REVERSIBILITY-001","name":"Decision Reversibility Check","description":"Classify supplied decisions by how difficult they are to reverse using only documented commitments, dependencies, cost states, and timing. Do not invent financial exposure.","tags":["Strategy","x402"],"examples":["A founder is choosing between signing a long lease now or piloting a short-term location."]},{"id":"SUST-CONSTRAINT-STACK-001","name":"Constraint Stack Map","description":"Identify hard constraints, soft constraints, preferences, assumptions, and dependencies in a supplied plan. Show which constraints dominate downstream options.","tags":["Strategy","x402"],"examples":["A launch plan has a fixed date, limited staff, optional branding changes, and an assumed vendor lead time."]},{"id":"SUST-TRADEOFF-MAP-001","name":"Strategic Tradeoff Map","description":"Make the tradeoffs in a supplied decision explicit across documented goals, constraints, risks, and sacrifices. Do not fabricate weights or declare a winner without decision criteria.","tags":["Strategy","x402"],"examples":["A company can launch faster with fewer features or wait for a broader release."]},{"id":"SUST-OPERATING-MODEL-001","name":"Operating Model Coherence Check","description":"Check whether a supplied operating model aligns roles, workflows, technology, governance, client promises, and revenue mechanics. Identify mismatches without redesigning unknown areas as fact.","tags":["Strategy","x402"],"examples":["A firm promises rapid client turnaround but approvals still depend on one founder."]},{"id":"SUST-KPI-CAUSALITY-001","name":"KPI Causality Check","description":"Trace whether supplied KPIs are linked to controllable work and documented outcomes or are only correlated reporting measures. Do not claim causation without evidence.","tags":["Strategy","x402"],"examples":["A team tracks training completions but cannot show how the metric connects to work quality."]},{"id":"SUST-LEVERAGE-POINT-001","name":"Bottleneck Leverage Map","description":"Identify the smallest documented constraints that appear to block the largest amount of downstream work. Separate proven bottlenecks from suspected ones and require verification before intervention.","tags":["Strategy","x402"],"examples":["Several projects wait on one approval step while most other tasks are ready."]},{"id":"SUST-CHANGE-READINESS-001","name":"Change Readiness Map","description":"Assess supplied evidence for process readiness, role clarity, capacity, training, tooling, governance, and feedback before a change. Do not diagnose employee attitudes or predict adoption.","tags":["Strategy","x402"],"examples":["A business wants to deploy a new workflow but has not assigned owners or trained reviewers."]},{"id":"SUST-AUTOMATION-SUITABILITY-001","name":"Automation Suitability Check","description":"Evaluate supplied work for repeatability, context stability, exception rate evidence, authority needs, failure impact, and review requirements. Do not equate technical possibility with safe automation.","tags":["Automation governance","x402"],"examples":["A team wants to automate client approvals even though exceptions are handled differently each time."]},{"id":"SUST-AGENT-RECOVERY-001","name":"Agent Failure Recovery Map","description":"Map how a supplied agent workflow detects bad output, partial execution, unavailable tools, stale context, payment uncertainty, and failed writeback. Require a return path to a safe state.","tags":["Automation governance","x402"],"examples":["An agent can send work downstream but has no defined behavior when verification fails."]},{"id":"SUST-CONTEXT-CONTRACT-001","name":"Prompt and Context Contract Check","description":"Check whether a supplied agent instruction defines role, authority, sources, constraints, expected output, verification, and return behavior. Do not rewrite absent business rules as though approved.","tags":["Automation governance","x402"],"examples":["An agent prompt says to finish the task but never defines what completion means or what it may send."]},{"id":"SUST-REVIEW-GATE-001","name":"Human Review Gate Designer","description":"Use supplied risk and authority rules to propose where human review belongs before publication, spending, sending, external modification, or irreversible action. Recommendations remain proposals until approved.","tags":["Automation governance","x402"],"examples":["A workflow can draft, publish, and email without distinguishing which steps require owner review."]},{"id":"SUST-DATA-HANDOFF-001","name":"Data Handoff Integrity Check","description":"Check whether data passed between supplied systems preserves required fields, identifiers, provenance, status, and return references. Do not claim data loss without evidence.","tags":["Automation governance","x402"],"examples":["A CRM sends leads to an automation but drops the original referral source and approval status."]},{"id":"SUST-SYSTEM-DEPENDENCY-RISK-001","name":"System Dependency Risk Map","description":"Map supplied systems, services, credentials, storage, queues, and human fallbacks into dependency paths. Identify single points of failure from documented architecture only.","tags":["Automation governance","x402"],"examples":["A production workflow depends on one hosted API and one manual credential owner."]},{"id":"SUST-SERVICE-RECOVERY-001","name":"Service Recovery Map","description":"Trace what happens after a documented service failure: detection, acknowledgement, ownership, corrective work, client communication, verification, and closure. Do not invent compensation or liability.","tags":["Service operations","x402"],"examples":["A client reports a failed deliverable, but the team has no documented recovery sequence."]},{"id":"SUST-ESCALATION-PATH-001","name":"Escalation Path Check","description":"Map when supplied work must escalate, to whom, under what trigger, and what evidence should travel with it. Unknown escalation authority remains unknown.","tags":["Service operations","x402"],"examples":["Urgent support tickets are marked priority but there is no rule for who receives them next."]},{"id":"SUST-SLA-EVIDENCE-001","name":"SLA Evidence Check","description":"Compare supplied service commitments with timestamps and records that can prove acknowledgement, work start, resolution, and exclusions. Do not infer compliance where timing evidence is missing.","tags":["Service operations","x402"],"examples":["A contract promises a response window, but tickets only show final resolution times."]},{"id":"SUST-PROMISE-TRACE-001","name":"Customer Promise Trace","description":"Trace a supplied customer promise from sales language through scope, operations, delivery evidence, and closure. Identify where the operating system cannot currently prove the promise.","tags":["Service operations","x402"],"examples":["Marketing promises weekly reporting, but the delivery workflow contains no reporting step."]},{"id":"SUST-MEETING-ACTION-001","name":"Meeting-to-Action Map","description":"Convert supplied meeting notes into decisions, commitments, owners, dependencies, due dates or unknowns, and proof of completion. Do not invent owners or deadlines.","tags":["Execution control","x402"],"examples":["A meeting ends with several verbal commitments but no formal action register."]},{"id":"SUST-WORKLOAD-PORTFOLIO-001","name":"Portfolio Workload Map","description":"Map supplied active work across owners, dependencies, deadlines, blocked states, and verification needs to expose overload and collision points. Do not infer capacity that is not documented.","tags":["Execution control","x402"],"examples":["One founder owns approvals across several projects that are all due in the same week."]},{"id":"SUST-COMPLETION-PROOF-001","name":"Completion Proof Check","description":"Test whether a supplied claim that work is complete has evidence of execution, verification, downstream update, and owner return. A status label or sent message alone is not completion proof.","tags":["Execution control","x402"],"examples":["A task is marked done after deployment, but the live system has not been checked."]},{"id":"SUST-COST-DRIVER-MAP-001","name":"Cost Driver Map","description":"Map supplied costs to the activities, quantities, timing, and dependencies that drive them. Separate fixed, variable, one-time, recurring, and unknown cost states without inventing amounts.","tags":["Financial decision support","x402"],"examples":["A launch budget lists software, labor, and rent but does not show what causes each cost to change."]},{"id":"SUST-MARGIN-PRESSURE-001","name":"Margin Pressure Check","description":"Use supplied price, cost, discount, rework, and delivery records to identify documented margin pressure. Do not calculate unsupported margins or assume missing cost components are zero.","tags":["Financial decision support","x402"],"examples":["A service is discounted often and requires rework, but the true delivery cost is incomplete."]},{"id":"SUST-SCENARIO-COMPARE-001","name":"Scenario Comparison Map","description":"Compare supplied scenarios using the same documented assumptions and decision criteria. Keep missing inputs visible and do not manufacture forecasts.","tags":["Financial decision support","x402"],"examples":["A founder wants to compare hiring, outsourcing, and delaying a project."]},{"id":"SUST-CASH-COMMITMENT-001","name":"Cash Commitment Map","description":"Map supplied commitments that create future cash obligations, including contracts, subscriptions, retainers, deposits, and contingent commitments. Do not treat unconfirmed estimates as booked liabilities.","tags":["Financial decision support","x402"],"examples":["A business has signed vendor agreements but lacks a consolidated view of future cash commitments."]},{"id":"SUST-RISK-REGISTER-001","name":"Risk Register Builder","description":"Convert supplied evidence into a structured risk register with triggers, dependencies, current controls, owners or unknowns, and verification. Separate observed risks from hypotheses.","tags":["Risk and resilience","x402"],"examples":["A project has known vendor, staffing, and approval risks spread across several documents."]},{"id":"SUST-CONTROL-GAP-001","name":"Control Gap Check","description":"Compare supplied risks and processes against documented preventive, detective, corrective, and recovery controls. Missing controls remain gaps; do not claim formal compliance.","tags":["Risk and resilience","x402"],"examples":["A payment workflow can fail silently because it has no reconciliation check."]},{"id":"SUST-SINGLE-POINT-FAILURE-001","name":"Single Point of Failure Map","description":"Find documented people, systems, vendors, approvals, or records whose loss would stop critical work. Separate concentration from proven failure likelihood.","tags":["Risk and resilience","x402"],"examples":["One person holds the only credentials and approval authority for a core workflow."]},{"id":"SUST-CONTINGENCY-READINESS-001","name":"Contingency Readiness Check","description":"Assess whether supplied contingency plans define triggers, authority, alternate paths, required resources, communications, and return-to-normal evidence. Do not assume an undocumented fallback exists.","tags":["Risk and resilience","x402"],"examples":["A business has a disaster plan but no evidence for who activates it or how operations resume."]},{"id":"SUST-SALES-STAGE-INTEGRITY-001","name":"Sales Stage Integrity Check","description":"Compare supplied opportunity records against explicit stage-entry and stage-exit evidence. Do not treat optimistic labels as proof that a deal advanced.","tags":["Sales operations","x402"],"examples":["Several CRM deals are marked proposal sent even though no proposal record exists."]},{"id":"SUST-PROPOSAL-COVERAGE-001","name":"Proposal Coverage Map","description":"Map a supplied buyer request or RFP to proposal sections, evidence, assumptions, exceptions, and unanswered requirements. Do not infer compliance from generic language.","tags":["Sales operations","x402"],"examples":["A proposal answers scope and pricing but omits two required implementation questions."]},{"id":"SUST-PIPELINE-DEPENDENCY-001","name":"Pipeline Dependency Map","description":"Map supplied sales opportunities to shared people, approvals, references, pricing inputs, and delivery capacity. Identify pipeline bottlenecks without forecasting win rates.","tags":["Sales operations","x402"],"examples":["Several active proposals all require founder pricing approval before they can be sent."]},{"id":"SUST-FOLLOWUP-INTEGRITY-001","name":"Follow-Up Integrity Check","description":"Check whether supplied outreach, commitments, promised materials, buyer questions, and next steps have documented follow-up and return evidence. Sending a message alone is not closure.","tags":["Sales operations","x402"],"examples":["A prospect asked for pricing and references, but only the pricing email was sent."]},{"id":"SUST-PROGRAM-DEPENDENCY-001","name":"Program Dependency Map","description":"Map supplied projects, milestones, shared resources, approvals, and deliverables into a program-level dependency graph. Preserve uncertain dependencies as uncertain.","tags":["Program delivery","x402"],"examples":["Three projects share one data migration and one executive approval milestone."]},{"id":"SUST-MILESTONE-PROOF-001","name":"Milestone Proof Check","description":"Test whether a supplied milestone claim has evidence for its required deliverables, approvals, dependencies, and verification. Calendar passage alone is not milestone completion.","tags":["Program delivery","x402"],"examples":["A phase is marked complete even though the acceptance signoff is missing."]},{"id":"SUST-CRITICAL-PATH-001","name":"Critical Path Evidence Map","description":"Use supplied dependencies and durations or timing constraints to identify the evidence-supported path most likely to control completion. Do not invent durations or certainty.","tags":["Program delivery","x402"],"examples":["A program has dependencies but several task durations are unknown."]},{"id":"SUST-DECISION-LOG-001","name":"Decision Log Integrity Check","description":"Check whether supplied decisions preserve date, decision owner, rationale, source evidence, affected scope, and downstream updates. Do not infer rationale that was not recorded.","tags":["Program delivery","x402"],"examples":["A team changed vendors but the decision record contains no rationale or affected deliverables."]},{"id":"SUST-CHANGE-IMPACT-001","name":"Change Impact Map","description":"Trace a supplied proposed change across scope, schedule, cost states, roles, systems, client commitments, and verification needs. Separate direct effects from hypotheses.","tags":["Program delivery","x402"],"examples":["A platform migration changes authentication, training, reporting, and client onboarding."]},{"id":"SUST-KNOWLEDGE-SOURCE-MAP-001","name":"Knowledge Source Map","description":"Map where supplied operational knowledge currently lives across people, documents, systems, messages, and tacit practice. Distinguish canonical from informal sources.","tags":["Knowledge systems","x402"],"examples":["Critical procedures are split between a wiki, chat threads, and one employee's notes."]},{"id":"SUST-DUPLICATE-KNOWLEDGE-001","name":"Duplicate Knowledge Conflict Check","description":"Find duplicated supplied guidance that differs in wording, dates, ownership, or instruction. Preserve versions and identify which authority is needed to reconcile them.","tags":["Knowledge systems","x402"],"examples":["Two SOPs describe different approval steps for the same workflow."]},{"id":"SUST-RETRIEVAL-READINESS-001","name":"Retrieval Readiness Check","description":"Assess whether supplied knowledge is structured enough to retrieve reliably by topic, entity, date, authority, and provenance. Do not claim search quality without retrieval tests.","tags":["Knowledge systems","x402"],"examples":["A document repository has files but no consistent metadata or canonical status."]},{"id":"SUST-RAG-GROUNDING-001","name":"RAG Grounding Check","description":"Evaluate supplied retrieval outputs and answers for source coverage, citation support, stale context, contradictory retrieval, and unsupported synthesis. Do not assume the retriever saw documents not supplied.","tags":["Knowledge systems","x402"],"examples":["A RAG answer cites two documents but makes a conclusion neither source contains."]},{"id":"SUST-MEMORY-BOUNDARY-001","name":"Memory Boundary Check","description":"Compare supplied remembered facts, canonical records, and current source evidence to identify what should remain contextual, what is stale, and what requires explicit reconciliation. Do not overwrite memory or canon.","tags":["Knowledge systems","x402"],"examples":["An assistant remembers an old contact route that conflicts with the current operating record."]},{"id":"SUST-TAXONOMY-COHERENCE-001","name":"Taxonomy Coherence Check","description":"Check supplied categories, labels, and naming conventions for overlap, ambiguity, inconsistent granularity, and routing confusion. Do not rename governed terms without approval.","tags":["Knowledge systems","x402"],"examples":["A workspace uses project, workstream, initiative, and program inconsistently."]},{"id":"SUST-METADATA-COVERAGE-001","name":"Metadata Coverage Map","description":"Map which required metadata fields are present across supplied records and where missing metadata blocks retrieval, governance, routing, or lineage. Do not infer metadata from file names unless instructed.","tags":["Knowledge systems","x402"],"examples":["A document set has titles and dates but lacks owner, status, and source lineage metadata."]},{"id":"SUST-BID-READINESS-001","name":"Bid Readiness Check","description":"Compare supplied solicitation requirements with documented business capabilities, registrations, certifications, past performance, staffing, and submission components. Separate eligibility from competitiveness and do not infer current registration status without dated evidence.","tags":["Procurement and contracting","x402"],"examples":["A company wants to bid but has not reconciled the solicitation against its current registrations and proof."]},{"id":"SUST-SOLICITATION-DECOMPOSE-001","name":"Solicitation Requirement Decomposer","description":"Break a supplied solicitation into mandatory requirements, rated factors, attachments, dates, dependencies, and submission proof. Do not answer unstated requirements.","tags":["Procurement and contracting","x402"],"examples":["An RFP mixes mandatory forms, technical questions, and evaluation factors across several sections."]},{"id":"SUST-SUBCONTRACTOR-GAP-001","name":"Subcontractor Coverage Map","description":"Map supplied prime requirements against documented subcontractor capabilities, responsibilities, and evidence. Identify uncovered scope without inventing partner qualifications.","tags":["Procurement and contracting","x402"],"examples":["A prime proposal covers management and training but lacks a documented cybersecurity delivery partner."]},{"id":"SUST-PAST-PERFORMANCE-001","name":"Past Performance Evidence Map","description":"Map supplied prior work to current opportunity requirements using documented scope, outcomes, client type, period, and proof. Do not embellish similarity or results.","tags":["Procurement and contracting","x402"],"examples":["A proposal claims relevant experience but the source material does not clearly connect the projects to the new scope."]},{"id":"SUST-COMPLIANCE-EVIDENCE-001","name":"Compliance Evidence Map","description":"Map supplied rules or control requirements to documentary evidence, owners, processes, and verification records. Do not certify legal or regulatory compliance.","tags":["Compliance evidence","x402"],"examples":["A policy says access is reviewed quarterly, but no review evidence is attached."]},{"id":"SUST-POLICY-VERSION-001","name":"Policy Version Integrity Check","description":"Compare supplied policy versions, effective dates, owners, approvals, and supersession statements. Preserve conflicting versions and do not assume the newest file name is authoritative.","tags":["Compliance evidence","x402"],"examples":["Two policy files have different approval dates and no clear supersession note."]},{"id":"SUST-CONTROL-EVIDENCE-AGING-001","name":"Control Evidence Aging Check","description":"Check whether supplied control evidence is recent enough for the stated review period and whether recurring evidence is missing. Age alone does not prove failure.","tags":["Compliance evidence","x402"],"examples":["A quarterly control has evidence for Q1 and Q2 but nothing for Q3."]},{"id":"SUST-ATTESTATION-GAP-001","name":"Attestation Gap Check","description":"Compare supplied attestation statements with the underlying evidence they rely on. Identify claims that exceed the supplied record and do not draft certifications as true without support.","tags":["Compliance evidence","x402"],"examples":["A management attestation says all controls operated effectively, but two controls have no evidence."]},{"id":"SUST-CUSTOMER-INTENT-001","name":"Customer Intent Map","description":"Map supplied customer messages into goals, constraints, questions, commitments, urgency, and unresolved intent. Do not infer sentiment beyond the supplied language.","tags":["Customer operations","x402"],"examples":["A customer email contains a complaint, a feature request, and a deadline in the same thread."]},{"id":"SUST-COMPLAINT-ROOT-MAP-001","name":"Complaint Root Evidence Map","description":"Map supplied complaints to documented events, handoffs, promises, system states, and recurrence. Separate customer accounts from verified causes.","tags":["Customer operations","x402"],"examples":["Several customers report late updates, but the workflow evidence is incomplete."]},{"id":"SUST-SUPPORT-HANDOFF-001","name":"Support Handoff Integrity Check","description":"Check whether a customer issue moving between teams preserves context, ownership, commitments, priority, and return instructions. Do not assume receipt unless evidenced.","tags":["Customer operations","x402"],"examples":["A support case moves from sales to operations without the promised delivery date."]},{"id":"SUST-RESOLUTION-PROOF-001","name":"Customer Resolution Proof Check","description":"Test whether a supplied customer issue is actually resolved using correction evidence, customer communication, verification, and recurrence status. Closed status alone is not proof.","tags":["Customer operations","x402"],"examples":["A ticket is marked resolved after a configuration change, but nobody checked whether the customer can now complete the task."]},{"id":"SUST-DATA-COMPLETENESS-001","name":"Data Completeness Check","description":"Assess supplied structured records for required-field coverage, missing values, incomplete periods, and decision-critical gaps. Do not infer missing values.","tags":["Data quality","x402"],"examples":["A customer export has names and emails but many records lack status and source fields."]},{"id":"SUST-DATA-CONSISTENCY-001","name":"Data Consistency Check","description":"Find conflicting values, formats, identifiers, and definitions across supplied datasets or records. Preserve source-level differences rather than forcing reconciliation.","tags":["Data quality","x402"],"examples":["The same customer has different status values in CRM and billing records."]},{"id":"SUST-METRIC-DEFINITION-001","name":"Metric Definition Integrity Check","description":"Compare supplied metric names, formulas, filters, periods, and inclusion rules. Identify where the same label represents different calculations.","tags":["Data quality","x402"],"examples":["Two dashboards both show active customers but use different date and status filters."]},{"id":"SUST-DATASET-LINEAGE-001","name":"Dataset Lineage Map","description":"Trace supplied datasets through sources, transformations, joins, filters, and outputs using documented steps only. Unknown transformations remain unknown.","tags":["Data quality","x402"],"examples":["A report is built from three exports and a spreadsheet, but one transformation step is undocumented."]},{"id":"SUST-DUPLICATE-RECORD-001","name":"Duplicate Record Risk Check","description":"Identify likely duplicate supplied records using explicit identifiers and documented matching fields. Do not merge or delete records automatically.","tags":["Data quality","x402"],"examples":["A contact list contains repeated names with slightly different emails and no stable customer ID."]},{"id":"SUST-ROLE-CLARITY-001","name":"Role Clarity Check","description":"Compare supplied responsibilities, decision rights, recurring work, and handoffs across roles to identify overlap, gaps, and unclear ownership. Do not infer performance.","tags":["Organizational design","x402"],"examples":["Two managers both approve exceptions while routine ownership is unclear."]},{"id":"SUST-SPAN-OF-CONTROL-001","name":"Span of Control Evidence Map","description":"Map supplied reporting relationships, work complexity, decision load, and coordination demands. Do not prescribe an ideal span without relevant context.","tags":["Organizational design","x402"],"examples":["One manager has twelve direct reports across very different functions."]},{"id":"SUST-DECISION-BOTTLENECK-001","name":"Decision Bottleneck Map","description":"Identify documented decisions concentrated in a person or role that delay downstream work. Separate actual wait evidence from assumptions about leadership.","tags":["Organizational design","x402"],"examples":["Multiple teams wait for one executive to approve routine exceptions."]},{"id":"SUST-ORG-INTERFACE-001","name":"Organizational Interface Map","description":"Map where teams, functions, vendors, or partners exchange work, decisions, data, and accountability. Identify weak interfaces without assuming internal conflict.","tags":["Organizational design","x402"],"examples":["Sales, delivery, and billing each hold different parts of the customer handoff."]},{"id":"SUST-ROLE-WORKFIT-001","name":"Role-to-Work Fit Check","description":"Compare supplied role definitions with the work actually documented as performed. Identify scope expansion, invisible work, and missing authority without evaluating individual worth.","tags":["Organizational design","x402"],"examples":["A coordinator routinely manages escalations and approvals not listed in the job description."]},{"id":"SUST-MEETING-GOVERNANCE-001","name":"Meeting Governance Check","description":"Assess supplied recurring meetings for purpose, decision rights, inputs, outputs, ownership, and closure. Do not assume meetings are unnecessary solely from frequency.","tags":["Organizational design","x402"],"examples":["A weekly operations meeting generates discussion but no decision or action record."]},{"id":"SUST-OPERATING-CADENCE-001","name":"Operating Cadence Map","description":"Map supplied daily, weekly, monthly, and event-driven operating rhythms to their inputs, decisions, outputs, and dependencies. Identify missing cadence links.","tags":["Organizational design","x402"],"examples":["The business has weekly sales and monthly finance reviews but no cadence connecting delivery risk to either."]},{"id":"SUST-MARKET-SIGNAL-MAP-001","name":"Market Signal Map","description":"Organize supplied market signals by source, date, relevance, direction, and confidence. Separate observed signals from interpretation and do not infer demand from isolated anecdotes.","tags":["Market intelligence","x402"],"examples":["A founder has customer comments, competitor moves, and search data but no structured view of what they collectively indicate."]},{"id":"SUST-COMPETITOR-EVIDENCE-001","name":"Competitor Evidence Check","description":"Map supplied competitor claims to evidence about offer, customer, pricing, channel, positioning, and operating model. Do not invent competitor facts or current pricing.","tags":["Market intelligence","x402"],"examples":["A strategy document describes three competitors but only one has documented pricing and service scope."]},{"id":"SUST-SEGMENT-FIT-001","name":"Customer Segment Fit Map","description":"Compare supplied customer segments against documented needs, buying conditions, delivery fit, and evidence. Keep attractive-but-unsupported segments distinct from validated ones.","tags":["Market intelligence","x402"],"examples":["A company is considering enterprise, small business, and government buyers with uneven evidence across each segment."]},{"id":"SUST-POSITIONING-PROOF-001","name":"Positioning Proof Check","description":"Test whether supplied positioning claims are supported by customer evidence, capabilities, outcomes, or differentiated operating methods. Do not treat slogans as proof.","tags":["Market intelligence","x402"],"examples":["A company says it is faster and more strategic than alternatives but has not connected those claims to evidence."]},{"id":"SUST-CHANNEL-DEPENDENCY-001","name":"Go-to-Market Channel Dependency Map","description":"Map supplied acquisition channels to required assets, people, approvals, content, partners, and conversion evidence. Do not forecast channel performance without data.","tags":["Market intelligence","x402"],"examples":["A launch plan depends on LinkedIn, referrals, and paid search but has no documented owner or asset readiness."]},{"id":"SUST-EXPERIMENT-DESIGN-001","name":"Experiment Design Check","description":"Evaluate supplied experiments for hypothesis, variable, audience, success measure, timebox, stopping rule, and learning objective. Do not claim statistical significance without appropriate data.","tags":["Experimentation","x402"],"examples":["A team wants to test a new offer but has no success threshold or comparison condition."]},{"id":"SUST-EXPERIMENT-LEARNING-001","name":"Experiment Learning Capture","description":"Map supplied experiment results to the original hypothesis, observed outcomes, confounders, decisions, and next tests. Do not turn ambiguous results into certainty.","tags":["Experimentation","x402"],"examples":["A pilot generated interest but the team cannot tell whether pricing, audience, or messaging caused the result."]},{"id":"SUST-ASSUMPTION-TEST-PRIORITY-001","name":"Assumption Test Priority Map","description":"Rank supplied assumptions by dependency impact, uncertainty, and reversibility using documented evidence only. Recommendations are test priorities, not guarantees.","tags":["Experimentation","x402"],"examples":["A new service depends on assumptions about demand, delivery time, pricing, and staffing."]},{"id":"SUST-PILOT-READINESS-001","name":"Pilot Readiness Check","description":"Check whether a supplied pilot has a defined scope, target participants, operating constraints, measures, support path, failure recovery, and exit criteria.","tags":["Experimentation","x402"],"examples":["A team wants to start a client pilot without defined success measures or support ownership."]},{"id":"SUST-PILOT-TO-SCALE-001","name":"Pilot-to-Scale Evidence Map","description":"Map supplied pilot evidence against the conditions required to scale: repeatability, capacity, quality, economics, governance, and support. Do not generalize beyond the evidence.","tags":["Experimentation","x402"],"examples":["A pilot worked with three customers but relied heavily on founder intervention."]},{"id":"SUST-SECURITY-CONTROL-MAP-001","name":"Security Control Evidence Map","description":"Map supplied security requirements to documented controls, owners, evidence, and gaps. Do not certify cybersecurity compliance or security posture.","tags":["Security governance","x402"],"examples":["A system requires access control, backups, and logging but only logging evidence is documented."]},{"id":"SUST-ACCESS-BOUNDARY-001","name":"Access Boundary Check","description":"Compare supplied users, roles, systems, and permissions to documented access needs and authority. Identify excessive, missing, or ambiguous access without changing permissions.","tags":["Security governance","x402"],"examples":["A contractor retains broad system access after the project scope changed."]},{"id":"SUST-CREDENTIAL-RISK-001","name":"Credential Dependency Map","description":"Map supplied credentials, owners, storage, rotation, recovery, and dependent systems. Identify documented concentration and recovery gaps without exposing secrets.","tags":["Security governance","x402"],"examples":["One administrator controls several production credentials with no documented recovery owner."]},{"id":"SUST-INCIDENT-READINESS-001","name":"Incident Response Readiness Check","description":"Assess supplied incident procedures for detection, classification, authority, containment, communication, evidence preservation, recovery, and closure. Do not provide offensive security guidance.","tags":["Security governance","x402"],"examples":["An organization has an incident contact list but no documented classification or recovery process."]},{"id":"SUST-PRIVACY-DATAFLOW-001","name":"Privacy Data Flow Map","description":"Map supplied personal or sensitive data through collection, use, storage, sharing, retention, and deletion points. Do not make legal compliance determinations.","tags":["Privacy governance","x402"],"examples":["Customer information moves from intake forms to CRM, spreadsheets, and vendors with unclear retention rules."]},{"id":"SUST-CONSENT-EVIDENCE-001","name":"Consent Evidence Check","description":"Compare supplied consent requirements to records of notice, choice, scope, timing, and withdrawal handling. Do not infer valid consent when evidence is missing.","tags":["Privacy governance","x402"],"examples":["A workflow stores customer data but cannot show when or how permission was captured."]},{"id":"SUST-RETENTION-BOUNDARY-001","name":"Retention Boundary Map","description":"Map supplied record types to documented retention periods, business purposes, deletion triggers, and exceptions. Unknown requirements remain unknown.","tags":["Privacy governance","x402"],"examples":["Client files are kept indefinitely because no retention rule is documented."]},{"id":"SUST-VENDOR-DATA-RISK-001","name":"Vendor Data Dependency Check","description":"Map supplied vendor data exchanges, purposes, access, retention expectations, and return or deletion obligations. Do not infer contractual protections not supplied.","tags":["Privacy governance","x402"],"examples":["A software vendor receives client information but the supplied agreement does not address deletion."]},{"id":"SUST-INTEGRATION-CONTRACT-001","name":"Integration Contract Check","description":"Check supplied system integrations for required fields, identifiers, authentication assumptions, failure responses, retries, ownership, and verification. Do not call live systems.","tags":["Technical operations","x402"],"examples":["Two systems exchange customer status but disagree on identifiers and retry behavior."]},{"id":"SUST-API-DEPENDENCY-001","name":"API Dependency Risk Map","description":"Map supplied API dependencies to consumers, authentication, limits, failure behavior, fallback, and business impact. Do not test or probe external APIs.","tags":["Technical operations","x402"],"examples":["A client workflow depends on one third-party API with no documented fallback."]},{"id":"SUST-DEPLOYMENT-PROOF-001","name":"Deployment Evidence Check","description":"Test whether supplied deployment records prove build, release, environment, verification, rollback readiness, and owner acceptance. A successful CI job alone is not production proof.","tags":["Technical operations","x402"],"examples":["A pull request merged and CI passed, but nobody confirmed the production endpoint."]},{"id":"SUST-CONFIG-DRIFT-001","name":"Configuration Drift Check","description":"Compare supplied configuration snapshots, environment settings, or deployment records to identify documented drift and its downstream effects. Do not expose secret values.","tags":["Technical operations","x402"],"examples":["Production and staging behave differently, but their environment configuration has not been reconciled."]},{"id":"SUST-INTEGRATION-RECOVERY-001","name":"Integration Recovery Map","description":"Map how supplied integrations recover from timeouts, partial writes, duplicate events, stale state, and downstream rejection. Identify missing reconciliation paths.","tags":["Technical operations","x402"],"examples":["A webhook can time out after the downstream system updates, creating uncertain retry behavior."]},{"id":"SUST-RELEASE-READINESS-001","name":"Release Readiness Gate","description":"Compare a supplied release against explicit requirements for tests, approvals, configuration, rollback, observability, documentation, support, and live verification. Do not release or deploy anything.","tags":["Technical operations","x402"],"examples":["A new service passes unit tests but lacks production configuration, rollback evidence, and support ownership."]},{"id":"SUST-CONTRACT-OBLIGATION-MAP-001","name":"Contract Obligation Map","description":"Map supplied contract obligations to responsible parties, dates, dependencies, evidence, and closure conditions. Do not provide legal interpretation beyond the supplied language.","tags":["Contract operations","x402"],"examples":["A services agreement contains deliverables, notice duties, and renewal terms spread across several sections."]},{"id":"SUST-CONTRACT-CHANGE-001","name":"Contract Change Impact Check","description":"Trace a supplied contract amendment or proposed change across scope, timing, price states, responsibilities, dependencies, and downstream records. Do not infer enforceability.","tags":["Contract operations","x402"],"examples":["A client amendment adds services but does not clarify how the schedule or acceptance terms change."]},{"id":"SUST-RENEWAL-READINESS-001","name":"Renewal Readiness Check","description":"Check supplied agreements for renewal dates, notice windows, performance evidence, pricing decisions, open obligations, and required approvals. Do not assume automatic renewal when language is unclear.","tags":["Contract operations","x402"],"examples":["A vendor contract may renew next month, but notice dates and performance review are not consolidated."]},{"id":"SUST-NOTICE-OBLIGATION-001","name":"Notice Obligation Check","description":"Map supplied notice requirements to trigger events, recipients, method, timing, and evidence. Do not send notices or determine legal sufficiency.","tags":["Contract operations","x402"],"examples":["A contract requires written notice after certain events, but the workflow does not track when notice is due."]},{"id":"SUST-VENDOR-PERFORMANCE-001","name":"Vendor Performance Evidence Map","description":"Map supplied vendor commitments to delivery records, defects, delays, communication, and acceptance evidence. Separate documented performance from opinion.","tags":["Vendor management","x402"],"examples":["A vendor is described as unreliable, but the records are scattered across tickets and emails."]},{"id":"SUST-VENDOR-DEPENDENCY-001","name":"Vendor Dependency Concentration Map","description":"Identify supplied operations that rely heavily on one vendor, product, geography, or capability. Do not predict vendor failure.","tags":["Vendor management","x402"],"examples":["One software provider supports intake, billing, and reporting with no documented alternative."]},{"id":"SUST-VENDOR-ONBOARDING-001","name":"Vendor Onboarding Readiness Check","description":"Check whether a supplied vendor onboarding process includes scope, authority, access, data handling, contacts, acceptance, escalation, and offboarding conditions.","tags":["Vendor management","x402"],"examples":["A new contractor has access and a start date but no documented escalation or offboarding plan."]},{"id":"SUST-VENDOR-EXIT-001","name":"Vendor Exit Readiness Map","description":"Map supplied vendor exit dependencies including data return, credentials, assets, replacement timing, open invoices, ownership, and service continuity. Do not terminate agreements.","tags":["Vendor management","x402"],"examples":["A business wants to replace a software vendor but has not mapped data export or cutover dependencies."]},{"id":"SUST-MESSAGE-INTENT-001","name":"Message Intent and Commitment Map","description":"Extract supplied messages into requests, questions, decisions, commitments, deadlines, and unresolved issues while preserving speaker attribution.","tags":["Communications","x402"],"examples":["A long email thread contains several decisions and promises mixed with background discussion."]},{"id":"SUST-COMMUNICATION-CONTRADICTION-001","name":"Communication Contradiction Check","description":"Find where supplied messages give conflicting instructions, dates, commitments, or status updates. Preserve each account and identify what authority is needed to reconcile them.","tags":["Communications","x402"],"examples":["Two managers sent different launch dates to the same team."]},{"id":"SUST-RESPONSE-OBLIGATION-001","name":"Response Obligation Map","description":"Identify supplied messages that require a response, decision, document, acknowledgement, or follow-up. Do not infer urgency beyond explicit context.","tags":["Communications","x402"],"examples":["An inbox contains requests, approvals, and FYI messages mixed together."]},{"id":"SUST-EXECUTIVE-BRIEF-001","name":"Executive Brief Integrity Check","description":"Check whether a supplied executive brief clearly distinguishes facts, decisions, risks, asks, dependencies, and unknowns. Do not compress away material uncertainty.","tags":["Communications","x402"],"examples":["A status memo is concise but hides unresolved dependencies behind a green status."]},{"id":"SUST-BRAND-CLAIM-PROOF-001","name":"Brand Claim Proof Check","description":"Map supplied brand claims to documented capabilities, evidence, customer outcomes, or approved positioning. Do not treat aspirational language as proven fact.","tags":["Brand integrity","x402"],"examples":["A company says it is enterprise-ready and fastest-in-market without evidence attached."]},{"id":"SUST-BRAND-CONSISTENCY-001","name":"Brand Consistency Check","description":"Compare supplied brand assets and copy for naming, tone, visual instructions, claims, audience, and approved terminology. Do not invent brand rules.","tags":["Brand integrity","x402"],"examples":["A website, proposal, and social profile use different taglines and company descriptions."]},{"id":"SUST-OFFER-CLAIM-ALIGNMENT-001","name":"Offer-to-Brand Alignment Check","description":"Compare a supplied offer with approved brand positioning, audience, scope, and evidence. Identify where the offer overreaches or drifts from the brand.","tags":["Brand integrity","x402"],"examples":["A new service promises outcomes that are broader than the approved company positioning."]},{"id":"SUST-PUBLIC-COPY-RISK-001","name":"Public Copy Evidence Check","description":"Review supplied public-facing copy for unsupported factual claims, unclear qualifiers, inconsistent promises, and missing evidence. Do not provide legal advertising clearance.","tags":["Brand integrity","x402"],"examples":["A homepage contains performance and certification claims that are not linked to proof."]},{"id":"SUST-PORTFOLIO-FIT-001","name":"Portfolio Fit Map","description":"Compare supplied projects, products, clients, or assets against documented strategic goals, constraints, capabilities, and resource demands. Do not assign financial value without data.","tags":["Portfolio strategy","x402"],"examples":["A business has several offerings but no clear view of which ones fit its stated strategic direction."]},{"id":"SUST-PORTFOLIO-OVERLAP-001","name":"Portfolio Overlap Check","description":"Identify supplied offerings or initiatives that overlap in customer, capability, workflow, messaging, or resource use. Overlap is not automatically duplication.","tags":["Portfolio strategy","x402"],"examples":["Three internal initiatives appear to solve similar workflow problems for different teams."]},{"id":"SUST-PORTFOLIO-DEPENDENCY-001","name":"Portfolio Dependency Map","description":"Map supplied portfolio items to shared people, systems, funding, vendors, and approvals. Identify concentration and sequencing dependencies.","tags":["Portfolio strategy","x402"],"examples":["Multiple offerings depend on the same founder approval and delivery platform."]},{"id":"SUST-ASSET-PRIORITY-001","name":"Asset Priority Map","description":"Rank supplied assets or initiatives by documented strategic importance, dependency impact, urgency, and evidence quality. Do not assign unsupported monetary value.","tags":["Portfolio strategy","x402"],"examples":["A company must decide which digital assets to stabilize first after several failures."]},{"id":"SUST-CAPABILITY-INVENTORY-001","name":"Capability Inventory Map","description":"Map supplied organizational capabilities to people, systems, process evidence, customers served, and maturity indicators. Do not infer capability from job title alone.","tags":["Capability strategy","x402"],"examples":["A company claims research, implementation, and analytics capabilities but evidence is uneven."]},{"id":"SUST-CAPABILITY-GAP-001","name":"Capability Gap Check","description":"Compare supplied strategic goals or requirements against documented current capabilities. Separate build, buy, partner, and unknown options without prescribing a choice as fact.","tags":["Capability strategy","x402"],"examples":["A growth plan requires 24-hour support, but the current operating model has no support coverage."]},{"id":"SUST-CAPABILITY-DEPENDENCY-001","name":"Capability Dependency Map","description":"Trace supplied capabilities to prerequisite skills, tools, data, governance, vendors, and operating routines. Identify hidden dependencies.","tags":["Capability strategy","x402"],"examples":["An analytics service depends on clean data, subject-matter review, and reporting infrastructure."]},{"id":"SUST-CAPABILITY-REPLICATION-001","name":"Capability Replication Check","description":"Compare two supplied implementations of the same claimed capability to determine whether the underlying process, evidence, and outcomes are actually reproducible. Appearance alone is insufficient.","tags":["Capability strategy","x402"],"examples":["A workflow works for one client but fails when reused for another because hidden assumptions changed."]},{"id":"SUST-WORKFORCE-DEMAND-MAP-001","name":"Workforce Demand Map","description":"Map supplied work demand to roles, skills, timing, workload, and capacity evidence. Do not infer headcount need without documented work volume or service requirements.","tags":["Workforce planning","x402"],"examples":["A company expects growth but has not connected projected work to staffing needs."]},{"id":"SUST-HIRING-READINESS-001","name":"Hiring Readiness Check","description":"Check whether a supplied role has clear work, outcomes, authority, dependencies, budget state, onboarding needs, and acceptance criteria before hiring begins.","tags":["Workforce planning","x402"],"examples":["A founder wants to hire an operations manager but the role still mixes strategy, admin, and approvals."]},{"id":"SUST-CANDIDATE-EVIDENCE-MAP-001","name":"Candidate Evidence Map","description":"Map supplied candidate evidence to explicit role requirements using documented experience, work samples, credentials, and interview evidence. Do not infer personal traits or protected characteristics.","tags":["Workforce planning","x402"],"examples":["A candidate appears strong overall but evidence is uneven across the role's required capabilities."]},{"id":"SUST-ONBOARDING-DEPENDENCY-001","name":"Onboarding Dependency Map","description":"Map supplied onboarding tasks to access, training, equipment, policies, managers, and proof of readiness. Identify sequencing gaps without granting access.","tags":["Workforce planning","x402"],"examples":["A new hire starts Monday but system access, training, and approval authority are not sequenced."]},{"id":"SUST-SERVICE-BLUEPRINT-001","name":"Service Blueprint Map","description":"Map supplied customer actions, frontstage work, backstage work, systems, evidence, and handoffs into a service blueprint. Do not invent customer behavior.","tags":["Service design","x402"],"examples":["A consulting service has clear deliverables but no mapped customer journey or backstage workflow."]},{"id":"SUST-SERVICE-BOUNDARY-001","name":"Service Boundary Check","description":"Check whether a supplied service clearly defines included work, excluded work, client responsibilities, handoffs, escalation, and completion conditions.","tags":["Service design","x402"],"examples":["A support offer says unlimited help but does not define what is outside scope."]},{"id":"SUST-SERVICE-FAILURE-POINT-001","name":"Service Failure Point Map","description":"Identify documented points where a service can fail due to missing inputs, handoffs, system states, authority, or verification. Separate observed failures from potential ones.","tags":["Service design","x402"],"examples":["Client delivery repeatedly breaks at intake and approval handoffs."]},{"id":"SUST-EXPERIENCE-CONSISTENCY-001","name":"Customer Experience Consistency Check","description":"Compare supplied service instances against intended experience standards, promises, handoffs, and completion rules. Do not infer customer satisfaction without evidence.","tags":["Service design","x402"],"examples":["Different clients receive different onboarding steps for the same service."]},{"id":"SUST-PRICE-LOGIC-001","name":"Pricing Logic Check","description":"Map supplied pricing to documented scope, effort, value logic, cost states, risk, and customer conditions. Do not invent willingness-to-pay or market benchmarks.","tags":["Pricing and commercial","x402"],"examples":["A service has a flat price but no documented connection to scope or delivery effort."]},{"id":"SUST-DISCOUNT-CONTROL-001","name":"Discount Control Check","description":"Check supplied discount decisions for authority, rationale, conditions, duration, and downstream margin or precedent evidence. Do not approve pricing changes.","tags":["Pricing and commercial","x402"],"examples":["Sales staff can discount proposals without documented approval thresholds."]},{"id":"SUST-COMMERCIAL-TERM-001","name":"Commercial Term Dependency Map","description":"Map supplied commercial terms such as payment timing, deposits, renewal, minimums, and acceptance to operational dependencies and delivery risk.","tags":["Pricing and commercial","x402"],"examples":["A contract allows delayed payment but delivery requires large upfront vendor costs."]},{"id":"SUST-UNIT-ECONOMICS-EVIDENCE-001","name":"Unit Economics Evidence Check","description":"Check whether supplied unit economics have complete revenue, direct cost, variable cost, allocation assumptions, and volume basis. Do not calculate unsupported profitability.","tags":["Pricing and commercial","x402"],"examples":["A service appears profitable, but labor and rework costs are incomplete."]},{"id":"SUST-DOCUMENT-AUTHORITY-001","name":"Document Authority Map","description":"Map supplied documents to owner, approver, effective date, canonical status, supersession, and intended audience. Do not declare authority without evidence.","tags":["Document control","x402"],"examples":["Several SOPs exist, but staff do not know which version controls."]},{"id":"SUST-DOCUMENT-CHANGE-001","name":"Document Change Impact Map","description":"Trace a supplied document change to affected workflows, training, systems, clients, forms, and downstream records.","tags":["Document control","x402"],"examples":["A policy update changes an approval step but related forms and training remain unchanged."]},{"id":"SUST-RECORD-COMPLETENESS-001","name":"Record Completeness Check","description":"Check supplied records for required fields, signatures or approvals where documented, dates, attachments, and closure evidence. Do not infer missing records.","tags":["Document control","x402"],"examples":["A case file contains correspondence and invoices but lacks final acceptance evidence."]},{"id":"SUST-DOCUMENT-ROUTING-001","name":"Document Routing Check","description":"Map supplied documents to where they should be created, reviewed, approved, stored, shared, and archived based on supplied governance rules.","tags":["Document control","x402"],"examples":["A client deliverable is reviewed in email, stored in Drive, and archived elsewhere without a clear canonical route."]},{"id":"SUST-FOUNDER-DEPENDENCY-001","name":"Founder Dependency Map","description":"Identify supplied decisions, approvals, relationships, knowledge, and workflows that depend disproportionately on the founder. Separate necessary founder authority from avoidable dependency.","tags":["Founder operating system","x402"],"examples":["Most client, pricing, and delivery decisions still route through the founder."]},{"id":"SUST-FOUNDER-ATTENTION-001","name":"Founder Attention Allocation Map","description":"Map supplied founder work across strategic, operational, administrative, approval, recovery, and relationship categories. Do not infer productivity from time alone.","tags":["Founder operating system","x402"],"examples":["A founder spends most of the week resolving operational exceptions while strategic work is delayed."]},{"id":"SUST-DECISION-LOAD-001","name":"Leadership Decision Load Map","description":"Map supplied recurring decisions by leader, frequency, reversibility, required context, and downstream impact. Identify concentration without judging leadership quality.","tags":["Founder operating system","x402"],"examples":["One executive approves hiring, pricing, client exceptions, and vendor changes."]},{"id":"SUST-LEADERSHIP-HANDOFF-001","name":"Leadership Handoff Contract Check","description":"Check supplied leadership delegations for scope, authority, escalation, reporting, acceptance, and return conditions. Delegation is not complete if authority remains unclear.","tags":["Founder operating system","x402"],"examples":["A founder delegates operations but retains undocumented approval over most exceptions."]},{"id":"SUST-PRIORITY-CONFLICT-001","name":"Strategic Priority Conflict Map","description":"Identify supplied priorities that compete for the same time, money, people, or sequencing dependencies. Do not choose a winner without documented criteria.","tags":["Founder operating system","x402"],"examples":["A company wants to launch a new service, rebuild infrastructure, and expand sales at the same time."]},{"id":"SUST-INITIATIVE-STOP-001","name":"Initiative Stop/Continue Check","description":"Compare supplied initiatives against current goals, evidence, dependencies, sunk-work state, and remaining value questions. Do not recommend termination without stating uncertainty.","tags":["Founder operating system","x402"],"examples":["Several internal projects remain open because no one has decided whether they still matter."]},{"id":"SUST-OPERATING-REVIEW-001","name":"Operating Review Integrity Check","description":"Check whether a supplied operating review connects metrics, risks, decisions, commitments, owners, and closure evidence rather than only reporting status.","tags":["Founder operating system","x402"],"examples":["A weekly review reports numbers but does not capture decisions or unresolved blockers."]},{"id":"SUST-LEADERSHIP-RETURN-LOOP-001","name":"Leadership Return Loop Check","description":"Check whether delegated work returns to leadership with the evidence needed for acceptance, decision, or closure. A completed task that never returns is not a closed leadership loop.","tags":["Founder operating system","x402"],"examples":["Managers complete work independently, but the founder cannot tell what changed or what still needs a decision."]},{"id":"SUST-PARTNER-FIT-MAP-001","name":"Partner Fit Map","description":"Compare supplied partner capabilities, goals, audience, authority, and operating model against a documented collaboration need. Do not infer strategic alignment without evidence.","tags":["Partnerships","x402"],"examples":["Two companies want to collaborate, but their roles, customers, and responsibilities are not clearly aligned."]},{"id":"SUST-PARTNER-OBLIGATION-001","name":"Partner Obligation Map","description":"Map supplied partner commitments to owners, dependencies, dates, evidence, and closure. Do not infer contractual obligations beyond supplied language.","tags":["Partnerships","x402"],"examples":["A referral partnership contains several promises but no shared obligation register."]},{"id":"SUST-PARTNER-HANDOFF-001","name":"Partner Handoff Integrity Check","description":"Check whether work or leads passed between partners preserve required context, ownership, attribution, deadlines, and return instructions.","tags":["Partnerships","x402"],"examples":["A partner sends leads but the receiving team does not retain source or follow-up expectations."]},{"id":"SUST-PARTNER-EXIT-001","name":"Partner Exit Readiness Map","description":"Map supplied partnership exit dependencies including customer communication, records, data, referrals, open obligations, assets, and replacement needs. Do not terminate relationships.","tags":["Partnerships","x402"],"examples":["A business wants to end a referral relationship but has not mapped open client obligations or shared data."]},{"id":"SUST-CLIENT-HEALTH-EVIDENCE-001","name":"Client Health Evidence Map","description":"Map supplied client health indicators to documented usage, delivery, issues, commitments, outcomes, and open risks. Do not invent satisfaction scores.","tags":["Client success","x402"],"examples":["A client is labeled at risk, but the underlying reasons are spread across delivery notes and support messages."]},{"id":"SUST-RENEWAL-RISK-001","name":"Client Renewal Risk Map","description":"Identify supplied renewal dependencies, unresolved issues, value evidence, decision timing, and commercial conditions. Do not predict renewal probability without data.","tags":["Client success","x402"],"examples":["A contract renews soon, but open issues and value evidence have not been reconciled."]},{"id":"SUST-SUCCESS-PLAN-001","name":"Client Success Plan Integrity Check","description":"Check whether a supplied success plan connects client goals, milestones, responsibilities, measures, risks, and closure evidence.","tags":["Client success","x402"],"examples":["A client plan lists goals and activities but no measures or decision points."]},{"id":"SUST-VALUE-PROOF-001","name":"Client Value Proof Map","description":"Map supplied client outcomes to baseline evidence, delivered changes, attribution limits, and supporting records. Do not claim value that cannot be traced.","tags":["Client success","x402"],"examples":["A case study claims improved operations but does not connect the outcome to specific evidence."]},{"id":"SUST-QA-COVERAGE-001","name":"QA Coverage Map","description":"Map supplied quality requirements to tests, reviews, checks, and evidence. Identify uncovered requirements without claiming defect-free performance.","tags":["Quality assurance","x402"],"examples":["A release has unit tests but several acceptance criteria have no quality check."]},{"id":"SUST-DEFECT-PATTERN-001","name":"Defect Pattern Map","description":"Group supplied defects by type, stage, source, recurrence, and dependency. Do not infer root cause without evidence.","tags":["Quality assurance","x402"],"examples":["Several recurring defects appear in different projects, but no one has mapped the shared pattern."]},{"id":"SUST-ACCEPTANCE-TEST-001","name":"Acceptance Test Integrity Check","description":"Check whether supplied acceptance tests map to requirements, expected outcomes, edge cases, and proof of execution. Do not mark acceptance without evidence.","tags":["Quality assurance","x402"],"examples":["A deliverable has acceptance criteria but no traceable test evidence."]},{"id":"SUST-REWORK-LOOP-001","name":"Rework Loop Map","description":"Trace supplied rework from defect discovery through correction, verification, return, and recurrence. Identify repeated loops and missing prevention controls.","tags":["Quality assurance","x402"],"examples":["A team repeatedly fixes the same class of issue without preventing recurrence."]},{"id":"SUST-CHANGE-ADOPTION-001","name":"Change Adoption Evidence Map","description":"Map supplied adoption evidence across awareness, understanding, capability, usage, support, and reinforcement. Do not infer employee attitudes.","tags":["Change management","x402"],"examples":["A new system launched, but only training attendance is tracked."]},{"id":"SUST-STAKEHOLDER-IMPACT-001","name":"Stakeholder Impact Map","description":"Trace a supplied change to affected roles, responsibilities, systems, incentives, communications, and dependencies. Separate direct impacts from hypotheses.","tags":["Change management","x402"],"examples":["A workflow redesign changes who approves, who enters data, and who handles exceptions."]},{"id":"SUST-CHANGE-COMMUNICATION-001","name":"Change Communication Coverage Check","description":"Check whether supplied change communications cover affected audiences, timing, required action, rationale, support, and feedback paths.","tags":["Change management","x402"],"examples":["Managers were told about a process change, but front-line users were not."]},{"id":"SUST-REINFORCEMENT-LOOP-001","name":"Change Reinforcement Loop Check","description":"Check whether a supplied change includes feedback, coaching, measurement, correction, and leadership return loops after launch.","tags":["Change management","x402"],"examples":["A new process was trained once but has no post-launch feedback or correction loop."]},{"id":"SUST-RESEARCH-TO-DECISION-001","name":"Research-to-Decision Trace","description":"Trace supplied research findings into claims, assumptions, options, decision criteria, and final decisions. Preserve uncertainty and do not invent missing reasoning.","tags":["Decision intelligence","x402"],"examples":["A market study exists, but the final recommendation does not show how the evidence shaped the choice."]},{"id":"SUST-EVIDENCE-WEIGHT-001","name":"Evidence Weight Map","description":"Classify supplied evidence by source type, independence, recency, relevance, and contradiction without turning the result into a false numeric certainty.","tags":["Decision intelligence","x402"],"examples":["A decision relies on one internal memo, two customer interviews, and an older external report."]},{"id":"SUST-OPTION-ELIMINATION-001","name":"Option Elimination Evidence Check","description":"Check whether rejected options have documented reasons, constraints, evidence, and decision criteria. Do not reconstruct reasons that were never recorded.","tags":["Decision intelligence","x402"],"examples":["A team selected one vendor but cannot explain why two alternatives were rejected."]},{"id":"SUST-DECISION-CONFIDENCE-001","name":"Decision Confidence Boundary Check","description":"Compare supplied decision certainty with the actual completeness, quality, contradiction, and freshness of supporting evidence. Do not assign probabilistic confidence without a defined method.","tags":["Decision intelligence","x402"],"examples":["Leadership is highly confident in a forecast despite several unresolved assumptions."]},{"id":"SUST-INSIGHT-ACTION-001","name":"Insight-to-Action Map","description":"Map supplied insights to decisions, actions, owners, dependencies, and verification. An insight that never changes work remains unclosed.","tags":["Decision intelligence","x402"],"examples":["A research report identifies several problems, but none are tied to implementation work."]},{"id":"SUST-DECISION-EXPIRY-001","name":"Decision Expiry Check","description":"Check whether supplied decisions still rest on current assumptions, evidence, constraints, and dates. Do not invalidate older decisions solely because of age.","tags":["Decision intelligence","x402"],"examples":["A pricing decision from last year still guides current work despite changed costs and scope."]},{"id":"SUST-RESEARCH-CLOSURE-001","name":"Research Closure Check","description":"Check whether a supplied research workstream has answered its stated question, documented unresolved gaps, connected findings to a decision, and archived evidence.","tags":["Decision intelligence","x402"],"examples":["A research project produced notes and sources but no explicit conclusion or decision handoff."]},{"id":"SUST-EVIDENCE-REFRESH-001","name":"Evidence Refresh Map","description":"Identify supplied decisions or claims that depend on evidence requiring periodic refresh. Map refresh triggers, owners, and downstream consumers.","tags":["Decision intelligence","x402"],"examples":["A market-entry recommendation depends on pricing and licensing evidence that changes over time."]},{"id":"SUST-GRANT-FIT-MAP-001","name":"Grant Fit Map","description":"Compare supplied grant requirements to documented organization eligibility, program fit, evidence, timing, and required attachments. Separate eligibility from competitiveness and do not predict award outcomes.","tags":["Funding and grants","x402"],"examples":["A nonprofit is considering a grant but has not reconciled program requirements with current documentation."]},{"id":"SUST-FUNDING-SOURCE-MAP-001","name":"Funding Source Dependency Map","description":"Map supplied funding sources to restrictions, timing, matching needs, reporting, and dependent activities. Do not infer funding availability without evidence.","tags":["Funding and grants","x402"],"examples":["A project depends on several funding sources with different restrictions and timing."]},{"id":"SUST-GRANT-EVIDENCE-001","name":"Grant Evidence Coverage Check","description":"Map supplied proposal claims to supporting data, records, outcomes, and attachments. Do not embellish impact or need.","tags":["Funding and grants","x402"],"examples":["A grant narrative makes community-impact claims that are only partly documented."]},{"id":"SUST-GRANT-REPORTING-001","name":"Grant Reporting Readiness Check","description":"Check whether supplied grant obligations have corresponding data sources, owners, cadence, evidence, and reporting proof. Do not create compliance certifications.","tags":["Funding and grants","x402"],"examples":["A funded program must report outcomes quarterly, but data ownership is unclear."]},{"id":"SUST-PROPERTY-LEASE-MAP-001","name":"Lease Obligation Map","description":"Map supplied lease obligations to parties, dates, notices, maintenance, payments, access, and evidence. Do not provide legal interpretation beyond supplied language.","tags":["Real estate operations","x402"],"examples":["A commercial lease contains maintenance, notice, and access obligations spread across sections."]},{"id":"SUST-TENANT-HANDOFF-001","name":"Tenant Handoff Integrity Check","description":"Check whether supplied tenant transitions preserve contacts, lease terms, open maintenance, payment state, access, notices, and communication responsibilities.","tags":["Real estate operations","x402"],"examples":["A property manager is taking over a tenant relationship while maintenance issues remain open."]},{"id":"SUST-PROPERTY-VENDOR-MAP-001","name":"Property Vendor Dependency Map","description":"Map supplied property operations to vendors, scopes, access, scheduling, approvals, and verification. Identify concentration without judging vendor competence.","tags":["Real estate operations","x402"],"examples":["One vendor handles roofing, emergency response, and inspections for several properties."]},{"id":"SUST-PROPERTY-READINESS-001","name":"Property Operations Readiness Check","description":"Check supplied property operations for tenant contacts, maintenance routes, vendor coverage, emergency procedures, records, payment routing, and owner approvals.","tags":["Real estate operations","x402"],"examples":["A new property-management engagement begins before vendor, tenant, and maintenance routing are fully documented."]},{"id":"SUST-LEGAL-FACT-MAP-001","name":"Legal Fact Pattern Map","description":"Organize supplied facts, dates, actors, documents, statements, and disputed points for attorney or self-help review. Do not provide legal advice or determine liability.","tags":["Legal document support","x402"],"examples":["A dispute involves emails, invoices, payments, and competing versions of events."]},{"id":"SUST-LEGAL-DOCUMENT-GAP-001","name":"Legal Document Gap Check","description":"Inventory supplied legal or dispute-related documents and identify missing referenced exhibits, notices, signatures, dates, and evidence. Do not determine legal sufficiency.","tags":["Legal document support","x402"],"examples":["A demand packet references attachments that are not included in the file set."]},{"id":"SUST-DEADLINE-EVIDENCE-001","name":"Deadline Evidence Map","description":"Map supplied deadlines to their source language, triggering event, calculation inputs, and proof. Do not calculate or assert legal deadlines unless the required rule and dates are supplied.","tags":["Legal document support","x402"],"examples":["A case file mentions a response deadline but does not include the rule that creates it."]},{"id":"SUST-STATEMENT-CONSISTENCY-001","name":"Statement Consistency Check","description":"Compare supplied statements across declarations, emails, transcripts, and records to identify material differences while preserving source and context.","tags":["Legal document support","x402"],"examples":["Two written accounts describe the same payment differently."]},{"id":"SUST-CURRICULUM-DEPENDENCY-001","name":"Curriculum Dependency Map","description":"Map supplied learning objectives, prerequisite knowledge, modules, activities, assessments, and sequencing dependencies. Do not claim instructional effectiveness without evidence.","tags":["Learning programs","x402"],"examples":["A course teaches advanced content before the prerequisite concepts are introduced."]},{"id":"SUST-LEARNER-JOURNEY-001","name":"Learner Journey Map","description":"Map supplied learner steps from enrollment through instruction, practice, assessment, support, completion, and follow-up. Do not infer learner sentiment.","tags":["Learning programs","x402"],"examples":["A program has strong course content but unclear enrollment and post-course support."]},{"id":"SUST-INSTRUCTOR-READINESS-001","name":"Instructor Readiness Check","description":"Check whether supplied instructor materials include objectives, facilitation guidance, timing, examples, activities, assessments, escalation, and required evidence.","tags":["Learning programs","x402"],"examples":["A live class has slides but no facilitator guide or timing plan."]},{"id":"SUST-CE-RECORD-INTEGRITY-001","name":"Continuing Education Record Integrity Check","description":"Check supplied CE records for course identity, participant identity, completion evidence, attendance or assessment records, certificate linkage, and reporting fields. Do not claim regulator acceptance.","tags":["Learning programs","x402"],"examples":["Certificates exist, but participant IDs and attendance evidence are inconsistent."]},{"id":"SUST-CONTINUITY-PROCESS-MAP-001","name":"Business Continuity Process Map","description":"Map supplied critical processes to people, systems, vendors, facilities, data, and minimum operating requirements. Do not infer recovery capability beyond evidence.","tags":["Business continuity","x402"],"examples":["A company knows its critical services but has not mapped their underlying dependencies."]},{"id":"SUST-RECOVERY-PRIORITY-001","name":"Recovery Priority Map","description":"Prioritize supplied recovery work using documented criticality, dependency, timing, and customer impact. Do not invent recovery-time objectives.","tags":["Business continuity","x402"],"examples":["Several systems are down, but the business has no evidence-based recovery order."]},{"id":"SUST-CONTINUITY-CONTACT-001","name":"Continuity Contact Chain Check","description":"Check whether supplied continuity contacts have roles, alternates, activation conditions, communication routes, and ownership. Do not contact anyone.","tags":["Business continuity","x402"],"examples":["An emergency plan lists names but no alternates or activation responsibilities."]},{"id":"SUST-CONTINUITY-EXERCISE-001","name":"Continuity Exercise Evidence Check","description":"Map supplied continuity exercise results to scenarios, observed failures, corrective actions, owners, and retest evidence. A completed exercise alone is not proof of readiness.","tags":["Business continuity","x402"],"examples":["A tabletop exercise found several gaps, but no retest was documented."]},{"id":"SUST-INSURANCE-DOCUMENT-MAP-001","name":"Insurance Document Map","description":"Organize supplied policy, endorsement, declaration, claim, vendor, and payment records by purpose and date. Do not interpret coverage or advise on claims.","tags":["Risk documentation","x402"],"examples":["A property file contains policies and endorsements but no clear document register."]},{"id":"SUST-POLICY-CHANGE-IMPACT-001","name":"Policy Change Impact Map","description":"Trace supplied policy or endorsement changes to documented operations, assets, contacts, records, and downstream review needs. Do not determine coverage effects beyond supplied language.","tags":["Risk documentation","x402"],"examples":["An endorsement changes a named location, but related records have not been reconciled."]},{"id":"SUST-CLAIM-COMMUNICATION-MAP-001","name":"Claim Communication Map","description":"Map supplied claim communications into requests, statements, decisions, documents promised, deadlines stated, and unresolved issues while preserving source.","tags":["Risk documentation","x402"],"examples":["A claim thread contains requests for documents and several unanswered questions."]},{"id":"SUST-RISK-DOCUMENT-LINEAGE-001","name":"Risk Document Lineage Check","description":"Trace supplied risk-related documents through versions, sources, references, updates, and downstream use. Preserve conflicting versions rather than selecting one without authority.","tags":["Risk documentation","x402"],"examples":["A claims packet uses values from a spreadsheet whose source and version are unclear."]},{"id":"SUST-CLAIM-INTAKE-MAP-001","name":"Claim Intake Evidence Map","description":"Map supplied claim-intake information into loss facts, parties, dates, property or asset details, documents, contacts, and unresolved questions. Do not determine coverage or liability.","tags":["Claims operations","x402"],"examples":["A claim intake contains loss facts and vendor information but several dates and records are still unclear."]},{"id":"SUST-CLAIM-PAYMENT-RECONCILE-001","name":"Claim Payment Reconciliation Check","description":"Compare supplied estimates, invoices, payments, deductibles, supplements, and balances while preserving each source. Do not decide what is legally owed or covered.","tags":["Claims operations","x402"],"examples":["A claim file includes several checks, vendor invoices, and an unresolved balance."]},{"id":"SUST-CLAIM-REQUEST-TRACKER-001","name":"Claim Request and Response Map","description":"Map supplied document requests, information requests, responses, promises, and unanswered items across a claim. A sent request is not a completed response.","tags":["Claims operations","x402"],"examples":["An adjuster requested documents in several emails and some responses remain incomplete."]},{"id":"SUST-CLAIM-TIMELINE-INTEGRITY-001","name":"Claim Timeline Integrity Check","description":"Compare supplied claim dates, notices, inspections, vendor activity, payments, and communications for chronology conflicts and missing transitions. Do not calculate statutory deadlines without supplied rules.","tags":["Claims operations","x402"],"examples":["The claim record contains different dates for inspection, mitigation, and payment events."]},{"id":"SUST-PURCHASE-READINESS-001","name":"Purchase Readiness Check","description":"Check whether a supplied purchase has approved scope, specification, quantity, budget state, supplier evidence, terms, delivery requirements, and acceptance criteria. Do not place orders.","tags":["Procurement execution","x402"],"examples":["A team wants to order equipment before final specifications and acceptance requirements are documented."]},{"id":"SUST-SUPPLIER-QUOTE-INTEGRITY-001","name":"Supplier Quote Integrity Check","description":"Compare supplied quotes for scope, quantity, currency, dates, terms, shipping, exclusions, and validity. Do not identify a cheapest option when delivered-cost inputs are incomplete.","tags":["Procurement execution","x402"],"examples":["Three quotes appear comparable but use different freight and payment terms."]},{"id":"SUST-PURCHASE-APPROVAL-001","name":"Purchase Approval Boundary Check","description":"Map supplied purchase decisions to approval thresholds, authority, exceptions, and evidence. Do not authorize spending.","tags":["Procurement execution","x402"],"examples":["A buyer can select a vendor but spending approval thresholds are unclear."]},{"id":"SUST-DELIVERY-ACCEPTANCE-001","name":"Procurement Delivery Acceptance Check","description":"Check whether supplied purchased goods or services meet documented quantity, specification, condition, timing, and acceptance evidence. Do not release payment.","tags":["Procurement execution","x402"],"examples":["A shipment arrived, but inspection and acceptance evidence are incomplete."]},{"id":"SUST-INVOICE-MATCH-001","name":"Invoice Match Check","description":"Compare supplied invoice lines against purchase, contract, delivery, and approval evidence. Do not approve payment or infer missing terms.","tags":["Finance operations","x402"],"examples":["An invoice includes charges that are not clearly tied to the purchase order."]},{"id":"SUST-EXPENSE-EVIDENCE-001","name":"Expense Evidence Map","description":"Map supplied expenses to receipts, business purpose, approval, category, date, and supporting records. Do not make tax determinations.","tags":["Finance operations","x402"],"examples":["A reimbursement packet contains charges with uneven receipt and approval evidence."]},{"id":"SUST-REVENUE-RECOGNITION-EVIDENCE-001","name":"Revenue Recognition Evidence Map","description":"Map supplied revenue events to contract terms, delivery or acceptance evidence, invoice state, and timing. Do not make accounting-policy determinations.","tags":["Finance operations","x402"],"examples":["A service was invoiced, but acceptance and delivery records are incomplete."]},{"id":"SUST-PAYMENT-TERM-RISK-001","name":"Payment Term Risk Map","description":"Map supplied receivable or payable terms to timing, dependencies, customer or vendor obligations, and documented cash-pressure points. Do not forecast default.","tags":["Finance operations","x402"],"examples":["A client pays net-60 while the business must pay vendors upfront."]},{"id":"SUST-KNOWLEDGE-TRANSFER-PLAN-001","name":"Knowledge Transfer Plan Check","description":"Check whether supplied knowledge-transfer plans cover critical topics, source experts, practice, observation, teach-back, documentation, and proof of independence.","tags":["Knowledge transfer","x402"],"examples":["A departing employee has documented procedures but no teach-back or practice plan."]},{"id":"SUST-EXPERT-DEPENDENCY-001","name":"Subject-Matter Expert Dependency Map","description":"Map supplied work that depends on specific experts, tacit knowledge, exceptions, and approvals. Do not infer unwillingness to share knowledge.","tags":["Knowledge transfer","x402"],"examples":["One specialist handles every exception in a technical process."]},{"id":"SUST-TEACHBACK-INTEGRITY-001","name":"Teach-Back Integrity Check","description":"Check whether supplied teach-back evidence demonstrates understanding, execution, exception handling, and correction rather than attendance alone.","tags":["Knowledge transfer","x402"],"examples":["A trainee completed shadowing but has not independently demonstrated the process."]},{"id":"SUST-SOP-TRANSFER-001","name":"SOP-to-Practice Transfer Check","description":"Compare supplied SOP instructions with observed or documented practice, exceptions, job aids, and verification. Do not assume the SOP reflects actual work.","tags":["Knowledge transfer","x402"],"examples":["The written procedure differs from how experienced staff actually handle exceptions."]},{"id":"SUST-ACCOUNT-EXPANSION-001","name":"Account Expansion Evidence Map","description":"Map supplied client needs, usage, outcomes, open problems, relationships, and adjacent opportunities without inventing demand.","tags":["Account growth","x402"],"examples":["A current client has additional needs, but the evidence for a broader engagement is scattered."]},{"id":"SUST-CROSS-SELL-FIT-001","name":"Cross-Sell Fit Check","description":"Compare supplied client needs against documented adjacent offers, capability fit, timing, and evidence. Do not recommend offers with unsupported fit.","tags":["Account growth","x402"],"examples":["A client uses one service and may need a second, but the operational fit has not been checked."]},{"id":"SUST-RELATIONSHIP-MAP-001","name":"Client Relationship Dependency Map","description":"Map supplied client relationships, decision makers, users, sponsors, approvers, and communication dependencies. Do not infer influence without evidence.","tags":["Account growth","x402"],"examples":["A client relationship depends on one sponsor while operational users are not mapped."]},{"id":"SUST-EXPANSION-READINESS-001","name":"Account Expansion Readiness Check","description":"Check whether a supplied expansion opportunity has value proof, delivery capacity, scope clarity, commercial terms, stakeholder support, and timing evidence.","tags":["Account growth","x402"],"examples":["A client wants more work, but current delivery capacity and scope boundaries are unresolved."]},{"id":"SUST-CONTACT-HISTORY-001","name":"Contact History Integrity Check","description":"Check whether supplied client contact history preserves dates, participants, commitments, decisions, requests, and next steps across channels.","tags":["Account growth","x402"],"examples":["Important commitments are spread across email, text, and meeting notes."]},{"id":"SUST-ACCOUNT-RISK-CONCENTRATION-001","name":"Account Concentration Risk Map","description":"Map supplied revenue, relationship, delivery, or dependency concentration around major accounts without predicting churn.","tags":["Account growth","x402"],"examples":["A large portion of delivery work depends on one client and one internal relationship owner."]},{"id":"SUST-SERVICE-USAGE-EVIDENCE-001","name":"Service Usage Evidence Map","description":"Map supplied service usage, requested work, adoption, outcomes, and gaps to distinguish purchased scope from actual use.","tags":["Account growth","x402"],"examples":["A client purchased a full service package but only uses part of it."]},{"id":"SUST-ACCOUNT-RETURN-LOOP-001","name":"Account Return Loop Check","description":"Check whether account actions, client requests, delivery outcomes, and follow-ups return to the account owner with enough evidence for closure or next decision.","tags":["Account growth","x402"],"examples":["Delivery resolves a client issue, but account leadership is never told what changed."]},{"id":"SUST-AUTOMATION-COST-MAP-001","name":"Automation Cost Driver Map","description":"Map supplied automation costs to model usage, infrastructure, human review, failures, retries, maintenance, and support. Do not estimate missing costs as zero.","tags":["Automation economics","x402"],"examples":["An AI workflow looks cheap per call but requires significant human review and retry handling."]},{"id":"SUST-AUTOMATION-ROI-EVIDENCE-001","name":"Automation ROI Evidence Check","description":"Compare supplied automation benefits against documented labor, error, delay, quality, adoption, and cost evidence. Do not claim ROI without complete inputs.","tags":["Automation economics","x402"],"examples":["A team says automation saves time, but baseline effort and review costs were never measured."]},{"id":"SUST-HUMAN-REVIEW-COST-001","name":"Human Review Cost Map","description":"Map supplied human review work to frequency, complexity, role, escalation, and downstream dependency. Do not infer labor rates.","tags":["Automation economics","x402"],"examples":["An agent output requires approval each time, but review effort is not tracked."]},{"id":"SUST-AUTOMATION-SCALE-001","name":"Automation Scale Readiness Check","description":"Check supplied automation for throughput, concurrency, cost, exception handling, observability, governance, and recovery before scale. Do not infer production readiness from pilot success.","tags":["Automation economics","x402"],"examples":["An automation works for ten cases but has not been tested for higher volume or failure recovery."]},{"id":"SUST-MODEL-OUTPUT-QUALITY-001","name":"Model Output Quality Check","description":"Evaluate supplied AI outputs against explicit criteria for grounding, completeness, structure, uncertainty, and task fit. Do not infer model quality beyond the supplied examples.","tags":["AI quality","x402"],"examples":["A model produces polished answers but sometimes omits source support."]},{"id":"SUST-HALLUCINATION-RISK-001","name":"Unsupported Claim Risk Map","description":"Identify supplied AI claims that lack supporting evidence, overstate uncertainty, or conflict with sources. Do not label every inference a hallucination.","tags":["AI quality","x402"],"examples":["An AI-generated brief contains several statements not found in the source documents."]},{"id":"SUST-PROMPT-DRIFT-001","name":"Prompt Drift Check","description":"Compare supplied prompt or instruction versions to identify changed goals, authority, constraints, outputs, and verification rules. Do not assume every change is harmful.","tags":["AI quality","x402"],"examples":["An agent behaves differently after several prompt edits, but the changes were never reconciled."]},{"id":"SUST-AGENT-CONSISTENCY-001","name":"Agent Consistency Check","description":"Compare repeated supplied agent runs against the same task and acceptance criteria to identify variation, missing context, and unstable outputs. Do not claim deterministic behavior.","tags":["AI quality","x402"],"examples":["The same input produces materially different recommendations across runs."]},{"id":"SUST-GOVERNANCE-EVIDENCE-MAP-001","name":"Governance Evidence Map","description":"Map supplied governance rules to approvals, records, ownership, exceptions, and verification evidence. Do not certify governance effectiveness.","tags":["Governance assurance","x402"],"examples":["A governance framework exists, but proof of approvals and exception handling is incomplete."]},{"id":"SUST-APPROVAL-LINEAGE-001","name":"Approval Lineage Check","description":"Trace supplied approvals back to requester, decision authority, evidence reviewed, conditions, and downstream action. Do not infer approval from silence.","tags":["Governance assurance","x402"],"examples":["A change is marked approved, but the record does not show who approved it or under what condition."]},{"id":"SUST-EXCEPTION-EVIDENCE-001","name":"Exception Evidence Map","description":"Map supplied exceptions to trigger, authority, rationale, duration, evidence, and return-to-standard path. Do not normalize undocumented workarounds.","tags":["Governance assurance","x402"],"examples":["A process has several standing exceptions but no documented owner or expiry."]},{"id":"SUST-GOVERNANCE-RETEST-001","name":"Governance Retest Check","description":"Check whether supplied corrective actions or control changes were retested and whether evidence supports closure. A remediation plan alone is not proof.","tags":["Governance assurance","x402"],"examples":["A control issue was fixed, but no follow-up evidence confirms the fix works."]},{"id":"SUST-WORKFLOW-OBSERVABILITY-001","name":"Workflow Observability Map","description":"Map supplied workflow states to available logs, alerts, timestamps, owners, and verification points. Do not claim monitoring coverage without evidence.","tags":["Operational observability","x402"],"examples":["A workflow fails intermittently, but only final success or failure is recorded."]},{"id":"SUST-FAILURE-DETECTION-001","name":"Failure Detection Coverage Check","description":"Check whether supplied failure modes have documented detection signals, thresholds, owners, and escalation paths.","tags":["Operational observability","x402"],"examples":["Several integration failures can occur without triggering an alert."]},{"id":"SUST-STATUS-TRUTH-001","name":"Status Truth Check","description":"Compare supplied reported statuses with underlying execution, verification, and return evidence. Do not treat labels such as green or done as proof.","tags":["Operational observability","x402"],"examples":["A dashboard shows all work green while several dependencies remain unresolved."]},{"id":"SUST-OPERATIONAL-SIGNAL-001","name":"Operational Signal Routing Map","description":"Map supplied alerts, events, exceptions, and status changes to intended recipients, urgency, ownership, and next actions.","tags":["Operational observability","x402"],"examples":["System alerts exist, but nobody is clearly responsible for acting on them."]},{"id":"SUST-SCALE-ROLE-MAP-001","name":"Scale Role Architecture Map","description":"Map supplied growth requirements to roles, decision rights, management layers, specialist capabilities, and handoffs. Do not infer ideal organization size.","tags":["Scale operating model","x402"],"examples":["A founder-led company is adding clients faster than its current role structure can support."]},{"id":"SUST-SCALE-PROCESS-001","name":"Process Scale Readiness Check","description":"Check supplied processes for standardization, exception handling, ownership, tooling, evidence, and throughput constraints before scale.","tags":["Scale operating model","x402"],"examples":["A service process works manually for a few clients but relies on undocumented founder intervention."]},{"id":"SUST-SCALE-GOVERNANCE-001","name":"Governance Scale Readiness Check","description":"Assess whether supplied approval, authority, exception, reporting, and escalation rules can support higher volume without central bottlenecks.","tags":["Scale operating model","x402"],"examples":["Every exception still requires founder approval as transaction volume grows."]},{"id":"SUST-SCALE-CLIENT-DELIVERY-001","name":"Client Delivery Scale Map","description":"Map supplied client-delivery work to capacity, standardization, handoffs, quality controls, escalation, and support dependencies.","tags":["Scale operating model","x402"],"examples":["Client delivery quality depends on one experienced operator reviewing every case."]},{"id":"SUST-SCALE-TECH-STACK-001","name":"Technology Scale Dependency Map","description":"Map supplied growth plans to systems, integrations, limits, data, observability, and recovery dependencies. Do not predict system capacity without evidence.","tags":["Scale operating model","x402"],"examples":["A platform is expected to support more clients, but limits and recovery behavior are undocumented."]},{"id":"SUST-SCALE-FINANCIAL-CONTROLS-001","name":"Financial Control Scale Check","description":"Check supplied growth operations for billing, approvals, reconciliation, spend authority, cash commitments, and evidence as transaction volume increases.","tags":["Scale operating model","x402"],"examples":["Billing volume is increasing faster than reconciliation and approval controls."]},{"id":"SUST-SCALE-KNOWLEDGE-001","name":"Knowledge Scale Readiness Check","description":"Assess whether supplied knowledge is canonical, retrievable, teachable, versioned, and transferable enough to support more people or clients.","tags":["Scale operating model","x402"],"examples":["A team is hiring quickly while critical knowledge remains in chat threads and individual memory."]},{"id":"SUST-SCALE-RETURN-LOOP-001","name":"Scale Return Loop Check","description":"Check whether delegated work, automated work, client delivery, and exceptions still return with enough evidence for oversight as volume increases.","tags":["Scale operating model","x402"],"examples":["More work is delegated, but leadership visibility drops because return evidence is inconsistent."]},{"id":"SUST-ENTERPRISE-CONTEXT-AUDIT-001","name":"Enterprise Context Architecture Audit","description":"Audit supplied enterprise context across canon, source authority, dependencies, decision lineage, retrieval, handoffs, governance, and return loops. Preserve evidence boundaries and identify structural context failures before proposing repairs.","tags":["Premium synthesis","x402"],"examples":["An organization uses multiple AI tools and repositories but cannot reliably reproduce decisions or determine which context is authoritative."]},{"id":"SUST-INVISIBLE-ECOSYSTEM-MAP-001","name":"Invisible Ecosystem Map","description":"Map supplied visible and invisible work across people, systems, decisions, dependencies, exceptions, information flows, and pressure points. Distinguish documented structure from inferred connective work.","tags":["Premium synthesis","x402"],"examples":["A business appears functional on paper but relies on undocumented coordination, exceptions, and founder intervention."]},{"id":"SUST-AI-OS-READINESS-001","name":"AI Operating System Readiness Audit","description":"Assess supplied AI operating environment across context architecture, tool boundaries, source governance, memory, routing, verification, failure recovery, human authority, and observability. Do not claim production readiness without evidence.","tags":["Premium synthesis","x402"],"examples":["A company has several agents and automations but lacks a governed operating system connecting them."]},{"id":"SUST-STRATEGIC-OPERATING-BLUEPRINT-001","name":"Strategic Operating Model Blueprint","description":"Synthesize supplied strategy, roles, workflows, governance, technology, client promises, revenue mechanics, and scale constraints into an evidence-bounded operating model blueprint. Unknowns remain explicit.","tags":["Premium synthesis","x402"],"examples":["A growing consulting company needs its strategy, delivery model, roles, systems, and governance reconciled into one operating model."]},{"id":"SUST-ENTERPRISE-FRICTION-ATLAS-001","name":"Enterprise Friction Atlas","description":"Aggregate supplied workflow, handoff, decision, data, role, and system friction into a connected atlas. Identify repeated structural causes separately from isolated incidents.","tags":["Premium synthesis","x402"],"examples":["Multiple departments report different problems that may share the same approval, data, and ownership bottlenecks."]},{"id":"SUST-DECISION-SYSTEM-AUDIT-001","name":"Decision System Audit","description":"Audit supplied decision processes across evidence intake, authority, criteria, reversibility, documentation, execution, and return loops. Do not judge decision quality solely from outcomes.","tags":["Premium synthesis","x402"],"examples":["Leadership makes frequent decisions but cannot trace why they were made or whether downstream work closed."]},{"id":"SUST-TRANSFORMATION-DEPENDENCY-MAP-001","name":"Transformation Dependency Map","description":"Map a supplied transformation across strategy, people, process, technology, data, governance, training, customer impact, and sequencing dependencies.","tags":["Premium synthesis","x402"],"examples":["A company is implementing AI while also redesigning workflows, roles, data practices, and client delivery."]},{"id":"SUST-ENTERPRISE-AI-WORK-DESIGN-001","name":"Enterprise Human-AI Work Architecture","description":"Synthesize supplied work into human-owned judgment, AI-supported execution, automation candidates, approval gates, context requirements, and recovery paths across an organization.","tags":["Premium synthesis","x402"],"examples":["An organization wants a coherent division of work between people and AI rather than isolated automation projects."]},{"id":"SUST-FOUNDER-ECOSYSTEM-AUDIT-001","name":"Founder Ecosystem Audit","description":"Map supplied founder dependencies across decisions, relationships, knowledge, approvals, strategy, operations, and recovery work. Identify where founder involvement creates leverage versus avoidable fragility.","tags":["Premium synthesis","x402"],"examples":["A founder is central to sales, delivery, approvals, problem solving, and institutional memory."]},{"id":"SUST-SCALE-ARCHITECTURE-AUDIT-001","name":"Scale Architecture Audit","description":"Assess supplied operating model for scale across role architecture, workflow repeatability, governance, technology, data, knowledge, finance controls, client delivery, and return loops.","tags":["Premium synthesis","x402"],"examples":["A business is growing quickly but its current operating system was designed around a small founder-led team."]},{"id":"SUST-CLIENT-ECOSYSTEM-MAP-001","name":"Client Ecosystem Journey Map","description":"Map supplied client experience across acquisition, intake, decisions, delivery, support, value proof, renewal, referrals, and internal backstage dependencies.","tags":["Premium synthesis","x402"],"examples":["A service business wants one evidence-backed map of the entire client relationship rather than separate sales and delivery views."]},{"id":"SUST-MARKET-OPPORTUNITY-ATLAS-001","name":"Market Opportunity Atlas","description":"Synthesize supplied market, customer, competitor, capability, channel, regulatory, cost, and operating evidence into a structured opportunity atlas without inventing current external facts.","tags":["Premium synthesis","x402"],"examples":["A founder is comparing several markets and needs one view connecting demand, fit, requirements, and execution dependencies."]},{"id":"SUST-PROCUREMENT-PURSUIT-AUDIT-001","name":"Procurement Pursuit Audit","description":"Audit a supplied public or enterprise procurement pursuit across eligibility, requirements, delivery chain, partners, past performance, evidence, proposal coverage, and submission dependencies.","tags":["Premium synthesis","x402"],"examples":["A company wants to know whether an opportunity is truly pursuit-ready before spending time on the proposal."]},{"id":"SUST-CLAIM-EVIDENCE-ATLAS-001","name":"Claim Evidence Atlas","description":"Synthesize supplied claim facts, documents, chronology, payments, communications, requests, competing accounts, and unresolved evidence into one source-linked map. Do not determine coverage, liability, or legal strategy.","tags":["Premium synthesis","x402"],"examples":["A complex property claim has records across vendors, payments, emails, estimates, and competing timelines."]},{"id":"SUST-PROPERTY-OPERATIONS-ATLAS-001","name":"Property Operations Atlas","description":"Map supplied property operations across tenant relationships, condition evidence, maintenance, vendors, leases, payment routing, emergency paths, and owner approvals.","tags":["Premium synthesis","x402"],"examples":["An owner needs one operating view of a property rather than separate tenant, maintenance, and vendor records."]},{"id":"SUST-WORKFORCE-SYSTEM-AUDIT-001","name":"Workforce System Audit","description":"Audit supplied workforce design across work demand, role clarity, load-bearing work, decision rights, capacity, hiring, onboarding, knowledge continuity, training, and AI augmentation.","tags":["Premium synthesis","x402"],"examples":["A company keeps treating workforce problems as training issues even though role and workflow problems may be driving them."]},{"id":"SUST-KNOWLEDGE-SYSTEM-AUDIT-001","name":"Knowledge System Audit","description":"Audit supplied knowledge architecture across canon, source authority, metadata, retrieval, duplication, RAG grounding, memory boundaries, transfer, and version control.","tags":["Premium synthesis","x402"],"examples":["An organization has large document stores but cannot reliably retrieve the right version or preserve decision lineage."]},{"id":"SUST-AUTOMATION-GOVERNANCE-AUDIT-001","name":"Automation Governance Audit","description":"Audit supplied automations across suitability, authority, review gates, data handoffs, recovery, observability, cost, security, privacy, and closure evidence.","tags":["Premium synthesis","x402"],"examples":["A company has many automations but no consistent governance model for what they may do or how failures return."]},{"id":"SUST-SERVICE-DELIVERY-AUDIT-001","name":"Service Delivery System Audit","description":"Audit supplied service delivery across intake, blueprint, boundaries, handoffs, capacity, quality, failure recovery, customer promises, acceptance, and value proof.","tags":["Premium synthesis","x402"],"examples":["A service company is growing but delivery varies across clients and rework is increasing."]},{"id":"SUST-COMMERCIAL-SYSTEM-AUDIT-001","name":"Commercial System Audit","description":"Audit supplied commercial system across offer architecture, pricing logic, buyer friction, sales stages, proposals, revenue leakage, referrals, account growth, and payment dependencies.","tags":["Premium synthesis","x402"],"examples":["A company has demand but cannot see where its commercial process loses buyers or revenue."]},{"id":"SUST-GOVERNANCE-CONTROL-ATLAS-001","name":"Governance and Control Atlas","description":"Synthesize supplied authority, decision rights, policies, controls, exceptions, approvals, audit trails, security, privacy, and compliance evidence into one governance map.","tags":["Premium synthesis","x402"],"examples":["An organization has policies and controls in several systems but no unified view of governance dependencies."]},{"id":"SUST-PROGRAM-EXECUTION-AUDIT-001","name":"Program Execution Audit","description":"Audit supplied program execution across milestones, dependencies, critical path evidence, change impact, decisions, workload, meetings, acceptance, and completion proof.","tags":["Premium synthesis","x402"],"examples":["A multi-project program reports progress but struggles to prove what is actually complete or blocking delivery."]},{"id":"SUST-EVIDENCE-SYSTEM-AUDIT-001","name":"Evidence System Audit","description":"Audit how supplied evidence is created, classified, linked, refreshed, contradicted, weighted, retrieved, and converted into decisions. Preserve source type and uncertainty throughout.","tags":["Premium synthesis","x402"],"examples":["An organization collects large amounts of information but cannot consistently distinguish fact, account, inference, canon, and decision evidence."]},{"id":"SUST-BOI-SYSTEM-DIAGNOSTIC-001","name":"BOI System Diagnostic","description":"Run a bounded BOI diagnostic across supplied context architecture, evidence lineage, dependencies, bridge gaps, information flow, workflow friction, authority, propagation, return loops, and replication risk. Do not claim a complete enterprise audit beyond supplied sources.","tags":["Premium synthesis","x402"],"examples":["A complex operating environment needs a single BOI diagnostic showing where context, work, authority, and evidence are breaking together."]}],"x-sustineri":{"interoperability":{"a2a_task_execution":"NOT_IMPLEMENTED","mcp_remote_transport":"NOT_IMPLEMENTED","mcp_host_adapter":"HOST_ADAPTER_ONLY"},"discovery":{"catalog":"https://sustineri-x402.onrender.com/v1/agents","openapi":"https://sustineri-x402.onrender.com/openapi.json","llms_txt":"https://sustineri-x402.onrender.com/llms.txt","x402_bazaar":"https://sustineri-x402.onrender.com/discovery/resources","x402_well_known":"https://sustineri-x402.onrender.com/.well-known/x402","sitemap":"https://sustineri-x402.onrender.com/sitemap.xml","distribution_manifest":"https://sustineri-x402.onrender.com/distribution/manifest.json","social_feed":"https://sustineri-x402.onrender.com/distribution/social.json","funnel_status":"https://sustineri-x402.onrender.com/distribution/status.json"},"execution":{"transport":"HTTP POST","path_template":"/v1/agents/{slug}/run","payment":{"protocol":"x402","x402_version":2,"terms":"Returned per request in the 402 PAYMENT-REQUIRED response."}},"released_count":312,"total_count":312}}