Repository navigation
Address accuracy findings and make map claims reviewable - #15
Merged
Merged
Conversation
What this change does to the map
Changed, nothing to do (5)
Next to the change ChangeDetector holds most of what changed, and a flow joins it to 10 of the 16 cards, so naming them would say nothing. The committed map at |
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.
Source extraction and recorded map reviews could disagree with current code. This PR keeps unreadable source visible, makes historical comparisons use the requested inputs, and reopens reviews when their source or claims change.
Exploratory reports, captured datasets and the unfinished ownership-evaluation harness are excluded. The benchmark README retains measured results, failed acceptance bars and links to the original artifacts in Git history. Production code and its regression tests are unchanged by this cleanup.
Validation after cleanup:
The ownership pilot missed its preset false-challenge bar and does not justify a default policy change. Journey write recovery handles reported I/O failures; process termination and concurrent edits remain outside that contract.