Repository navigation
feat: expose lensing catch-up freshness in cockpit - #110
Merged
Merged
Conversation
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.
Summary
The catch-up banner used activity from all research topics to recommend a lensing action, and the cockpit did not expose the banner's condition as an actionable row. Derive the banner and cockpit row from one lensing-specific freshness model using the existing seven-day policy and
/catch_up lensingprocedure.The model distinguishes actual bib-plus-sources ingestion from queue completion (which can mean read-without-filing). It includes cutoff, age, deadline, observation time and provenance. Healthy activity adds no attention row; missing, invalid, inconsistent and future evidence stays unknown. Actions remain manual, with scientific-judgement metadata and a runbook link.
Closes #109. Builds on PyAutoBrain#434 / PR #435; no Brain or website edits.
API Changes
lensing_ingest_evidencein board collection andlensing_catch_upinstate.json.last_ingestedanddays_since_ingest; new fields explicitly distinguishlast_ingestion,last_completedandlast_activity.Test Plan
make validate: citation metadata, repository structure and wikilinks passed.Heart gate
Live user authorization: “I authorize”, in direct response to “Ship Memory #109 despite Heart RED”. Commit, push and opening the pending-release PR only; no merge or release authorization.
Heart RED:
release validation FAILED (stage integrate)(snapshot 2026-10-01T10:10:03.098482+00:00).Other reasons:
workspace validation not passing (0 failed, 1 timeout, cloud#36404726969: autolens_test scripts/multi_dataset/rectangular.py);manifest drift: public front-door organ tables (generated) — 1 mismatch(es) vs PyAutoMind/repos.yaml.Passed gates: 254 Memory tests, make validate, shared feed validator for live/stale/unknown data, Chromium mobile/desktop light/dark, cockpit action/clipboard/runbook checks and in-session diff/visual review. No independent review claimed. Tested diff unchanged before shipping.