Ops board

Operator-facing intake and status, without pretending this shell runs the system.

This board mirrors the current operations truth already documented in the repo. It is a navigation surface for active threads, ownership, evidence, and restart pointers, not a live control plane and not a substitute for sovereign Nexus execution.

Healthy path

`prod_ops` is the current known healthy bounded verification path.

Open downstream issue

Issue #59 remains the main remote-owned thread after in-repo route and harness ambiguity were removed.

How to use this

Start with the thread cards below, then open the linked evidence or playbook docs before choosing the next bounded lane.

Active threads

Current bounded threads and their safest next move.

These cards mirror the current live evidence index. Status and ownership stay tied to repo-backed docs and artifacts, not inferred runtime assumptions.

prod_ops bounded checkout verification

Healthy

Current bounded verification is healthy again after the surface-specific checkout harness repair.

Ownership

In repo for harness/config, otherwise runtime-observed

Next safe bounded lane

No action required; keep under normal observation.

Issue #59 — prod_chaos AI Plan overclaim

Open and packaged for downstream action

Route and target correctness are confirmed. The remaining failure is still the visible AI Plan control paired with a 404 backend contract.

Ownership

Downstream-owned product/UI/backend issue

Next safe bounded lane

Wait for downstream owner change, then rerun bounded chaos verification.

local_ops availability

Blocked by missing local ops runtime

The bounded local target still points to localhost:8080, but no local ops runtime is currently answering the required ops endpoints there.

Ownership

In repo only if target config/tooling drifts; otherwise a local runtime prerequisite

Next safe bounded lane

Start the expected local ops runtime, then rerun bounded local ops verification.

local_chaos availability

Blocked by missing local chaos runtime

The bounded local target still points to localhost:8088, but no local chaos runtime is currently answering the required chaos endpoints there.

Ownership

In repo only if target config/tooling drifts; otherwise a local runtime prerequisite

Next safe bounded lane

Start the expected local chaos runtime, then rerun bounded local chaos verification.

Restart guidance

Use the canonical ops docs before opening the next lane.

The board is only a shortcut surface. The linked docs remain canonical for method, evidence, and restart-safe intake.

Live evidence index

Canonical operator jump point for current bounded evidence and thread status.

Repo-boundary playbook

Decision rules for when to fix in repo, hand off, or escalate.

Lane intake template pack

Reusable lane templates for review, fix, handoff, escalation, and evidence refresh work.

Local runtime prerequisites summary

Single operator reference for the current local ops and local chaos runtime requirements before reruns.

Re-verification entry points

Bounded reruns stay explicit.

If a downstream owner changes a remote surface or a local setup thread becomes active again, rerun the exact bounded commands below instead of widening scope.

node scripts/run-website-checkout.mjs --mode prod --surface ops --json
node scripts/run-website-checkout.mjs --mode prod --surface chaos --json
node scripts/run-website-checkout.mjs --mode local --surface ops --json
node scripts/run-website-checkout.mjs --mode local --surface chaos --json

Return to docs hub Return to shell