Chapter 05 / 14

Request journeys

Conversational form preparation

The questionnaire selects a procedure. The conversation endpoint returns typed turns: retrieved-choice questions for known domain values, confirmation turns for proposed values, and ephemeral fill-in turns for data that should not be stored. Each accepted answer targets an explicit form field. The browser frames that field, scrolls the official page into view, and renders the value with Playpen Sans ExtraLight 200. Completion produces a five-page PDF; it does not submit it.

Authentication

Passwords are hashed; access and refresh JWTs are carried in authorization headers. A server-side session row remains the revocation backstop. Operator and end-user identities are separate populations. Reset and verification tokens are random once, stored only by digest, purpose-scoped, expiring, and single-use.

Tool execution

The model proposes a versioned tool call. Python validates the arguments, authenticates the principal, checks resource authorization, derives an idempotency key, records authorization, executes the adapter, and stores bounded outcome evidence. Replays return the established result or state rather than repeating an external action.

Voice enrolment and German telephony

Explicit localized consent precedes capture. Audio is sent to the selected provider and discarded; Postgres retains only provider reference and consent/deletion lifecycle. A call uses the same authorization boundary as any tool. Synthetic presentation calls demonstrate the flow but do not contact a person or authority.

Publication and OTA

Operators create immutable revisions, attach evidence, review, and explicitly publish one version. Android clients call OTA discovery, verify signatures and hashes, download a bundle, and activate only a validated artifact with rollback retained.