KKissan Ki Pehchan
Architecture

Component Boundaries

Stable responsibilities and contracts across live media, reasoning, data and control.

BlueprintVersion 0.25 Aug 2026

Stable contracts

ComponentOwnsMust not own
Mobile clientcamera/microphone UI, local preview, network state, permissions, queued fallbackvendor secrets, final treatment authority
Live media planeWebRTC rooms, tracks, TURN, participant authorization, telemetryagricultural reasoning or long-term case authority
Realtime agentstreaming STT/TTS, interruption, frame sampling, camera guidance deliverypolicy authorization or raw media retention policy
Case servicedurable case/session state, access, status, snapshotsprovider-specific model logic
Reasoning agenthypotheses, questions, tools, research, stoppingexact registration/dosage authority
Model gatewayprovider routing, versions, schemas, redaction, quotasbusiness workflow authority
Knowledge/context servicesretrieval, provenance, environmental contextfarmer-facing final decisions
Policy serviceexact legal/numerical checksgeneral diagnosis reasoning
Review servicequeue, officer join, handoff and dispositionsilent override without audit

Failure isolation

  • A model outage must not terminate an already connected room without explanation.
  • A media-plane failure must preserve the durable case and allow reconnect or queued fallback.
  • A video-sampler failure must set visual evidence unavailable rather than reusing stale frames.
  • A research outage must not weaken local-policy verification.
  • A policy outage blocks exact treatment claims.