Live dashboard

Factory Status

This is the live dashboard behind Explore's Dark Factory claim: current maturity, AI usage, repo automation seams, release evidence, and recent factory activity.

Want the narrative version first? Read Dark Factory. Want the product story? Read About Explore.

Generated: 2026-04-29 23:19 UTC

Each block is labeled as Live runtime, Recorded evidence, or Interpretation so the proof surface reads as evidence instead of one blended status dump.

Factory Maturity

Interpretation

Closer to Level 5

Level 4.5: Autonomous delivery with a few true Level 5 gaps left

This factory now behaves like a disciplined Level 4 system with strong Level 5 traits: local-first CI, agent-owned PR and release flow, and recorded deploy plus smoke evidence.

4.5 / 5.0

  1. Level 1

    AI-assisted coding

    The repo already treats AI as a normal implementation tool rather than an occasional helper.

  2. Level 2

    Recorded agent pairing

    Prompts, run logs, acceptance criteria, and verification artifacts make each slice inspectable.

  3. Level 3

    Agent-owned implementation

    Agents own branch setup, implementation, local verification, and PR preparation.

  4. Level 4

    Agent-owned delivery

    The factory expects agents to carry work through CI, merge, release, deploy, smoke, and cleanup.

  5. Level 5

    Outcome-autonomous dark factory

    The remaining gap is outcome confidence: richer scenario proof and stronger trust that the system can ship routine work with minimal human governance.

What is already in place

  • Full local CI before PR creation The fast feedback loop now happens locally, so remote CI is mostly confirmation instead of first discovery.
  • Remote CI confirmation and same-PR fixes The factory watches GitHub checks, fixes failures in the same PR, and waits for a final green state.
  • Agent-owned release path Normal dark-factory work is documented as continuing through merge, deploy, smoke, and recorded evidence.
  • Visible execution artifacts Prompts, run logs, timing summaries, and AI usage reporting make the operating model legible.

What is still missing for Level 5

  • Scenario-first outcome validation Most proof still comes from repo tests and smoke checks instead of a richer scenario harness that validates end-to-end user outcomes.
  • Higher-confidence external-system simulation A true Level 5 setup usually has stronger test doubles or digital-twin style validation for risky dependency behavior.
  • Default trust in autonomous shipping The process is close, but it still needs more operational history before routine shipping feels completely black-box safe.

AI Economics

Recorded evidence

Live AI economics are intentionally not shown in this view.

The production app server does not store Codex session logs, so showing placeholder numbers here would overstate what the live dashboard actually knows.

Use governed PR slice evidence and recorded run logs when you want AI usage and cost details for a specific delivery slice.

Deploys & Smoke

Recorded evidence

Latest release evidence: 2026-04-27_2246-production-release.md (2026-04-27)

Smoke evidence: present in 2026-04-27_2243-release-smoke-fix-to-main.md

Runbook: docs/ops/smoke-check.md

Command: bin/host_factory smoke

Promotion Policy

Interpretation

The default governed lane is Governance in Single slice mode. It advances automatically through Ready for merge, then stops for the default human gate: merge_approval.

Governed software delivery and promotion through PR-based trust boundaries.

Default profile: auto_pr_manual_merge. Promotion horizon: Ready for merge. Active run horizon: Ready for merge.

Current stage: Request received. Stop point: wait_for_human_merge_approval. Next human action: Approve and merge the PR after required checks are green.

Governed Path

  • Request received: This is where a new request enters the factory.
  • Local green: This stage is inside the active automatic path for the selected lane and horizon.
  • PR created: This stage is inside the active automatic path for the selected lane and horizon.
  • Remote CI green: This stage is inside the active automatic path for the selected lane and horizon.
  • Ready for merge: This stage is inside the active automatic path for the selected lane and horizon.

Later production stages stay modeled after the default stop point instead of being implied: merged via auto_or_manual; deployed via command_or_manual; smoked via command_or_manual.

Repo Automation

Live runtime

Provider: github. Current mode: manual. Portability impact: optional layer.

Current runtime context: repo johnnybutler7/johnnybutler-com, current ref unavailable.

Credential requirement: not required for the current lane.

Supported auth sources: gh_cli

CI readiness source: host-test, factory-proof-test, lint, scan_js, scan_ruby

Current ci_status result: unavailable via unavailable. Readiness: unavailable.

No supported GitHub credential source is currently available for ci_status reads.

Current branch/ref PR view: unavailable via unavailable.

No supported GitHub credential source is currently available for PR association reads.

Merge-readiness view: unavailable via unavailable.

Merge readiness is unavailable because the underlying ci_status result could not be read live.

This proof is read-only and narrow. It can show current-ref PR association plus required-check-based merge readiness, but it does not infer approvals, branch protection, merge queue state, or merge policy.

Required checks summary: 0 passed, 0 pending, 0 failed, 0 missing, 0 manual, 5 unavailable.

  • host-test: unavailable via config
  • factory-proof-test: unavailable via config
  • lint: unavailable via config
  • scan_js: unavailable via config
  • scan_ruby: unavailable via config

Sections

Recorded evidence

Harness

Validation harness docs and checks.

1 markdown files

Latest: README.md

Updated: date unavailable

View details (coming soon)

Recorded evidence

Prompts

Recorded job prompts with scope and acceptance criteria.

966 markdown files

Latest: 2246-production-release.md

Updated: 2026-04-27

View details (coming soon)

Recorded evidence

Runs

Execution logs with verification outputs.

984 markdown files

Latest: 2026-04-27_2246-production-release.md

Updated: 2026-04-27

View details (coming soon)

Recorded evidence

Scenarios

Acceptance scenarios (holdout excluded from this page).

21 markdown files

Latest: 869-job-request-new-integration-option.md

Updated: date unavailable

View details (coming soon)

Recorded evidence

Recent Activity

  • prompts: 2246-production-release.md (2026-04-27)
  • runs: 2026-04-27_2246-production-release.md (2026-04-27)
  • prompts: 2244-mobile-home-hero-duplicate-trust-signals.md (2026-04-27)
  • runs: 2026-04-27_2244-mobile-home-hero-duplicate-trust-signals.md (2026-04-27)
  • prompts: 2243-release-smoke-fix-to-main.md (2026-04-27)