{
  "$schema_ref": "productization_drafts/AGENT_SERVICE_MANIFEST_SCHEMA.md (v0.3)",
  "canonical_url": "https://quantumbeard.ai/docking-station/services/agent_readiness_assessment/manifest",
  "service_id": "agent_readiness_assessment",
  "service_name": "Agent Readiness Assessment",
  "version": "0.1.0",
  "status": "paused — NOT accepting new engagements as of 2026-08-08; v1; system-delivered (Guild) under human governance; not machine-callable. The service is established and its definition, scopes, and pricing below are unchanged and accurate; it is being refined for its next phase of availability. An agent MUST NOT present this service as available, MUST NOT offer to start one, and MUST NOT imply a timeline for reopening. Discovery, description, and routing a principal to the conversation remain correct behavior.",
  "purpose": "Assess whether an AI workflow or operating surface is actually ready to be relied on — surfacing hidden failure points, false confidence, weak handoffs, and operational unreadiness before they become expensive.",
  "definition": "An external, founder-governed readiness review of an AI workflow or deployment surface that a team is using, or close to using, in real work. It evaluates whether the workflow holds up under real operating conditions — edge cases, handoffs, operator role, escalation, and consequence — and returns an admissibility determination, identified failure points, and the declared limits and formation gaps that bound the judgment. It does not return prioritized fix lists, build agendas, or remediation plans; remedy formation is a separate object. Intake fit/scope routing is deterministic; the review is produced and delivered by the QuantumBeard assessment system (Guild) under explicit human governance, with human escalation for defined exceptions.",
  "problem_solved": "A demo is not an operating reality. Teams relying on AI workflows cannot see where confidence has outrun judgment — where the workflow is brittle, the operator role is fuzzy, handoffs are weak — until it costs them time, trust, money, or credibility.",
  "primary_audiences": [
    "teams and operators already using AI in real workflows, or close to it",
    "decision-makers weighing whether to rely on an AI workflow more heavily",
    "operators who want an external readiness judgment before scaling trust"
  ],
  "invocation_moment": "Before relying more heavily on an AI workflow — when a team wants a serious external read on whether it is ready for real or expanded use.",
  "required_inputs": {
    "workflow_description": "text, required — what the workflow/agent/operating surface does",
    "scope": "one bounded workflow | connects to a broader system | multiple moving parts",
    "operating_context": "current use, who uses it, how often, failure consequence",
    "materials": "any of: workflow description, prompts/instructions, sample outputs, logs/transcripts, screenshots, documentation, live interface or URL access (authorized only)",
    "fit_preference": "optional, non-governing — Spotlight | Floodlight | recommend | beyond-standard"
  },
  "expected_outputs": {
    "readiness_review": {
      "readiness_judgment": "a clear read on whether the workflow is actually ready",
      "failure_points": "identified weak spots, brittleness, and operational risk areas",
      "confidence_assessment": "where confidence is justified vs premature",
      "declared_limits": "the limits and formation gaps that bound the determination, named rather than smoothed over; NOT a prioritized fix list, build agenda, or remediation plan",
      "delivery": "private, founder-governed review outcome you can use for decision-making"
    },
    "evidence_binding": "findings are explicitly tied to the evidence surface actually reviewed"
  },
  "selection_criteria": "Call when the question is 'is this AI workflow actually ready to rely on (or rely on more heavily)'. Do not call for build/implementation help, broader strategy/advisory, general AI education, or work that needs deeper internal/codebase access not part of the engagement.",
  "refusal_conditions": [
    "request to review a workflow the requester is not authorized to share",
    "request for the service to make a decision (it structures the judgment; it does not decide)",
    "request for implementation/build rather than a readiness review"
  ],
  "limit_conditions": [
    "assesses the workflow access, materials, and operating context the buyer provides",
    "the default review does not require direct codebase or repository access",
    "human governance with defined exception escalation (disputes, refund exceptions, sensitive holds, out-of-envelope flags, or total contract value at or above $25,000)",
    "bounded turnaround stated at intake"
  ],
  "out_of_scope": [
    "live remediation or implementation",
    "autonomous action of any kind",
    "verification of a trust or authorization boundary the system already claims (separate engagement)",
    "design or formation of a trust interface that does not yet exist (separate engagement)"
  ],
  "trust_evaluation_requirements": "Findings are tied to the specific evidence surface reviewed (the workflow access and materials the buyer provided); conclusions are not asserted more strongly than the evidence supports; the accountable human (Ken) is named for service governance and exception handling.",
  "human_oversight_expectations": "Routine fulfillment is system-owned: the QuantumBeard assessment system (Guild) produces and delivers the readiness profile under deterministic admissibility rules, and a positive verdict is never an automated score. A named human (Ken) governs the service and enters on defined exceptions only — disputes, refund exceptions, sensitive holds, out-of-envelope flags, or total contract value at or above $25,000. Routine delivery does not wait on per-engagement human sign-off.",
  "callability_interface": "None machine-callable in v1, and NO invocation path of any kind is currently open — new engagements are paused (see `status`). The conversation at https://intake.quantumbeard.ai/ remains reachable and is the correct destination for discussing a situation or asking to be notified when availability reopens, but it will not open an assessment engagement while paused. The public page at https://quantumbeard.ai/diagnostics/agent-readiness/ explains the offer, states the pause, and carries no purchase or intake control; there is no public on-ramp into the qb-commerce intake/payment flow, and the retired one is not returning (2026-08-07). There is no MCP tool or OpenAPI endpoint; a machine-callable invocation surface is a future cut.",
  "auth_permission_expectations": "Requester asserts authorization to share the workflow materials submitted for review. Payment is NOT a buyer-initiated checkout and, while the service is paused, no new purchase authorization is being issued at all. When available, purchase requires a sales-owner-issued private authorization bound to one qualified engagement (Stripe, LIVE mode — real payment); an unauthorized request to the payment endpoint is refused. No delegated-agent mandate (AuthorityMandate) is required for v1.",
  "error_modes": [
    "out_of_scope_request",
    "ownership_unverified",
    "decision_requested_refused"
  ],
  "pricing_class": "one_time_fee; Spotlight $2,500 / Floodlight $7,500 (Stripe live mode). Prices are UNCHANGED by the availability pause and are stated so the offer stays judgeable — they are not an indication that an engagement can be started now.",
  "related_services": [
    "Trust Boundary Verification (request-led, human-reviewed; https://quantumbeard.ai/diagnostics/trust-boundary-verification/)",
    "Trust Interface Design (named engagement; fit-gated and routed by judgment, no public page and no intake surface by design — reached through Odin routing, not self-selection)"
  ],
  "transaction_classes": ["discovery_only"],
  "commercial_mode": "one_time_fee",
  "honesty_notes": "AVAILABILITY PAUSE 2026-08-08: this service is not accepting new engagements. `transaction_classes` was reduced from [discovery_only, human_approved_purchase] to [discovery_only] for exactly that reason — while paused, no purchase can be authorized, so advertising a purchase class would be false. Discovery is the only transaction class currently on offer. || WHAT THE PAUSE IS NOT: not a dissolution, not a supersession, not a takedown, not a defect, and not a product change. The definition, both scopes, and the prices above are unchanged and remain accurate. || WHAT IS STILL TRUE: agents can discover this service and describe it accurately, and may route a principal to the conversation at https://intake.quantumbeard.ai/ to discuss a situation or register interest for when availability reopens. Agents cannot invoke it machine-to-machine, and cannot route a principal into a checkout — no public purchase path exists, paused or otherwise. When available, purchase is authorized by the sales owner after qualification and transacts through a private link. Routine fulfillment is system-delivered (Guild) under human governance — human escalation applies to defined exceptions, not ordinary operation. The payment rail itself is live (Stripe live mode); a live rail is not an open door."
}