Repository navigation
Risk repository: Switch to tree hierarchy for classification - #59
Merged
Merged
Conversation
Concurrency now happens at the risk level rather than the document level. This makes it simpler to process pre-extracted risks from Airtable.
Instead of classifying risks extracted by the pipeline, it operates on risks stored in Airtable from the previous iteration of the risk repository.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rgambee
added a commit
that referenced
this pull request
Sep 23, 2026
This switches the classification stage from using the older (sub)category hierarchy to a more flexible tree hierarchy, which allows arbitrary levels of nesting. The evaluation helper is already using it. There's a conversion stage needed for the existing extraction stage (which is currently unused), as well as for the risks from the first iteration of the repository, which we use as ground truth for evaluating the classifier. There's also a new script for running the classifier by itself against the first iteration's risks for easier tuning.
This branch was successfully deployed
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.
This switches the classification stage from using the older (sub)category hierarchy to a more flexible tree hierarchy, which allows arbitrary levels of nesting. The evaluation helper is already using it.
There's a conversion stage needed for the existing extraction stage (which is currently unused), as well as for the risks from the first iteration of the repository, which we use as ground truth for evaluating the classifier.
There's also a new script for running the classifier by itself against the first iteration's risks for easier tuning.