Skip to main content

Chat Things Into Existence

Valor is designed for users who know what they want but do not necessarily know which schema, workflow, ExecModule, credential, model, or deployment path should be used.

Intent Patterns​

User saysValor should create or prepare
"Build me a dating app for local events."Requirements, ThorAPI schema draft, generated app plan, workflow list, deployment plan, ValorIDE handoff.
"Turn this spreadsheet into an API."OpenAPI schema, Rune formula candidates, generated API/model/database path, Sheetster view.
"Post new CMS articles to social every Monday."ValkyrAI workflow with CMS query, LLM title/copy module, social ExecModules, scheduling, audit.
"Publish this workflow as an MCP tool."MCP metadata, workflow validation, RBAC checks, marketplace publish payload.
"Help my agents remember this decision."GrayMatter memory write with tags, relationships, confidence, and RBAC scope.

Reviewable Action Loop​

Valor should operate in a reviewable loop:

  1. Understand the user persona, subscription entitlements, and RBAC-visible capabilities.
  2. Inspect GrayMatter memory and relevant object graph context.
  3. Draft a concrete plan using ThorAPI schemas, app templates, workflow modules, and IntegrationAccounts.
  4. Execute only permitted tool actions.
  5. Show the created or changed object.
  6. Persist durable memory when the result should inform future work.

Persona-Aware, RBAC-Governed​

Persona mode changes the language, density, defaults, and suggested next actions. It does not grant permissions. A CXO may see strategy and GrayMatter controls first; a solopreneur may see app builder, CMS, CRM, and ecommerce paths first; an engineer may see API Designer, generated clients, deployment, and ValorIDE handoff first.

RBAC still determines what buttons, APIs, objects, and secrets are available.

LLM Providers​

Valor should represent the model layer explicitly. Users may work through:

  • OpenAI models for coding, reasoning, extraction, and multimodal tasks.
  • Claude models for planning, coding, and document work.
  • Ollama/open source models for local or lower-cost execution.
  • Enterprise gateways and configured provider accounts through LLMDetails.

The UX should let users choose a model at the level they understand while preserving exact provider/model metadata for execution.