FAQ
Does DGI need an LLM?
No. Jev, the typed decision engine, decides most requests on its own, and the LLM is off by default. Without the LLM, a request Jev cannot decide comes back as suggestion chips. Turn the LLM on per chat profile, actor or surface when you want open questions answered. See How DGI works.
Who pays for model use?
You do, through your own AI provider configuration. DGI does not resell tokens. Jev uses your organization's TypeSafe connection.
Can my app's end users use DGI?
Yes, through structured chat, the dgi.chat API and single cards. They run as themselves and can only reach workflows your app exposes to end users. Living Surfaces are for members of your organization only.
Which languages does it speak?
Fixed texts and cards come in English, Brazilian Portuguese and Spanish (en, pt-BR, es). Set a default on the profile, or pass locale per turn. With the LLM on, free-form answers follow the person's language.
What if the workflow a person needs does not exist?
DGI does not improvise. It says what it can do instead. Record the gap with dgi.workflow-request.create so your team can build the workflow, and once it is registered and allowed, DGI can use it right away.
Can DGI change things on its own?
No. Every write is a proposal on a confirm card, and runs only when the person it was issued to confirms it. Scheduled work, such as a Living Surface's heartbeat, only reads.
How is DGI different from an AI assistant over MCP?
They share the same catalog, schemas and permissions. An assistant over MCP is a general agent that calls tools one at a time and answers in prose. DGI is built for your product's own screens: it answers with cards your users can act on, keeps writes behind stored confirms, and does not need a model for most requests. An assistant can also call DGI's workflows.
Can I control how cards look?
Yes. The card is a JSON object. The hosted chat takes a theme document, the React component accepts your own renderers, and with the dgi.chat API or dgi.view.render you draw every card yourself. See the card catalog.
Can a good conversation become an automation?
Yes. A member can promote a plan with dgi.workflow.promote, or crystallize a Living Surface, into a versioned composition that runs as an ordinary workflow with no model call. See Virtual workflows.
Is DGI production-ready?
DGI is Alpha. The interfaces on these pages are available today, and the contracts are versioned. Expect additions, and check the status table before you depend on a capability.