Reference
This reference defines the public terminology used across CoreVexa, VEXA, the CoreVexa Governance Standard, Layer-7, governed execution, and related documentation.
Definitions on this page describe public product concepts and observable behavior without publishing proprietary implementation schemas, internal routing logic, private services, or confidential CoreVexa intellectual property.
CoreVexa Terms
CoreVexa Labs
The organization developing CoreVexa governed infrastructure, VEXA, CGS, and related products and governance capabilities.
VEXA
CoreVexa Labs’ governed AI workspace and execution platform for moving from objectives and current-state understanding through governed action, evidence, outcomes, and reevaluation.
CGS
The CoreVexa Governance Standard. CGS defines the public governance model for decisions, authority, risk, gates, escalation, evidence, and pre-execution control.
Layer-7
The CoreVexa governance enforcement model positioned between proposed intent and consequential execution.
Governance Console
A CoreVexa operational control surface for observing governed decision review, approval, blocking, risk, and evidence.
Governed Execution
Consequential action that proceeds only after the applicable governance and authority requirements have been satisfied.
CGS, Layer-7, and VEXA
VEXA provides the user-facing environment in which governed work can move through this model.
CGS Object Categories
Decision
The proposed consequential action and the context required to govern it.
Authority
The person, role, or approved authority structure permitted to authorize, deny, escalate, or govern a decision.
Risk
The relevant operational or consequential exposure associated with a proposed action.
Gate
The governance outcome that determines whether execution may proceed, requires further approval, or remains blocked.
Escalation
Movement of a governed decision to a different or higher authority when additional review is required.
Evidence
Information retained to support review and reconstruction of governed decisions and resulting execution.
Pre-Execution Path
Intercept
Capture the proposed consequential action before execution.
Structure
Represent the action with enough context for governance.
Score
Evaluate relevant operational or consequential risk.
Route
Determine the applicable authority or approval path.
Enforce
Apply the resulting governance gate before execution.
Ledger
Preserve evidence of the governed decision path.
Canonical Journey Stages
VEXA’s First Journey uses ten canonical stages. A journey stage represents a governed position in the lifecycle. A screen or state represents an interaction occurring inside a stage.
01 — Goal
Defines the objective the workspace is intended to pursue.
02 — Current State
Establishes the relevant present condition before planning forward.
03 — Strategy
Develops the approach for moving from current state toward the goal.
04 — Recommendation
Presents a proposed path, option, or recommended course of action.
05 — Next Action
Identifies the consequential next step under consideration.
06 — Governance
Applies the relevant authority and governance boundary.
07 — Execution
Carries out the authorized work.
08 — Evidence
Captures information demonstrating what occurred.
09 — Outcome
Evaluates the result produced by the executed action.
10 — Reevaluation
Uses evidence and outcomes to determine what should happen next.
Stage
A canonical governed position within the VEXA lifecycle. The First Journey has ten canonical stages.
Screen / State
A visual, interactive, approval, evidence, or functional state occurring inside a journey stage. Multiple states do not create additional canonical stages.
Workspace Terms
Workspace
A persistent governed environment containing context, progress, decisions, evidence, and continuing work.
Current State
The established present condition relevant to the objective being pursued.
Strategy
The approach or path developed to move from current state toward the intended objective.
Recommendation
A proposed course of action generated for user consideration. A recommendation is not automatically an authorized decision.
Next Action
The proposed operational step intended to move the workspace forward.
Outcome
The observed result associated with executed work.
Talk to VEXA
Discussion, exploration, questioning, scenario development, or planning that does not automatically alter governed operational workspace state.
VEXA Execute
Governed operational work that can move through defined workspace state, next actions, authority, execution, evidence, and outcome review.
Information Classes
CoreVexa is designed to preserve meaningful distinctions between different types of information used during reasoning and governed execution.
Verified Fact
Information treated as established through the applicable source or validation process.
User-Provided Information
Information supplied directly by the user or organization.
Assumption
Information being treated provisionally rather than as verified fact.
Inference
A conclusion derived from available context rather than directly supplied fact.
Recommendation
A proposed course of action requiring user or governance consideration.
User Decision
A choice explicitly made by the user or authorized decision-maker.
External Information
Information obtained from an approved outside source or connected system.
Execution Evidence
Information produced or preserved as evidence that an authorized action occurred.
Observed Outcome
The measurable or reviewable result associated with executed work.
Adaptive Experience
A VEXA working environment adapted to the type of work being performed while preserving the underlying governed workspace and authority model.
General VEXA
General governed planning and execution environment.
Business Builder
Business creation and development experience.
CRM
Customer and relationship-focused governed experience.
Creative Operations
Creative planning and execution experience.
Music
Music-focused planning, career, asset, and execution experience.
Domain Experience
An additional VEXA experience adapted to a specific class of work.
Extension
An approved capability that extends VEXA without replacing the governed workspace with a separate uncontrolled mini-application.
Extension Boundary
Extensions can remain subject to defined permissions, data ownership boundaries, governance controls, and execution authority.
Integration Terms
Integration
A defined connection between CoreVexa and an approved external capability or system.
External System
A model, application, data source, workflow, service, or execution capability outside the CoreVexa platform boundary.
Public API
An interface intentionally designated and documented for supported external programmatic use.
Internal Interface
A product or service interface used internally and not automatically part of the supported public API.
Execution Boundary
The point at which a proposed operation becomes consequential action.
Authorized Action
A proposed action for which the applicable governance and authority requirements have been satisfied.
Current-State Entry
VEXA can begin with an organization from the state that already exists rather than requiring the organization to follow a new-company or blank-state journey.
Understand the current state, understand the intended destination, construct the path between them, and preserve final human authority.
Human Authority
Decision authority retained by an authorized person where governance requires human approval.
Approval
An explicit authorization required before a governed action may proceed.
Block
A governance outcome preventing execution because the required conditions have not been satisfied.
Definitions Without Proprietary Implementation Disclosure
This reference defines CoreVexa’s public terminology and product concepts.
It intentionally does not publish protected schemas, private object structures, proprietary scoring methods, internal routing logic, source code, private endpoints, security-sensitive controls, infrastructure topology, orchestration methods, or confidential implementation details.