Glosario
El vocabulario de una ontología de negocio ejecutable.
Definiciones de los términos que usa este sitio, escritas para ser citadas. Cada entrada abre con una frase que se sostiene sola, explica después qué significa el término en la práctica y enlaza los artículos y páginas que lo usan.
5 términos
-
Flujo de aprobación
Un flujo de aprobación es un proceso de negocio en el que un cambio propuesto queda retenido en estado pendiente hasta que una persona con autoridad para decidir registra una aprobación o un rechazo explícitos, de modo que el cambio solo surte efecto después de que alguien responsable lo haya firmado.
-
Grafo de conocimiento
Un grafo de conocimiento representa la información de una organización como nodos y aristas tipadas —las entidades que le importan y las relaciones etiquetadas entre ellas—, de modo que las preguntas sobre cómo se conectan las cosas pueden responderse recorriendo esas relaciones en lugar de haciendo joins entre tablas.
-
Ontología
Una ontología, en el sentido en que la usa ObjectStack, es una ontología de negocio ejecutable: la definición de un negocio —sus objetos y campos, relaciones, acciones, permisos, flujos y definiciones de agentes y herramientas— escrita como metadatos tipados que un runtime valida y después ejecuta, de modo que el software y los agentes de IA operan el negocio a través de esa única definición y no a través de tablas en bruto.
-
Seguridad a nivel de fila
La seguridad a nivel de fila (RLS) es un mecanismo de control de acceso que limita qué filas de una tabla puede leer o escribir un usuario concreto adjuntando un predicado a la propia tabla, de modo que la restricción se aplica dentro de la consulta y no en el código de aplicación que la emite.
-
Capa semántica
Una capa semántica es un conjunto gobernado de definiciones de negocio —métricas, dimensiones y nombres de entidades— situado entre el almacenamiento de datos en bruto y las herramientas que lo consultan, de modo que «cliente activo» o «ingresos netos» se resuelven en un único cálculo acordado sin importar quién pregunte ni desde qué herramienta.
Aún sin traducir
Estos términos se muestran en inglés hasta que exista una traducción.
18 términos
-
Agent guardrails
Agent guardrails are the constraints placed on what an AI agent may do — from prompt instructions and output filters to runtime permission checks, approval gates, and audit logging — and they divide into the ones an agent can ignore and the ones it cannot.
-
AI agent runtime
An AI agent runtime is the execution environment that runs an agent loop — calling the model, invoking tools, carrying state and memory between steps, and handling retries, timeouts, and concurrency — so that an agent runs as a supervised program rather than as a single prompt.
-
Application definition vs. runtime
Application definition vs. runtime is the architectural split between what an application is — a typed, version-controlled declaration of its objects, fields, relationships, permissions, workflows, actions, and APIs — and what runs it: an engine that reads that declaration on every request and derives the database, the API, the interface, and the permission and audit enforcement from it, so that the definition stays portable and the engine stays replaceable.
-
Application metadata
Application metadata is the structured, typed definition of a business application — its objects, fields, relationships, views, permissions, workflows, actions, and APIs — stored as source files that a runtime reads and executes directly, rather than as generated application code.
-
Audit trail
An audit trail is a chronological, append-only record of who did what to which data and when, written by the system that executed the actions rather than by the parties performing them, so that history can be reconstructed and attributed after the fact.
-
Comprehension debt
Comprehension debt is the widening gap between the software an organization runs and the software anyone in it can still explain — a liability that accrues whenever working code ships faster than the understanding of it, and that comes due at the first change nobody dares to make.
-
Declared vs. enforced
Declared vs. enforced names the gap between what a system’s configuration lets you write down and what its runtime actually checks at execution time — a declaration that nothing enforces reads like a guarantee and behaves like a comment.
-
Definition layer
The definition layer is the tier of a software stack that holds a business’s own declarations — which objects exist, how they relate, who may do what to them, and which steps require approval — as versioned files the organization owns, sitting above the runtime layer that executes those declarations and outside any single vendor that happens to ship an engine for them.
-
Governed runtime
A governed runtime is an application runtime that enforces identity and permissions on every read, write, and tool call, routes decisions through approvals, and writes reads and writes to an audit log, so that an AI agent and the person it acts for are held to exactly the same rules. In ObjectStack, record reads and writes are audited; the built-in AI’s tool calls are audited too on ObjectOS Enterprise.
-
Governed tool layer
A governed tool layer is the layer between an AI agent and a business system in which the agent calls controlled actions rather than raw interfaces, so that every call carries the initiating user identity, is checked against that user permissions, pauses for approval when the action requires one, and lands in an audit ledger.
-
MCP (Model Context Protocol)
MCP (Model Context Protocol) is an open standard that defines how an AI application connects to external tools, data sources, and prompts over a uniform client–server interface, so that any compliant client can use any compliant server without integration code written for that specific pair.
-
Metadata-driven development
Metadata-driven development builds an application by declaring its objects, fields, permissions, workflows, actions, and APIs as typed metadata that a runtime executes directly, instead of writing the code that implements them — a distinction that becomes decisive once an AI agent is doing the writing, because the declaration is small enough for a human to review and the runtime, not the generated code, is what enforces the rules.
-
Object type / action type
Object type and action type are the two halves of an ontology's vocabulary: an object type declares a class of business entity together with its properties and its links to other types, while an action type declares a permitted, permission-checked operation that changes those objects — so that writing is defined as explicitly as reading.
-
Ontology projection
An ontology projection is a view, dashboard, app, or translation derived from an executable business ontology — authored as metadata and validated by the same gate, but not part of the ontology itself, so that changing the core changes the projection while removing a projection leaves the business it showed unchanged.
-
Permission model
A permission model is the structure a system uses to decide who may do what — which principals exist, which containers hold grantable capability, how multiple grants combine, and what happens when nothing grants access — as distinct from any individual permission expressed within it.
-
Reviewable diff
A reviewable diff is a change small enough, and expressed at a high enough level, that the person accountable for it can read every line and judge on business terms whether it is right — the property that decides whether AI-written software gets merged with a signature behind it or on faith in green CI.
-
Typed metadata
Typed metadata is application metadata whose keys and values are constrained by a published schema, so that an unknown field type, a misspelled permission, or a workflow step pointing at an object that does not exist is rejected at a validation gate when the definition is written, instead of being discovered in production after it runs.
-
Vibe coding
Vibe coding is the practice of building software by describing what you want to an AI model in natural language and accepting the code it produces without reading or understanding it — a term Andrej Karpathy coined in February 2025 for giving in to the vibes until you "forget that the code even exists."