Skip to content

Natural-language tickets and tighter scope — 3 November2026

Owner explicitly authorized free-prompt ticket creation/status plus polite reasoned refusal for unrelated topics, referring users to Risdikti or their Element Commander. Extend the existing one-call Gemma JSON response with a bounded action enum; the backend owns execution, descriptions, IDs and access checks. No arbitrary model tool calls, ticket edits or staff assignment.

Explicit natural-language creation requires a matching current-user request and enough literal issue text; ambiguous complaints only store a short-lived per-member offer. Short affirmative replies confirm that offer (15-minute expiry), cancellation clears it. No cross-member context or old message-body replay. Creation is idempotent by originating job ID and commits with job completion. Status requests read actual owner-filtered rows, even for staff using WhatsApp, and never expose internal notes.

Keep legacy commands working and enforce obvious unrelated-topic refusal before ticket actions. Model scopes cover P3MDI systems, activities, membership and verified public corps-official duties; unknown organization facts cannot be invented and personal details/gossip are refused. Fixed server-generated polite refusal explains the boundary and directs to Divisi Risdikti/Komandan Elemen. Contextual pizza/recipe refusal does not quote arbitrary user text or private values.

Tests: explicit create, offer/yes/cancel/expiry, insufficient details, duplicate job, own/list/foreign status, invalid/model-invented IDs/actions, no consent, refusal without side effects, multilingual intent, and existing regression suite in an isolated DB. Live model routing probes use generic text only and never execute production ticket writes or send WhatsApp messages. Deploy only API/worker after tests; dashboard remains compatible.