NEXUS
Trust posture, contracts, and deployment controls
Back to learning & controls Open replay set
Settings

Show the trust posture behind every decision the product makes.

This screen explains the control surface behind the triage workflow: auth, signatures, replay readiness, contracts, and the operational posture that makes the product deployable.

Mode
Product
Auth
Enabled
Policies
Active
Integrations
Healthy
Signature
Active
Configuration
How to read this screen
Settings is the proof that the product is not just attractive. It has an explicit trust, audit, and deployment posture behind the experience.
Validation profile

Replay-safe defaults, seeded incidents, and deterministic metrics keep validation reliable.

Product mode

Authenticated APIs, webhook handling, audit logs, and integration posture point at a deployable surface.

Tenant Onboarding & Deployment Readiness

Before NEXUS can be used in this environment, the tenant must complete a bounded onboarding process.
Bootstrap Status
Overall
-
Owners
-
Repos
-
Delivery targets
-
Approval policy
-
Enabled packs
-
Supported Outage Families
  • Loading supported families...

These are the incident families your tenant can currently investigate and reproduce.

Required Setup Steps
  • Loading bootstrap requirements...

Contact your administrator to complete onboarding if this environment is not yet ready.

Operational Status

This product is meant to be deployed and governed, not only demoed.
Webhook auth
Configured
Rate limiting
Enabled
Audit logs
Enabled
Replay readiness
Ready
Replay launches
-
Training snapshots
-
Learning contracts
-
Artifact audit events
-
Guardian reviews
-

Runtime Host

This is the packaged-app truth layer for bounded replay: is a relay configured, is it reachable, and which outage packs can it actually execute.
Relay posture
State
-
Reachability
-
Pack coverage
-
Auth
-

Runtime host visibility will appear here once the platform payload loads.

Relay health details will appear here once the platform payload loads.

Relay endpoint

No runtime host relay configured.

  • No bounded pack catalog loaded yet.

Runtime Queue Recovery

Monitor the durable state of runtime replay jobs across app restarts and recovery boundaries.
Recovery Posture
Status
-
Active Jobs
-
Recovered
-
Failed
-
Total
-

Runtime queue recovery posture will appear here once the platform loads.

Deployment Readiness

Verify the deployment environment is ready for bounded replay and investigate degraded features.
Readiness posture
Overall
-
Docker
-
Runtime host
-
Pack root
-

Deployment readiness will appear here once the platform loads.

Degraded features
  • Feature degradation details will appear here once the platform loads.

Pilot Observability

Read the bounded pilot operating posture without checking server logs: what is healthy, what is partial, what is unavailable, and what the operator should inspect next.
Pilot-safe observability summary
Overall
-
Attention
-

Loading bounded pilot observability summary...

Subsystem posture
  • Loading subsystem posture...
What to check next
  • Loading service health status...

Services include replay execution, downstream delivery, runtime queue, and memory. Guidance is explicitly bounded and does not imply autonomous remediation.

Use Learning & Controls to generate the weekly review and pilot closeout packets from the current scorecard and artifact state.

Environment Controls

These controls define how the product behaves in validation, review, and production-like operation.
Deployment environment

Local product shell with deterministic data, ready for browser validation and demo review.

Replay readiness

Replay incidents, training payloads, and agent flows are preloaded into the same workflow surface.

Admin Controls

Bounded operator administration for pilot operations. Some controls require code changes.
Enabled packs

Curated runtime packs available for this tenant environment.

  • checkout-python-fastapi-auth-redis-v1 — INC001 timeout/retry (enabled)
  • checkout-python-fastapi-postgres-v1 — INC002 DB pool (enabled)
  • api-python-fastapi-catalog-v1 — INC003 deploy regression (enabled)
  • worker-backlog-kafka-v1 — INC005 queue backlog (enabled)
  • checkout-python-fastapi-auth-validation-v1 — INC007 auth dependency (enabled)

Packs are code-managed. Contact engineering to enable new packs.

Approval policies

Guardian approval requirements by incident severity.

  • P0 incidents → incident_manager approval
  • P1-P2 incidents → operator approval
  • P3-P4 incidents → operator review

Policies are system-configured. Updates require code change and redeployment.

Delivery destinations

Downstream targets where investigation packets can be sent.

  • GitHub — ✓ Active (configured but not yet connected)
  • Slack — ✓ Active (UI support ready)

Destinations are product-managed. New targets require backend implementation.

Backend Contract Surface

This is the contract surface the product grows from as reproduction, debugging, and deeper integration work come online.
Intake contracts
  • POST /webhooks/incident
  • POST /api/v1/incidents/manual-report
  • POST /api/v1/incidents/batch-import
Read / action contracts
  • GET /api/v1/incidents/{incident_id}/status
  • GET /api/v1/audit-logs/{incident_id}
  • POST /api/v1/incidents/{incident_id}/execute