ai-draft

Enterprise Part of the commercial Kumiko Enterprise offering — not in the open framework.

Query handler (ai-draft:query:draft) that takes a source message (subject, sender, body) and a stated purpose, then returns a ready-to-send draft reply via the tenant’s configured LLM provider. The system prompt is editable per-tenant through a config-key or the prompt-store (no deploy required); the caller is responsible for sending or storing the returned draft in a separate write action.

How it fits

What this feature needs to run (Requires, top) and the write commands it provides (Provides, bottom).

flowchart TB
  n_ai_draft["ai-draft"]
  subgraph how_reqs["Requires"]
    n_ai_foundation["ai-foundation"]
    n_config["config"]
    n_prompt_store["prompt-store"]
  end
  n_ai_foundation --> n_ai_draft
  n_config --> n_ai_draft
  n_prompt_store --> n_ai_draft

Dependencies

• Requires: ai-foundation, config, prompt-store
• Activation: always on (not toggleable)

Configuration

Per-tenant config keys, set via the tenant-admin UI or a seed. 🔒 = encrypted at rest.

Key	Type	Default	Scope	Who can write	Who can read
draft-system-prompt	text	You draft a reply message for a business application.\n\nGiven the source message and the stated purpose, write a professional, concise reply.\n- Match the language of the source message unless a target language is given.\n- Courteous and to the point; avoid placeholders like [name] unless unavoidable.\n- Return the draft via the draft_message tool (subject + body).\n\nIf the purpose is unclear or you are missing information you cannot reasonably assume, call clarify_request instead. Call exactly one tool.	tenant	TenantAdmin, SystemAdmin	TenantAdmin, SystemAdmin