Repository navigation
Build inference campaign control room and evidence organ - #2
Merged
Merged
Conversation
This was referenced Oct 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the organ destination for #1. Keep #1 open until the coordinated migration, refresh and deployment are shipped and verified.
This implements the PyAutoInsight inference campaign control room following Pulse's 2–3 October design: an editable all-inference check-in prompt, campaign table and canonical task ledger, followed by diagnostic/result/provenance coverage. It includes the inference-summary reader, explicit registry, resolved-commit receipts and last-good snapshots, CLI, reproducible dashboards, cockpit feed/badge, CI, refresh and Pages workflows. Integrity, freshness, execution and scientific qualification remain separate. Cortex owns scientific records/conclusions; projects retain drivers and samples; Mind retains bounded implementation lifecycle/claims.
Six preserved Mind prompts have destination files and migration hashes. Mind originals must remain until this destination has landed. Dashboard refresh is observation only: no compute submission, approval, scientific status transition or fabricated check-in.
Validation: 77 organ tests passed; lint, formatting and offline contract checks passed; all 6 migration hashes verified; Node editable-copy and clipboard fallback tests passed. Initial real evidence is explicitly captured from autolens_inference feature/insight-producer at 9c362a7a, a public feature-branch source awaiting merge. It is labelled as that branch. This PR does not assert main deployment, successful production refresh dispatch or live-dashboard verification yet.
Merge order: autolens_inference#18 producer first, then this Insight destination, then Mind source-removal migration. Complete post-merge refresh/receipt and live Pages verification before closing the overall task. Companion integration PRs are tracked under #1; Brain#460 establishes the shared theme/identity.
Human-authorized end-to-end implementation and normal review/merge/close-out workflow (/prm); preserve branch CI and shipping gates. Explicit Heart RED development override: "I authorize on red and repo made, continue". This is scoped to Insight#1 and does not waive scientific approvals or release gates. Exact overridden entry reasons: