Terms and limits

Core terms

Intent — the outcome expressed in your request, including relevant constraints and payload.

Capability — a discoverable, callable function with an explicit input and output contract. It may already exist or be materialized from available building blocks.

Materialization — the process of resolving how a requested capability can be created or made executable from available resources.

Environment — the Elyxis scope where applications and operational resources are managed and run.

Environment Setting — a named setting containing configuration entries, owned by an environment. Names are unique within the environment. All settings in the selected environment contribute configuration.

Keystore — an Environment-scoped store managed by Elyxis or connected to an external secret provider. Settings can reference its secret values.

Plugin — an installed integration or processing building block, with configuration and payload requirements.

Flow — the definition of processing steps and their connections.

App — a runnable application prepared from a Flow and its configuration. A Draft App is an intermediate resource used in preparing it.

See how the concepts fit together for a worked example and links to each guide.

Clarification — one or more questions requesting input that Elyxis cannot safely infer.

Confirmation — explicit approval or rejection of a displayed proposed action.

Session context — selected resource bindings retained by the CLI for the Assistant session. Inspect it with /context.

What the Assistant can do

Depending on your permissions and available Elyxis resources, the Assistant can inspect resources, discover capabilities, propose or execute managed changes with confirmation, materialize capabilities, and invoke executable capabilities.

What it cannot safely infer

The Assistant should not invent credentials, secret configuration, missing business requirements, an ambiguous production target, or permission it does not have. It may ask for clarification or report a configuration requirement instead.

Important boundaries

• Natural-language confidence is not execution evidence.
• A plan is not a mutation.
• Confirmation is not completion.
• Creation is not always readiness.
• Readiness is not execution.
• Suggested actions are not completed actions.
• Conversation context is not an authorization mechanism.

Current client boundary

The CLI retains recent conversational context and safe selected-resource context locally for the session, while pending confirmation state is coordinated with the server. Use /new, /clear, /history, and /context to manage and inspect what the client retains.

Security boundary

Never place passwords, access tokens, private keys, or other secrets into ordinary Assistant requests. Use the Elyxis configuration and key-store facilities approved for your workspace.