Kona AIKona Business AIEvidence-backed business planningExplore Kona
Chat for answers. Workspace for defensible work.
Product readiness
This register separates working product paths from limited support and roadmap intent. It is a capability boundary—not an uptime promise, certification, or substitute for reviewing AI output.
An operational product path exists and can be exercised now.
Operational within the boundary stated on the capability.
Not generally available; listed so the boundary is explicit.
Ask business questions, analyze supplied context, and request web research with source links when research is used.
Current boundary
Generated answers can still be incomplete or wrong. Source links support review; they do not certify every sentence.
Turn a decision brief into persistent planning work with sources, assumptions, scenarios, review flags, versions, and exports.
Current boundary
Workspace is strongest for structured business planning. Complex outputs still require user review before external use.
Keep source records, editable assumptions, formula lineage, verification state, and artifact versions attached to planning work.
Current boundary
The ledger makes evidence gaps visible; it does not automatically prove that a source supports every generated claim.
Compare base, downside, and upside cases using editable inputs and deterministic calculations.
Current boundary
Scenario quality depends on the supplied inputs. Kona exposes missing inputs instead of treating estimates as facts.
Export supported work to formats such as DOCX, XLSX, PPTX, CSV, Markdown, and PDF.
Current boundary
Available formats and formatting depth depend on the artifact. Exported work should be reviewed before delivery.
Use supported documents, spreadsheets, presentations, data files, and images as context in Chat and Workspace.
Current boundary
Exact page, slide, sheet, or cell citations are not available for every file type, and large or image-only files may need preprocessing.
Provider-backed reads exist for Stripe, HubSpot, Google Analytics 4, QuickBooks, and Google Workspace.
Current boundary
A provider connection and permissions are required. Other connector catalog entries are setup-only and do not imply a working adapter.
Create one-time or recurring tasks when persistent storage and background dispatch are enabled for the deployment.
Current boundary
This is not a contractual job-delivery service; failures and delayed runs must remain visible to the user.
Generate and revise project files with a preview and isolated runtime when the runtime provider is available.
Current boundary
Kona does not deploy generated code to production without a separate provider connection and explicit user action.
Use speech input and response playback in supported browsers.
Current boundary
Full-duplex realtime voice is not a generally available Kona capability.
Provider write operations remain disabled while verification, approval, idempotency, and rollback contracts are developed.
Current boundary
Approval screens are control foundations; they do not mean Kona can currently modify a connected service.
Enterprise SSO, SCIM, independently audited controls, and a complete immutable audit log are roadmap work.
Current boundary
Kona does not currently claim enterprise certification or a contractual control framework.
See the evidence
The ClinicFlow sample is fictional and exposes its public sources, editable assumptions, three scenarios, and unresolved input flag.