bvandeusenandClaude Opus 5.5
79655fd19f
CI & Build / Python lint (push) Successful in 2s
CI & Build / Plugin hooks (push) Successful in 13s
CI & Build / TypeScript typecheck (push) Successful in 59s
CI & Build / integration (push) Successful in 1m32s
CI & Build / Python tests (push) Successful in 2m33s
CI & Build / Build & push image (push) Successful in 26s
Record, milestone, phase and plan citations go from every migration header; the "end before start" fix (0043) and the suppressed-count column (0095) state the condition they prevent rather than the incident. 0053 and 0055 pointed at design specs under docs/superpowers that are not in the repo; those pointers are removed. Kept: alembic's generated "Create Date:" headers (template metadata, not rationale), 0121's ARM_BORN justification beside the constant, and 0051's illustrative "update task 42" format example. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
58 lines
2.2 KiB
Python
58 lines
2.2 KiB
Python
"""rule_embeddings — rules become findable by meaning
|
|
|
|
Revision ID: 0089
|
|
Revises: 0088
|
|
Create Date: 2026-08-26
|
|
|
|
Rules were the only major record type with no vector, so `search` could never
|
|
return one and a rule could only ever arrive by being preloaded. That single
|
|
fact is what made every rule compete for the same always-on budget.
|
|
|
|
A sibling table rather than a generalisation of note_embeddings: the row could
|
|
have been made polymorphic, but the SEARCH could not — semantic_search_notes is
|
|
Note-specific scoping end to end, and a rule shares none of it. See the model
|
|
docstring for the full reasoning.
|
|
|
|
The vectors are DERIVED data. Nothing is backfilled here: the startup backfill
|
|
regenerates them, which is also how a chunker-version bump is handled.
|
|
"""
|
|
import sqlalchemy as sa
|
|
from alembic import op
|
|
|
|
revision = "0089"
|
|
down_revision = "0088"
|
|
branch_labels = None
|
|
depends_on = None
|
|
|
|
# Matches note_embeddings — bge-small-en-v1.5, 384-dim unit-normalized.
|
|
_EMBEDDING_DIM = 384
|
|
|
|
|
|
def upgrade() -> None:
|
|
op.create_table(
|
|
"rule_embeddings",
|
|
sa.Column("rule_id", sa.BigInteger(), sa.ForeignKey("rules.id", ondelete="CASCADE"), primary_key=True),
|
|
sa.Column("chunk_index", sa.Integer(), primary_key=True),
|
|
sa.Column("chunk_text", sa.Text(), nullable=False),
|
|
sa.Column("chunker_version", sa.Integer(), nullable=False),
|
|
sa.Column("updated_at", sa.DateTime(timezone=True), nullable=False, server_default=sa.text("now()")),
|
|
)
|
|
# The vector column is added by raw DDL for the same reason 0067 did it:
|
|
# the type comes from the pgvector extension, not from SQLAlchemy's
|
|
# type system.
|
|
op.execute(f"ALTER TABLE rule_embeddings ADD COLUMN embedding vector({_EMBEDDING_DIM}) NOT NULL")
|
|
# HNSW for cosine distance — matches Vector.cosine_distance (`<=>`), so the
|
|
# search is an indexed ORDER BY ... LIMIT k rather than a full scan.
|
|
op.execute(
|
|
"""
|
|
CREATE INDEX ix_rule_embeddings_embedding_hnsw
|
|
ON rule_embeddings
|
|
USING hnsw (embedding vector_cosine_ops)
|
|
"""
|
|
)
|
|
|
|
|
|
def downgrade() -> None:
|
|
op.execute("DROP INDEX IF EXISTS ix_rule_embeddings_embedding_hnsw")
|
|
op.drop_table("rule_embeddings")
|