Authority Signal
AI systems can propose actions. Who decides if they are allowed to execute?
Ophaelis governs whether AI-proposed actions are allowed to cross the execution boundary.
Credentials revoked. Funds transferred. Access removed. Or nothing happens.
AI can advise. Ophaelis authorizes.
Decisions resolve against policy and intent packs under human governance.
SEE IT LIVE
You shouldn’t have to imagine this. Watch a governed decision reach the execution boundary.
Watch proposals, policy evaluation, and authorization resolve in sequence.
Internal environment. If enabled, external AI providers generate untrusted proposals; Ophaelis remains deterministic and policy-authoritative.
Decision Replay
Scheduled evaluation is active. This view updates after the next run.
—
—
—
Receipts
Ophaelis Authority Console
- The system is proposing a high-impact action.
- That action could materially change live operations.
- Ophaelis applies policy authority before any execution step.
- The next step follows the compliant path shown below.
- Request received Pending
- Policy pack resolved Pending
- Advisory/provider step Pending
- Deterministic authority decision Pending
- Authorization issued or withheld Pending
- Execution blocked or permitted Pending
Proposed Action
Governance Evaluation
- Constraints will populate after decision.
- Policy and intent pack resolution pending
- Capability gating pending
- Irreversibility and human-approval checks pending
Authority Decision
- Compliant alternatives will be proposed after policy evaluation.
Receipt + Execution Authorization
- Generated after decision
Guarded Execution Check
Decision Lab
- Event: Admin privilege escalation attempt
- Environment: Production
- Location: New country login
- Confidence: High detection signal
- Requested Action: Immediate irreversible containment
- (none)
- Environment: —
- Account Type: —
- Confidence: —
- Irreversibility: —
- Requested Actions: —
- Permitted Actions: —
- Blocked Actions: —
- (none)
AI Advice
- (none)
- No proposals yet. Click Evaluate to generate proposals and run governance.
| Signal | AI Proposal | Policy Final |
|---|---|---|
| Risk | - | - |
| Confidence | - | - |
| Reversibility | - | - |
Policy Evaluation & Trace
Technical Details
This is the Founder / Operator Control Room. It shows whether Ophaelis is healthy, what it recently decided, and what proof ran most recently. Commands stay disabled until admin auth is designed.
Ophaelis is evaluating decisions. Execution halt is off.
Controlled enablement path. Safe actions can proceed with boundaries.
Models can suggest actions. Ophaelis decides what may execute.
Decision Anatomy
System or AI proposes an action
Intent and context are evaluated
Policies determine what is allowed
Requested actions must exist in the capability ledger
Ophaelis returns allow, deny, or escalate
Action only runs if explicitly authorized
Example: Audit Log Tampering Attempt
Delete audit logs
Destructive, irreversible action affecting protected data
Audit logs are protected and cannot be removed
delete_audit_logs is known but restricted
Denied
Action is blocked before execution
Example: Audit Log Export for Investigation
Export last 24 hours of audit logs
Legitimate investigation request with bounded scope
Audit logs may be accessed but not modified or deleted
export_audit_logs is allowed with constraints
Allowed with boundary (requires confirmation or limited scope)
Export proceeds only within approved scope
Ophaelis sits between decision and execution. Nothing runs unless it is authorized.
Ophaelis prevents destructive actions even when requested by an AI or system.
Ophaelis allows safe actions, but only within explicitly approved boundaries.
Reality Check
- Deployed Worker gateway
- Protected decision endpoint
- Capability ledger
- Live Proof scenarios
- Audit persistence
- Smoke test validation
- Top summary cards
- Decision Anatomy examples
- Command Preview
- Latest proof display
- System status display
- Latest proof summary
- Capability coverage
- Status snapshot
- Recent decisions
- Operator events
The engine exists. This console is becoming the safe operator surface around it.
Next Wiring Order Explained
1. Latest Proof Summary
Meaning: Shows the most recent Live Proof run and whether Ophaelis blocked, allowed, or constrained execution.
Why it matters: This tells the founder whether the authority engine is still proving the right behavior.
2. Capability Coverage
Meaning: Checks whether every scenario uses capabilities that exist in the ledger.
Why it matters: This prevents fake or ungoverned actions from sneaking into demos.
3. Status Snapshot
Meaning: Shows operational state, including whether execution halt is active.
Why it matters: This tells the operator whether Ophaelis is open for decision evaluation or intentionally halted.
4. Recent Decisions
Meaning: Shows real decision receipts produced by Ophaelis.
Why it matters: This proves the system is producing auditable outcomes.
5. Operator Events
Meaning: Shows admin/operator actions such as halt changes or fail-closed triggers.
Why it matters: This creates accountability around changes to the authority layer.
These should be wired as read-only data first. Commands come later, after admin auth and server-side protection.
Customer Integration Flow
This is how a customer system would use Ophaelis before any high-risk action executes.
Phase 1 Product Model
Customers keep their credentials, infrastructure, and execution systems. Ophaelis owns the authorization decision before sensitive actions run.
This keeps Ophaelis privacy-aligned while still enforcing the execution boundary.
1. Customer System
A product, workflow, or AI agent is about to perform a sensitive action.
2. Proposed Action
The system sends Ophaelis the intent, context, environment, and requested capabilities.
3. Ophaelis Authority Check
Ophaelis evaluates policy, intent, capability, risk, and execution boundaries.
4. Decision Receipt
Ophaelis returns an auditable decision: allow, deny, withhold, or allow with boundary.
5. Execution Gate
The customer system executes only if Ophaelis explicitly authorizes it.
The customer owns execution. Ophaelis owns authorization.
Example: before deleting logs, moving funds, changing access, or exporting sensitive data, the customer system calls Ophaelis.
Founder Console
Tells the operator whether Ophaelis is allowed to evaluate decisions or whether execution is halted.
- Execution halt state will come from
/api/admin/status-snapshot. - Recent operator events will come from
/api/admin/events/recent. - Capability coverage will come from
/api/admin/live-proof/capability-coverage.
Shows the most recent proof scenario used to verify the authority engine.
Latest scenario, run source, verdict, and explanation will come from /api/admin/live-proof/latest-summary.
Shows recent governed decisions and why execution was allowed, constrained, withheld, or denied.
- Recent decisions
- Cybersecurity decisions
- Denied decisions
- Human authority decisions
- Missing context decisions
- Allowed with boundary decisions
Recent decisions and outcome-specific feeds will come from existing admin decision summary endpoints.
Shows advisory model evidence later. Index can inform Ophaelis, but Ophaelis authorizes changes.
- Current live advisory providers: OpenAI + Anthropic
- Index role: evidence layer
- Ophaelis role: authority layer
Provider evidence remains advisory. Index informs; Ophaelis authorizes.
Index informs. Ophaelis authorizes.
Commands are intentionally disabled in this public/mock surface. Real commands require admin auth and server-side protection.
-
Status snapshot
Source:/api/admin/status-snapshot
Purpose: execution halt state + recent operator signal -
Capability coverage
Source:/api/admin/live-proof/capability-coverage
Purpose: pre-demo scenario safety check -
Latest live proof summary
Source:/api/admin/live-proof/latest-summary
Purpose: operator-friendly view of latest proof state -
Recent operator events
Source:/api/admin/events/recent
Purpose: control-plane activity timeline -
Decision feeds
Sources:
-/api/admin/decisions/recent-summary
-/api/admin/decisions/recent-cyber-summary
-/api/admin/decisions/recent-by-domain
-/api/admin/decisions/recent-by-class
Purpose: inspect decisions by outcome/domain/class -
Provider / Index recommendations
Future source: Index/Ophaelis recommendation pipeline
Purpose: Index informs; Ophaelis authorizes
Admin wiring should not happen in the public browser until authentication and access boundaries are intentionally designed. This panel documents order, not active data access.
| created_at | tenant_id | domain | intent_id | verdict | authority_level | risk_level | confidence_level | reversibility_level | requires_human_confirmation | policy_pack_hash | intent_pack_hash | proposals_status | proposal_strategy_used | openai_ok | anthropic_ok |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| No decisions yet. | |||||||||||||||
| created_at | tenant_id | domain | intent_id | verdict | authority_level | risk_level | confidence_level | reversibility_level | requires_human_confirmation | policy_pack_hash | intent_pack_hash | proposals_status | proposal_strategy_used | openai_ok | anthropic_ok |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| No decisions yet. | |||||||||||||||
What This Console Is For
Internal founder/operator visibility into Ophaelis governance truth: provider health, recent governance decisions, and Decision Lab workflows.
What Each Tab Means
- Overview: fast operational pulse and latest decision snapshots.
- Decisions: fuller audit rows with lightweight filtering.
- Decision Lab: evaluator/testing flow; not source of production truth.
- Read Me: internal runbook and reminders.
Healthy vs Degraded
- Healthy: providers responding, low recent failures, decisions flowing.
- Degraded: repeated provider errors, stale timestamps, or failing refresh.
Deploy / Build Commands
npm install npm run build npm run deploy
Refresh / Cache-Bust Troubleshooting
1) Click Refresh in Overview. 2) Hard refresh browser (Ctrl+Shift+R). 3) Verify /api routes are returning JSON. 4) Re-run build and redeploy if UI is stale.
Ophaelis Today: Is / Is Not
- Is: deterministic governance authority with auditable policy enforcement.
- Is Not: autonomous destructive executor; delete/prune controls are not active.