docs: add embed:regulations step to local setup#9
Open
franrob-projects wants to merge 2 commits into
Open
Conversation
Reads SLACK_BOT_TOKEN and SLACK_CHANNEL_ID from the environment. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The "Running locally" instructions jumped from migrations straight to the dev server, omitting the embedding step that populates pgvector. Without it the RAG pipeline returns no regulation context, so AI scenarios can't cite real law. Document the npm run embed:regulations step so a fresh clone works end-to-end. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Adds the missing
npm run embed:regulationsstep to the Running locally section of the README.Why
The setup instructions went straight from running Supabase migrations to starting the dev server, skipping the embedding step. Without it, pgvector is empty, so the RAG retrieval returns nothing and AI-generated scenarios can't cite real regulation — one of the project's headline features. This documents the step so a fresh clone works end-to-end.
Change
One small docs-only edit; no code changes.
🤖 Generated with Claude Code