Kotlin / Android SDK

The reference client ships in this repo at app/src/main/java/com/onemedical/healthai/ai/AkharaPolicy.kt. It’s built on OkHttp, kotlinx-serialization, and coroutines. See requirements for versions.

Types

enum class PolicyVerdict { ALLOW, REWRITE, BLOCK, ESCALATE, PAUSE }

data class PolicyDecision(
    val verdict: PolicyVerdict,
    val stage: String,
    val policyId: String,
    val rule: String,
    val reason: String,
    val transformedContent: String? = null,
    val permitId: String? = null,
) {
    val mayContinue: Boolean
        get() = verdict == PolicyVerdict.ALLOW || verdict == PolicyVerdict.REWRITE
}

Construct the PEP

val pep = PolicyEnforcementPoint(
    AkharaPolicyClient(
        baseUrl = "https://api.akhara.dev",
        agentId = "health-ai",
    )
)

Always pass your workspace’s baseUrl (https://api.akhara.dev) explicitly. The client attaches Telemetry.sessionId as the session automatically, and the call timeout is 8 seconds.

The in-repo demo build ships with a loopback default for the Android emulator so it can reach a developer’s machine. Production builds must set baseUrl to the managed PDP over HTTPS.

Methods

suspend fun checkInput(content: String): PolicyDecision
suspend fun checkContextEgress(content: String): PolicyDecision
suspend fun checkOutput(content: String): PolicyDecision
suspend fun checkDelivery(content: String): PolicyDecision
suspend fun authorizeAction(tool: String, args: JsonObject): PolicyDecision

All are suspend and run on Dispatchers.IO. Call them from a coroutine (e.g. inside a ViewModel’s viewModelScope).

End-to-end example

suspend fun handleTurn(userText: String, patientCtx: String): String {
    // 1. input gate
    val input = pep.checkInput(userText)
    if (!input.mayContinue) return refusal(input)

    // 2. context egress: PHI minimization
    val egress = pep.checkContextEgress(patientCtx)
    val modelInput = egress.transformedContent ?: patientCtx

    val draft = assistant.reply(modelInput, userText)

    // 3. output gate
    val output = pep.checkOutput(draft)
    if (!output.mayContinue) return escalateOrDrop(output)

    // 4. delivery gate
    val finalText = output.transformedContent ?: draft
    val delivery = pep.checkDelivery(finalText)
    if (!delivery.mayContinue) return escalateOrDrop(delivery)

    return finalText
}

Permit-gated action

suspend fun requestMedicationRenewal(medication: String) {
    val args = buildJsonObject { put("medication", medication) }
    val permit = pep.authorizeAction("renew_meds", args)

    when (permit.verdict) {
        PolicyVerdict.ALLOW -> {
            val receipt = renewalService.submit(medication, permit.permitId!!)
            // deliver the receipt to the member
        }
        PolicyVerdict.ESCALATE -> queueForClinician(permit)
        else -> refusal(permit)   // BLOCK
    }
}

Fail-closed behavior

Any error, non-2xx, or parse failure yields a synthesized BLOCK:

PolicyDecision(
    verdict = PolicyVerdict.BLOCK,
    stage = stage,
    policyId = "latch-4",
    rule = "Fail-Closed Defaults",
    reason = "Akhara policy authorization is unavailable: …",
)

Two known caveats in the shipped client, called out so you can align a production build with the verdict taxonomy:

WARN handling. The PDP returns WARN, but the enum has no WARN member, so PolicyVerdict.valueOf("WARN") throws and trips fail-closed. Add a WARN member (or map WARN → REWRITE) if your attached policies can return it: for example healthcare-0 context-egress rewrites.
Fail-closed policyId. The client cites latch-4, but the canonical Fail-Closed Defaults policy is reliability-4. Align if you rely on the id.

Get started

How it works

Enterprise onboarding

SDK

Kotlin / Android SDK

Types

Construct the PEP

Methods

End-to-end example

Permit-gated action

Fail-closed behavior

​Types

​Construct the PEP

​Methods

​End-to-end example

​Permit-gated action

​Fail-closed behavior

Types

Construct the PEP

Methods

End-to-end example

Permit-gated action

Fail-closed behavior