Repository navigation
Update log in Methodology + footer chip with the last data update - #15
Merged
Merged
Conversation
… data update - Footer: "Data updated 13 Oct 2026 · +8 new" — the later of the API build date and the newest log entry, and the documents added in the last 30 days. It opens the log. - About > Methodology: "Update log", a scrollable list, newest first, of every document added since 13 October 2026 (date, symbol linking to the reader, title, body) and every document reviewed and not added, with the reason. Read from docs/updates/log.json, which the pipeline writes with the feeds. - app.js / app.css ?v=20261013-log. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds a visible record of what was added to the database, and what was checked and left out, starting today.
docs/updates/log.json, written bybuild_feeds.pyin the pipeline after every corpus change. Additions come fromfirstAddedAt; rejections come from the hand-keptmysite_pythonanywhere/not_added.json.Tested
#documents/cerd-c-gc-40, and the not-added row shows its reason.🤖 Generated with Claude Code