Compact Density
Tightens cards, tables, and proof records for operators reviewing many events.
NEHRAQ
Open the Nehraq OS Manual for step-by-step setup, app explanations, workflows, FAQs, and BETA guidance.
Manage account profile, team roles, notifications, integrations, security posture, billing, reports, and workspace-level operating preferences for the Liability OS.
Manage the reviewer identity used for approval receipts, authority decisions, workspace activity, and proof records inside the Liability OS.
Risk Lead · Authority Reviewer
Browser-demo image preview only. No backend upload is performed in this phase.
Manage approved workspace members who can review, approve, deny, request context, own evidence obligations, and appear in Nehraq responsibility records.
Can review AI actions.
Awaiting approval.
Kept for history.
Core roles covered.
Control how the Liability OS behaves in your browser workspace: density, default view, live refresh behavior, demo visibility, theme preference, and proof display style.
Tightens cards, tables, and proof records for operators reviewing many events.
Allows proof rollups and runtime views to refresh from browser proof state.
Keeps browser-demo proof packages, approvals, incidents, and packet records visible.
Choose where this workspace should start when entering the Liability OS.
Control how proof-heavy views show evidence records, demo data, and OS emphasis.
This is localStorage only. Later these preferences can become workspace-level saved settings.
Configure how AI agents, agent platforms, enterprise systems, and downstream tools route high-risk actions through Nehraq before execution. This is browser-demo only for now.
Define the system that will route high-risk actions through Nehraq.
These are demo connection values. Later they will be generated by the backend.
Loading SDK snippet...
This creates a browser-demo integration test event. It does not call a real backend yet.
Nehraq access is organized around risk-controlled AI workflows, enforcement volume, and evidence requirements. No public pricing is shown during BETA. Sandbox/BETA access is free for approved evaluation workspaces. Production access is reviewed by workflow risk and deployment readiness.
Sandbox/BETA access is free for approved evaluation workspaces. Production activation is not self-serve. Nehraq reviews the controlled workflow, connected agents, approval responsibilities, evidence needs, retention expectations, and operating risk before enabling production access.
Sandbox is an evaluation access category for approved BETA workspaces. It lets teams test sample agents, boundary checks, approval flows, evidence receipts, and the Refund Approval Control Pack before production activation.
For teams controlling several AI workflows across support, finance, compliance, operations, or customer experience.
For regulated organizations, high-volume AI vendors, and teams with custom evidence, retention, security, or legal review requirements.
Each control pack defines the AI action, authority boundary, approval path, receipt type, and evidence export.
Controls approve, deny, escalate, and promise refund actions.
Controls compensation promises, policy exceptions, and unsupported commitments.
Controls account changes, access resets, unlocks, and sensitive profile modifications.
Controls regulated responses, disclosures, notices, and sensitive customer communications.
Controls fraud flags, holds, account freezes, and sensitive investigation actions.
Controls vendor promises, purchasing commitments, and third-party obligation changes.
Controls agent-triggered workflows, escalations, automations, and downstream actions.
Controls credits, waivers, adjustments, reversals, and payment-sensitive actions.
Access reviews consider the risk-controlled workflow, number of connected agents, boundary-check volume, Verified Action Receipt volume, approval roles, evidence retention, packet exports, and security requirements.
Control reviewer authentication, privileged action review, evidence protection, retention posture, and browser-demo security readiness for the Liability OS.
Browser-demo posture.
Ledger safety posture.
Privileged action control.
Reviewer access window.
Require a 6-digit reviewer code before sensitive workspace access and authority actions.
Active evidence records cannot be hard-deleted. Removal flows go through retention review.
Sensitive changes require authority review before they affect proof posture.
Evidence marked for legal hold remains protected for incident and claim-defense workflows.
Browser-demo policy controls for reviewer access, session limits, and workspace authority posture.
Demo posture for future API keys, agent middleware secrets, webhook signing, and credential rotation.
Nehraq should preserve defensible records. Archive, retention review, legal hold, and removal review are acceptable. Permanent deletion is not part of the active evidence workflow.
Build browser-demo summaries from Nehraq proof state: boundary decisions, human oversight, evidence records, incident exposure, regulatory coverage, liability passports, and claim readiness.
All proof inputs.
Human oversight queue.
Blocked / restricted.
Packet builder outputs.
Proof readiness.
Executive proof digest for operators, risk owners, and workspace administrators.
Maps proof records to EU AI Act, NIST AI RMF, ISO 42001, GDPR, HIPAA, and internal controls.
Summarizes whether the workspace has enough defensible proof to support a claim-ready packet.
Build a report above to generate a browser-demo report snapshot.
Route important Liability OS events to reviewers, workspace owners, legal, compliance, privacy, and risk leads. Browser-demo only — no email, SMS, Slack, or backend delivery yet.
Needs attention.
Human review.
Restricted / blocked.
Evidence events.
Notify required authority when an AI action enters human approval.
Notify risk, legal, and compliance when restricted actions become defense candidates.
Notify workspace owners when proof records are added to the Evidence Ledger.
Notify legal and risk reviewers when a packet has enough proof to preview.
Notification routing is mapped to workspace authority roles. Later this will connect to email, Slack, Teams, webhooks, and in-app notification delivery.
| Event Type | Primary Recipient | Backup Role | Linked App | Status |
|---|---|---|---|---|
| Approval Escalation | Required Authority | Risk Lead | Approval Desk | Enabled |
| Incident Candidate | Legal Reviewer | Compliance Owner | Incident Defense | Enabled |
| Proof Record | Workspace Owner | Evidence Owner | Evidence Ledger | Enabled |
| Claim Packet | Legal Reviewer | Risk Lead | Claim-Ready Packets | Enabled |