FAQ

Help

FAQ

Common questions about Corevexa, Layer 7 governance, approvals, audit logging, and deployment. This page is written for executives, operators, and engineering teams.

Governance fundamentals Approvals + authority Audit + ledger Deployment + integration

Core Principle (Power Move)

Corevexa is not built to generate AI outcomes. It is built to govern outcomes — to make authority enforceable and auditability non-optional.

If an action is High or Critical risk: no approval, no execution. And the ledger proves it.

Questions

What does “Layer 7 governance” mean?
It means governance is enforced at the decision and execution layer — where actions are approved, routed, logged, and either permitted or blocked. It is not policy on paper. It is policy enforced by the system.
How is Corevexa different from automation tools?
Automation tools focus on execution (“do the thing”). Corevexa focuses on permission, authority, and audit (“should this execute — and who approved it?”). Corevexa can sit between AI/automation and execution as an enforcement gate.
Does Corevexa replace my AI models or agents?
No. Corevexa governs them. Your AI systems can continue generating proposals and actions. Corevexa evaluates and routes those actions, enforcing approvals when required.
What happens when an action is High risk?
High risk actions are routed to an Executive approval queue. Execution remains blocked until an authorized executive issues an approval signature bound to the decision_id.
What is multi-signature approval?
For Critical actions, Corevexa can require multiple independent approvals (e.g., 2 signatures from different executives). This supports separation of duties and reduces single-point-of-failure approvals.
What is the Decision Ledger and why does it matter?
The Decision Ledger is the immutable audit record of what was proposed, how it was scored, what authority was required, who approved or rejected it, and whether it executed. If it executed and it’s not in the ledger, it’s treated as a governance breach.
Can Corevexa run on-premises?
Yes. Corevexa supports SaaS, On-Prem, Hybrid, and Air-Gapped deployment models. The governance guarantees remain consistent across all models.
How do systems integrate with Corevexa?
Systems submit actions to the API for evaluation. Corevexa returns a decision_id and governance outcome. If approvals are required, authorized users approve via control surfaces. Execution then proceeds based on the satisfied authority set.
What is the Executive Panel?
The Executive Panel is the controlled approval surface for High/Critical actions. It presents the decision context and records approvals as signature events in the ledger.
What is the Creative Ops Panel?
The Creative Ops Panel is a governed surface for marketing/media operations. It submits campaign actions into the same Layer 7 pipeline and routes high-risk decisions to executives.
Do I need Corevexa hardware products?
Not always. Hardware strengthens assurance in strict environments: edge enforcement (EGD-1), infrastructure enforcement mesh (IGN-1), executive on-prem control plane (EGA-1), hardware authority signatures (EAT-1), and real-time visibility (GCW-1).
What’s the fastest way to prove Corevexa works?
Run the Layer 7 evaluation flow end-to-end: submit an action, receive a High tier result, approve it via the Executive Panel, and confirm the ledger reflects approval + execution status.

Next: Getting Started

Use Getting Started to deploy a demo, submit your first governed action, and validate approvals and ledger history.