flake: rename the project to cocobee - #2
Merged
Merged
Conversation
The repository outgrew its name: it is no longer a place to try CocoIndex out, it is a Slack retrieval index with an eval harness and a measured pipeline. The flake description, the package name, the lock entry and the dev shell's virtualenv all follow the directory. The .envrc also stopped the formatter: shellcheck cannot see that direnv exports its own path into the file it evaluates, so SC2154 is silenced where it is raised, with the reason next to it.
Slack is the first source, not the only one planned, so the package takes the project's name and the module names carry the subject: cocobee.source scans a channel, cocobee.files reads what was shared in it. Directory layout stays flat until a second source exists — splitting now would mean guessing which parts are shared, and the second implementation is what answers that. Renaming the modules changes the logic fingerprints cocoindex derives from them, so the whole channel re-distilled and re-embedded on the next run; the scores are unaffected because neither the prompts nor the text changed.
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
1 participant
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.
The repository outgrew its name: it is no longer a place to try CocoIndex out, it is a Slack retrieval index with an eval harness and a measured pipeline. The flake description, the package name, the lock entry and the dev shell's virtualenv all follow the directory.
The .envrc also stopped the formatter: shellcheck cannot see that direnv exports its own path into the file it evaluates, so SC2154 is silenced where it is raised, with the reason next to it.
cocobee: rename the package after the project
Slack is the first source, not the only one planned, so the package takes the project's name and the module names carry the subject: cocobee.source scans a channel, cocobee.files reads what was shared in it. Directory layout stays flat until a second source exists — splitting now would mean guessing which parts are shared, and the second implementation is what answers that.
Renaming the modules changes the logic fingerprints cocoindex derives from them, so the whole channel re-distilled and re-embedded on the next run; the scores are unaffected because neither the prompts nor the text changed.