links.arjun.tv/docs/end-user/use-cases/uc-20-knowledge-agent-qa-governance

UC-20: Knowledge, Agent, QA, and Governance Control Plane

Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.

Developer Outcome

Ship knowledge, agent, qa, and governance control plane for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.

Prerequisites

  • A valid handle and environment access for Gharart.com.
  • JWT and/or PAT credentials with required scope for this use case.
  • Access to logs, support escalation endpoints, and test workspace.

Gharart Scenario

AI strategy publishing with QA approval gates.

Persona: Platform governance manager

Business goal: Coordinate knowledge ingestion, agent proposals, QA validation, and admin governance before production rollout.

Step-by-Step Flow (UI + API)

  1. Open the relevant Gharart workflow in the dashboard and confirm actor role access.
  2. Execute route calls in sequence for this use case and capture response IDs.
  3. Validate expected state in UI and API after each step before moving forward.
  4. Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.

Primary API Routes

MethodPath
DELETE/v2/handles/{handle}/knowledge/documents/{documentId}
DELETE/v2/handles/{handle}/qa/environments/{environmentId}
DELETE/v2/handles/{handle}/qa/suites/{suiteId}
POST/v2/support/report
GET/v2/handles/{handle}/agent/proposals
GET/v2/handles/{handle}/agent/recommendations
GET/v2/handles/{handle}/agent/runs/{runId}
GET/v2/handles/{handle}/agent/strategy/context/{contextId}
GET/v2/handles/{handle}/knowledge/documents
GET/v2/handles/{handle}/knowledge/usage
GET/v2/handles/{handle}/qa/environments

Limits and Quotas

  • Respect per-route throttles and daily write limits before bulk operations.
  • Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
  • Schedule high-volume workflows outside peak campaign windows where possible.

Where This Breaks

  • knowledge query quality drops after stale ingest index
  • agent run blocked due active risk cap and proposal conflicts
  • qa runner lease heartbeat misses causing run stuck state

How Gharart Debugs It

  1. Check knowledge rebuild status before agent recommendation fetch
  2. Review pending agent proposals and risk summary before approve
  3. Validate QA runner heartbeat and lease acquisition timeline

Escalation

Use end-user escalation path:

  • Submit POST /v2/support/report.
  • Include summary, details, and when available handle, sessionId, requestId, reproArtifact.

Audience boundaries:

  • POST /v2/operator/escalations is an internal operator workflow and not an end-user escalation action.
  • POST /v2/public/content-report is for public abuse moderation reports, not product incident escalation.