Execution overview.
Intent in. Verified outcomes out.
- 01Trust
- 02Match
- 03Execute
- 04Evidence
- 05Verify
- 06Outcome
Waiting for execution signals.
Connect a workspace and Nexus will surface concise, explainable actions—not a generic chatbot.
Work orders
A scoped view of execution across your workspace.
Your execution network is clear.
Connect a Nexus identity to load its scoped tasks, activity, and review queue.
Create an inspection requestRouting queue.
Organization-scoped work needing routing, reassignment, or assignment monitoring. Suggestions do not override authorization or human judgment.
Operator queue
Deadline urgency, candidate eligibility and active assignment status.
Candidate eligibility is a matching signal, not a guarantee of worker competence. Payment authorization and assignment state are enforced by the server.
Network health.
Runtime nodes, field capacity, and active assignments in this organization.
Assignments across the network
Lines reflect persisted task assignments; runtime workers are shown separately.
Execution nodes
Job health
Persisted worker jobs. Queued jobs require an online worker to claim them.
Executor directory.
Organization-scoped profiles, credentials, and availability.
Register a field executor
Trust Passport.
Specific claims, credential provenance, and execution history. No universal reputation score.
Choose an executor
Claims and credential records are contextual signals. Completion and evidence-quality metrics are historical aggregates, not guarantees of physical truth.
Evidence records.
Task-linked submissions and integrity metadata visible to this identity.
Metadata and file integrity do not independently establish what happened in the physical world.
Verification queue.
Evidence checks are policy-bound. Every final outcome records a reviewer decision.
Automation control.
Task events enqueue matching rules automatically. A separate worker runs the supported actions.
Define an execution rule
Notifications are stored in the organization's inbox. No email or payment is triggered.
Queue a matching run
Manual dispatch is organization-scoped. A running worker executes only the supported notification actions.
Recent workflow activity
Workflow run operations
Inspect worker outcomes and retry eligible failures with an auditable reason.
Activity.
A traceable stream of task, evidence, verification, and identity events.
Payments.
Financial state is separated from execution state. This pilot does not trigger charges or payouts.
Payments disabled
Task budgets are commercial terms only. No money moves through this pilot workspace.
Financial posture
Budget ledger
Transparent task terms without implying a completed settlement.
Plan & usage.
Organization-scoped task and API usage, with current plan limits and transparent billing status.
Upgrade plan
Checkout is enabled only when the payment provider and plan prices are configured.
Business verification
Submit organization details for review. Submitted details alone never grant verified status.
Available tiers
Displayed limits are entitlements. Paid checkout depends on configured provider credentials and prices.
Developer portal.
OpenAPI reference, organization keys, and a same-origin API explorer.
API reference
Developer keys
API explorer
Choose a route to inspect its response.
Workspace settings.
Local presentation preferences and identity session controls.
Console theme
Choose a display suited to your workspace or field conditions.
Not connected
Access tokens are held only in this page session and are not saved to browser storage.
My work.
Your assigned tasks will appear here.