From 79655fd19f8361e2a56783fedafa86cdb78b9e58 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Wed, 21 Oct 2026 20:49:32 -0400 Subject: [PATCH] docs(6207): the remaining migrations state their rationale in terms of the data 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 --- .../versions/0043_event_duration_replaces_end_dt.py | 8 +++----- .../0044_add_note_description_and_consolidated_at.py | 2 +- .../versions/0048_conversation_last_curator_run.py | 2 +- .../versions/0049_conversation_curator_summary.py | 2 +- .../0053_drop_chat_journal_push_curator_tables.py | 8 +++----- alembic/versions/0054_drop_image_cache.py | 2 +- alembic/versions/0055_rulebook_tables.py | 4 ++-- alembic/versions/0066_milestone_body.py | 2 +- alembic/versions/0074_design_prose.py | 5 ++--- alembic/versions/0076_note_supersessions.py | 4 ++-- alembic/versions/0077_chunked_embeddings.py | 2 +- alembic/versions/0078_forge_connections.py | 4 ++-- alembic/versions/0080_code_shape_proposals.py | 2 +- .../versions/0081_shape_history_and_divergence.py | 2 +- alembic/versions/0083_code_shape_reason_code.py | 2 +- alembic/versions/0084_code_shape_uses.py | 2 +- alembic/versions/0085_project_inception.py | 2 +- alembic/versions/0086_code_shape_consumers.py | 2 +- alembic/versions/0089_rule_embeddings.py | 3 +-- .../versions/0095_retrieval_log_suppressed_count.py | 7 +++---- .../0096_retrieval_log_best_available_score.py | 4 ++-- .../versions/0097_retrieval_log_best_available_id.py | 2 +- alembic/versions/0098_rule_kind.py | 4 ++-- .../0099_scrub_secrets_from_retrieval_logs.py | 2 +- alembic/versions/0100_drop_always_on_tier.py | 4 ++-- alembic/versions/0102_milestone_embeddings.py | 6 +++--- alembic/versions/0103_retrieval_tuning_events.py | 12 ++++-------- .../0106_rule_usage_events_carry_an_outcome.py | 4 +--- alembic/versions/0107_system_embeddings.py | 5 ++--- .../versions/0109_embeddings_record_their_model.py | 2 +- alembic/versions/0110_task_claims.py | 2 +- alembic/versions/0113_system_path_patterns.py | 1 - alembic/versions/0114_system_usage_events.py | 2 +- alembic/versions/0115_retrieval_judgments.py | 1 - alembic/versions/0119_rule_moment_misfires.py | 2 +- alembic/versions/0122_seal_forge_tokens.py | 2 +- 36 files changed, 53 insertions(+), 69 deletions(-) diff --git a/alembic/versions/0043_event_duration_replaces_end_dt.py b/alembic/versions/0043_event_duration_replaces_end_dt.py index 3fac32ad..b84d7210 100644 --- a/alembic/versions/0043_event_duration_replaces_end_dt.py +++ b/alembic/versions/0043_event_duration_replaces_end_dt.py @@ -1,13 +1,11 @@ -"""replace events.end_dt with duration_minutes (Fable #160) +"""replace events.end_dt with duration_minutes Revision ID: 0043 Revises: 0042 Create Date: 2026-04-29 -Structural fix for the "end before start" bug class observed on prod -2026-04-29: an event landed with end_dt 32 days before start_dt due -to a tool-call mishap, then disappeared from upcoming-list filters. -Storing duration instead of end_dt makes the invalid state +Structural fix for the "end before start" bug class: an event whose end_dt +precedes its start_dt disappears from upcoming-list filters. Storing duration instead of end_dt makes the invalid state inexpressible at the schema level (duration_minutes >= 0). Backfill rules: diff --git a/alembic/versions/0044_add_note_description_and_consolidated_at.py b/alembic/versions/0044_add_note_description_and_consolidated_at.py index 2fe7957f..6f23942a 100644 --- a/alembic/versions/0044_add_note_description_and_consolidated_at.py +++ b/alembic/versions/0044_add_note_description_and_consolidated_at.py @@ -5,7 +5,7 @@ Revises: 0043 Create Date: 2026-05-13 Adds two columns to the ``notes`` table to support the task-as-durable-record -design (spec 2026-05-13): +design: - ``description``: user-stated goal / initial context. Meaningful when ``is_task=true``; left NULL on knowledge notes. diff --git a/alembic/versions/0048_conversation_last_curator_run.py b/alembic/versions/0048_conversation_last_curator_run.py index 302f57d0..1ee64ad2 100644 --- a/alembic/versions/0048_conversation_last_curator_run.py +++ b/alembic/versions/0048_conversation_last_curator_run.py @@ -4,7 +4,7 @@ Revision ID: 0048 Revises: 0047 Create Date: 2026-05-22 -Phase 2 of the conversation+curator architecture (Fable #172). The +Part of the conversation+curator architecture. The scheduler runs every 15 minutes and processes any journal conversation with messages newer than its `last_curator_run_at` timestamp. NULL means "never run; process all of today on first sweep." diff --git a/alembic/versions/0049_conversation_curator_summary.py b/alembic/versions/0049_conversation_curator_summary.py index 6e1cea00..4570e96d 100644 --- a/alembic/versions/0049_conversation_curator_summary.py +++ b/alembic/versions/0049_conversation_curator_summary.py @@ -4,7 +4,7 @@ Revision ID: 0049 Revises: 0048 Create Date: 2026-05-22 -Phase 3 of the conversation+curator architecture (Fable #172). The +Part of the conversation+curator architecture. The curator's final summary line (≤ 240 chars) is persisted here so the NEXT chat turn can include it in the system prompt. This is the feedback loop that closes the architecture — without it, the chat diff --git a/alembic/versions/0053_drop_chat_journal_push_curator_tables.py b/alembic/versions/0053_drop_chat_journal_push_curator_tables.py index e21823a4..2aee7f69 100644 --- a/alembic/versions/0053_drop_chat_journal_push_curator_tables.py +++ b/alembic/versions/0053_drop_chat_journal_push_curator_tables.py @@ -4,13 +4,11 @@ Revision ID: 0053 Revises: 0052 Create Date: 2026-05-27 -Phase 9 of the MCP-first pivot. The Python models for these tables were -deleted in Phase 8 (commit 91bafb6); this migration drops the orphan +Part of the MCP-first pivot. The Python models for these tables are gone; +this migration drops the orphan SQL tables and cleans up dead per-user setting rows. -Hard-cutover: existing rows in these tables are discarded. The -accompanying spec at docs/superpowers/specs/2026-05-26-mcp-first-pivot-design.md -explicitly accepted this loss. +Hard-cutover: existing rows in these tables are discarded, deliberately. """ from alembic import op diff --git a/alembic/versions/0054_drop_image_cache.py b/alembic/versions/0054_drop_image_cache.py index 187b4022..b9324ff8 100644 --- a/alembic/versions/0054_drop_image_cache.py +++ b/alembic/versions/0054_drop_image_cache.py @@ -4,7 +4,7 @@ Revision ID: 0054 Revises: 0053 Create Date: 2026-05-27 -The image cache was wired into the LLM image-search tool (removed in Phase 8). +The image cache was wired into the LLM image-search tool, which is gone. With no producer or consumer left, the table is dropped here. """ from alembic import op diff --git a/alembic/versions/0055_rulebook_tables.py b/alembic/versions/0055_rulebook_tables.py index 54f48467..68a499e5 100644 --- a/alembic/versions/0055_rulebook_tables.py +++ b/alembic/versions/0055_rulebook_tables.py @@ -6,8 +6,8 @@ Create Date: 2026-05-27 Adds the Scribe Rulebook hierarchy as a fourth top-level entity, sibling to Project. Rules carry a structural (statement, why, how_to_apply) -triple. Projects subscribe to Rulebooks (many-to-many). See the design -doc at docs/superpowers/specs/2026-05-27-scribe-rulebook-design.md. +triple. Projects subscribe to Rulebooks (many-to-many; migration 0101 +later drops subscriptions). """ from alembic import op import sqlalchemy as sa diff --git a/alembic/versions/0066_milestone_body.py b/alembic/versions/0066_milestone_body.py index 5f3fb0f1..9f78469a 100644 --- a/alembic/versions/0066_milestone_body.py +++ b/alembic/versions/0066_milestone_body.py @@ -4,7 +4,7 @@ Revision ID: 0066 Revises: 0065 Create Date: 2026-06-14 -T3 of plan #819. The milestone becomes the plan container: its `body` holds +The milestone becomes the plan container: its `body` holds the design/intent/purpose (markdown), `description` stays the one-liner, and individual steps live as first-class child tasks (milestone_id) instead of checkboxes crammed into a kind=plan task body. start_planning is reworked to diff --git a/alembic/versions/0074_design_prose.py b/alembic/versions/0074_design_prose.py index b48971ce..43e7246b 100644 --- a/alembic/versions/0074_design_prose.py +++ b/alembic/versions/0074_design_prose.py @@ -4,8 +4,7 @@ Revision ID: 0074 Revises: 0073 Create Date: 2026-07-31 -The operator's shape for #254: prose doesn't live as one-offs, it lives centrally -on the system. Two fields rather than one per category: +Prose doesn't live as one-offs; it lives centrally on the system. Two fields rather than one per category: design_systems.guidance the narrative a token table cannot hold — aesthetic, voice and tone, what is deliberately out of scope. @@ -17,7 +16,7 @@ on the system. Two fields rather than one per category: Free-form rather than a column per category on purpose. A schema with `voice`, `aesthetic` and `scope` columns would bake one rulebook's table of contents into -every install (rule #115), and the next install's design system would have three +every install, and the next install's design system would have three empty columns and nowhere to put what it actually cares about. Both nullable: a design system with no prose at all is complete, not a draft. diff --git a/alembic/versions/0076_note_supersessions.py b/alembic/versions/0076_note_supersessions.py index 8fd6b86b..8db1e483 100644 --- a/alembic/versions/0076_note_supersessions.py +++ b/alembic/versions/0076_note_supersessions.py @@ -4,7 +4,7 @@ Revision ID: 0076 Revises: 0075 Create Date: 2026-08-07 -Step 1 of milestone #278. Structure only — nothing reads or writes the new +Structure only — nothing reads or writes the new table yet, and nothing behaves differently after this runs. ## What the table is for @@ -39,7 +39,7 @@ and not for notes, so the column looked like the notes-side half of that feature, modelled and abandoned. It is dropped rather than repurposed for supersession, and the distinction is -the point (#2483): consolidation folds several records into one survivor and +the point: consolidation folds several records into one survivor and destroys the originals. Merging two snippets is lossless — one helper, several call sites. Folding two dev-logs means writing a summary and losing what each actually said. Supersession is the opposite act: both records survive, and the diff --git a/alembic/versions/0077_chunked_embeddings.py b/alembic/versions/0077_chunked_embeddings.py index f7a8bd84..9ac3277d 100644 --- a/alembic/versions/0077_chunked_embeddings.py +++ b/alembic/versions/0077_chunked_embeddings.py @@ -1,4 +1,4 @@ -"""Chunked embeddings: one note_embeddings row per chunk (#280) +"""Chunked embeddings: one note_embeddings row per chunk Revision ID: 0077 Revises: 0076 diff --git a/alembic/versions/0078_forge_connections.py b/alembic/versions/0078_forge_connections.py index da9b7808..f5ec0b18 100644 --- a/alembic/versions/0078_forge_connections.py +++ b/alembic/versions/0078_forge_connections.py @@ -1,4 +1,4 @@ -"""Forge connections move to the user level (#2778) +"""Forge connections move to the user level Revision ID: 0078 Revises: 0077 @@ -12,7 +12,7 @@ keyring, with an optional per-project pin (projects.forge_connection_id). The data move carries the existing admin config into a connection row for the first admin user (host parsed from the base URL), then deletes the old -setting keys outright — no legacy dual-read (rule #22). The env-var channel +setting keys outright — no legacy dual-read. The env-var channel (FORGE_KIND/FORGE_BASE_URL/FORGE_TOKEN) is untouched by this migration; it survives as an implicit keyring entry for admin users only. """ diff --git a/alembic/versions/0080_code_shape_proposals.py b/alembic/versions/0080_code_shape_proposals.py index 7a6e9320..e93c2ee9 100644 --- a/alembic/versions/0080_code_shape_proposals.py +++ b/alembic/versions/0080_code_shape_proposals.py @@ -1,4 +1,4 @@ -"""Shape fingerprints + the mechanical proposer's columns (#2792, milestone 294) +"""Shape fingerprints + the mechanical proposer's columns Revision ID: 0080 Revises: 0079 diff --git a/alembic/versions/0081_shape_history_and_divergence.py b/alembic/versions/0081_shape_history_and_divergence.py index 052f8836..429afc04 100644 --- a/alembic/versions/0081_shape_history_and_divergence.py +++ b/alembic/versions/0081_shape_history_and_divergence.py @@ -1,4 +1,4 @@ -"""Shape history, recheck, and the divergence flag (#2793, milestone 294) +"""Shape history, recheck, and the divergence flag Revision ID: 0081 Revises: 0080 diff --git a/alembic/versions/0083_code_shape_reason_code.py b/alembic/versions/0083_code_shape_reason_code.py index 6798ae70..19d62045 100644 --- a/alembic/versions/0083_code_shape_reason_code.py +++ b/alembic/versions/0083_code_shape_reason_code.py @@ -1,4 +1,4 @@ -"""Exempt/variant reason codes — a small fixed catalogue beside the prose (#2874, milestone 294) +"""Exempt/variant reason codes — a small fixed catalogue beside the prose Revision ID: 0083 Revises: 0082 diff --git a/alembic/versions/0084_code_shape_uses.py b/alembic/versions/0084_code_shape_uses.py index 652a7f13..d601f4cb 100644 --- a/alembic/versions/0084_code_shape_uses.py +++ b/alembic/versions/0084_code_shape_uses.py @@ -1,4 +1,4 @@ -"""code_shape_uses — consumption edges, separate from conformance (#2870, milestone 294) +"""code_shape_uses — consumption edges, separate from conformance Revision ID: 0084 Revises: 0083 diff --git a/alembic/versions/0085_project_inception.py b/alembic/versions/0085_project_inception.py index 40e776be..36a5f63c 100644 --- a/alembic/versions/0085_project_inception.py +++ b/alembic/versions/0085_project_inception.py @@ -1,4 +1,4 @@ -"""Project inception: the decision record + always-on rulebook exclusions (milestone 297) +"""Project inception: the decision record + always-on rulebook exclusions Revision ID: 0085 Revises: 0084 diff --git a/alembic/versions/0086_code_shape_consumers.py b/alembic/versions/0086_code_shape_consumers.py index d6c017d9..ac85a680 100644 --- a/alembic/versions/0086_code_shape_consumers.py +++ b/alembic/versions/0086_code_shape_consumers.py @@ -1,4 +1,4 @@ -"""code_shape_consumers — the CSS consumer map (milestone 302, note 2917) +"""code_shape_consumers — the CSS consumer map Revision ID: 0086 Revises: 0085 diff --git a/alembic/versions/0089_rule_embeddings.py b/alembic/versions/0089_rule_embeddings.py index 3537c820..8cabb3f0 100644 --- a/alembic/versions/0089_rule_embeddings.py +++ b/alembic/versions/0089_rule_embeddings.py @@ -1,5 +1,4 @@ -"""rule_embeddings — rules become findable by meaning (milestone 307 step 4, -decision note 3026) +"""rule_embeddings — rules become findable by meaning Revision ID: 0089 Revises: 0088 diff --git a/alembic/versions/0095_retrieval_log_suppressed_count.py b/alembic/versions/0095_retrieval_log_suppressed_count.py index 87fe5aac..d578d6d8 100644 --- a/alembic/versions/0095_retrieval_log_suppressed_count.py +++ b/alembic/versions/0095_retrieval_log_suppressed_count.py @@ -1,4 +1,4 @@ -"""add retrieval_logs.suppressed_count — tell a ranker decline from a repeat (#3497) +"""add retrieval_logs.suppressed_count — tell a ranker decline from a repeat Revision ID: 0095 Revises: 0094 @@ -20,9 +20,8 @@ the dropped rows never come back and there is nothing to count. NULLABLE, AND THE NULL IS THE POINT. A surface that does not measure suppression stores NULL, not 0, and the readout renders it as "not measured" rather than "none". Defaulting to 0 would make an unmeasured surface look like -a perfectly clean one — the exact substitution of an artifact for a -measurement that #3311 made and that #3497 exists to correct. Doing it again, -in the migration that fixes it, would be its own small joke. +a perfectly clean one — the substitution of an artifact for a measurement +that this column exists to prevent. No backfill for the same reason: existing rows genuinely do not know, and saying so is the honest state. `retrieval_logs` is not restored from backup, diff --git a/alembic/versions/0096_retrieval_log_best_available_score.py b/alembic/versions/0096_retrieval_log_best_available_score.py index 4772572b..9cacd01e 100644 --- a/alembic/versions/0096_retrieval_log_best_available_score.py +++ b/alembic/versions/0096_retrieval_log_best_available_score.py @@ -1,4 +1,4 @@ -"""add retrieval_logs.best_available_score — the score the bar rejected (#3670) +"""add retrieval_logs.best_available_score — the score the bar rejected Revision ID: 0096 Revises: 0095 @@ -34,7 +34,7 @@ NULLABLE, AND UNBACKFILLED, for the reason 0095 spells out: a row written before this shipped genuinely does not know what its best rejected candidate scored, and saying so is the honest state. A 0.0 default would read as "the corpus had nothing remotely relevant" — an artifact standing in for a -measurement, which is the whole defect this milestone corrects. +measurement, which is the defect this column corrects. `retrieval_logs` is not restored from backup, so no importer changes. diff --git a/alembic/versions/0097_retrieval_log_best_available_id.py b/alembic/versions/0097_retrieval_log_best_available_id.py index 6edc8c67..994f8426 100644 --- a/alembic/versions/0097_retrieval_log_best_available_id.py +++ b/alembic/versions/0097_retrieval_log_best_available_id.py @@ -1,4 +1,4 @@ -"""add retrieval_logs.best_available_id — WHICH record the bar refused (#3807) +"""add retrieval_logs.best_available_id — WHICH record the bar refused Revision ID: 0097 Revises: 0096 diff --git a/alembic/versions/0098_rule_kind.py b/alembic/versions/0098_rule_kind.py index 35bb0aaa..8902a5ce 100644 --- a/alembic/versions/0098_rule_kind.py +++ b/alembic/versions/0098_rule_kind.py @@ -1,4 +1,4 @@ -"""rules gain a `kind` — a preference is a rule that does not bind (#3849) +"""rules gain a `kind` — a preference is a rule that does not bind Revision ID: 0098 Revises: 0097 @@ -37,7 +37,7 @@ install upgrades and every existing row keeps the force it had. That is the same reasoning 0088 used for `tier`, and it is the reason both are safe to apply without reading the data first. -The CHECK is created with the column (rule 36: there is no prior constraint, +The CHECK is created with the column (there is no prior constraint, so the pair is created together — a value added to it LATER does DROP + ADD in one migration). diff --git a/alembic/versions/0099_scrub_secrets_from_retrieval_logs.py b/alembic/versions/0099_scrub_secrets_from_retrieval_logs.py index d2c5f9f0..d47ca01a 100644 --- a/alembic/versions/0099_scrub_secrets_from_retrieval_logs.py +++ b/alembic/versions/0099_scrub_secrets_from_retrieval_logs.py @@ -7,7 +7,7 @@ Create Date: 2026-09-11 `pre_tool_rule` retrieves against the RAW COMMAND TEXT and `write_path_rule` against the code being written, so whatever was on the command line or in the buffer is what `record_retrieval` wrote into `retrieval_logs.query`. A command -that exported a token stored the token (#3925). +that exported a token stored the token. `services/retrieval_telemetry.scrub_secrets` closes that going forward — the value never reaches the column. It cannot reach BACKWARDS, and this does: it diff --git a/alembic/versions/0100_drop_always_on_tier.py b/alembic/versions/0100_drop_always_on_tier.py index a5242815..f3246fd8 100644 --- a/alembic/versions/0100_drop_always_on_tier.py +++ b/alembic/versions/0100_drop_always_on_tier.py @@ -4,14 +4,14 @@ Revision ID: 0100 Revises: 0099 Create Date: 2026-09-11 -Milestone 394. Every rule now reaches a session by retrieval — because +Every rule reaches a session by retrieval — because something it is about to do made the rule relevant — and the machinery that delivered rules unconditionally goes with it. WHAT GOES, AND WHERE IT CAME FROM - ``rules.tier`` and its ``ck_rules_tier`` CHECK (migration 0088). Dropping - the column takes the constraint with it. Rule 36 is about ADDING a value to + the column takes the constraint with it. DROP + ADD is about ADDING a value to a live whitelist, which needs DROP + ADD in the same migration; it does not speak to removing the column outright, and saying so here is cheaper than the next reader wondering whether it was forgotten. diff --git a/alembic/versions/0102_milestone_embeddings.py b/alembic/versions/0102_milestone_embeddings.py index 61281aa7..df757182 100644 --- a/alembic/versions/0102_milestone_embeddings.py +++ b/alembic/versions/0102_milestone_embeddings.py @@ -1,4 +1,4 @@ -"""milestone_embeddings — a plan becomes findable by meaning (milestone 415) +"""milestone_embeddings — a plan becomes findable by meaning Revision ID: 0102 Revises: 0101 @@ -9,8 +9,8 @@ lives in — could not be found at all. So "is there already a plan for this?" had no tool, and a project whose roadmap was written as milestones had every later plan opened as a new milestone beside the one that already described it. -The sibling of rule_embeddings (0089), for the reasons its model docstring and -note 3163 give. The vectors are DERIVED: nothing is backfilled here, the startup +The sibling of rule_embeddings (0089), for the reasons its model docstring +gives. The vectors are DERIVED: nothing is backfilled here, the startup backfill writes them. """ import sqlalchemy as sa diff --git a/alembic/versions/0103_retrieval_tuning_events.py b/alembic/versions/0103_retrieval_tuning_events.py index 7dc69ac3..68ff1651 100644 --- a/alembic/versions/0103_retrieval_tuning_events.py +++ b/alembic/versions/0103_retrieval_tuning_events.py @@ -1,16 +1,12 @@ -"""retrieval_tuning_events — why a floor is where it is (#4102) +"""retrieval_tuning_events — why a floor is where it is Revision ID: 0103 Revises: 0102 Create Date: 2026-09-17 -Milestone 416 stops shipping similarity thresholds as values somebody has to -defend, and hands the adjustment to the model that reads the surface's own -telemetry. The operator's decision: - - "the floor should be chosen and adjusted by the model using it… the user - should be able to touch it but the model should be the thing handling it 9 - times out of 10." +Similarity thresholds are not values somebody has to defend: the model that +reads the surface's own telemetry adjusts them, and the operator can still +touch them. The number itself already has a home — the generic settings table. What has no home is the ARGUMENT, and once the values move on their own the argument is the diff --git a/alembic/versions/0106_rule_usage_events_carry_an_outcome.py b/alembic/versions/0106_rule_usage_events_carry_an_outcome.py index b5853496..e02ee635 100644 --- a/alembic/versions/0106_rule_usage_events_carry_an_outcome.py +++ b/alembic/versions/0106_rule_usage_events_carry_an_outcome.py @@ -12,9 +12,7 @@ sessions leave identical telemetry: - a rule surfaced, opened, and silently ignored. The second is the more urgent by a distance, and it is the one the readout -cannot name. That is the whole of what this milestone is about, measured on a -session where three of seven misses were caught by the operator and none by -the system. +cannot name, and it is what an outcome column is for. TWO NEW EVENT VALUES, AND NO CHECK MIGRATION. `event` was created in 0094 as plain `sa.Text()` with no constraint — checked in the migration itself, not diff --git a/alembic/versions/0107_system_embeddings.py b/alembic/versions/0107_system_embeddings.py index e98251c1..70211dfe 100644 --- a/alembic/versions/0107_system_embeddings.py +++ b/alembic/versions/0107_system_embeddings.py @@ -1,4 +1,4 @@ -"""system_embeddings — a charter becomes an ANSWER, not just a filter (#4251) +"""system_embeddings — a charter becomes an ANSWER, not just a filter Revision ID: 0107 Revises: 0106 @@ -13,8 +13,7 @@ to one, and an agent asking where a record belonged had to read every charter or guess. The fourth sibling of note_embeddings (0067), rule_embeddings (0089) and -milestone_embeddings (0102), and for the same reason note 3163 gives about the -third: the row could be shared, the search cannot. "Where does this belong?" +milestone_embeddings (0102), and for the same reason as the third: the row could be shared, the search cannot. "Where does this belong?" is a different question from "what prior art is there?", and no note or rule search can answer it, because a charter is not a note. diff --git a/alembic/versions/0109_embeddings_record_their_model.py b/alembic/versions/0109_embeddings_record_their_model.py index 334b2986..b8ccbe95 100644 --- a/alembic/versions/0109_embeddings_record_their_model.py +++ b/alembic/versions/0109_embeddings_record_their_model.py @@ -1,4 +1,4 @@ -"""embeddings_record_their_model — a vector says whose space it lives in (#4132) +"""embeddings_record_their_model — a vector says whose space it lives in Revision ID: 0109 Revises: 0108 diff --git a/alembic/versions/0110_task_claims.py b/alembic/versions/0110_task_claims.py index 3b95078c..b1f0d533 100644 --- a/alembic/versions/0110_task_claims.py +++ b/alembic/versions/0110_task_claims.py @@ -1,4 +1,4 @@ -"""task_claims — a task can say a session is working it (milestone 381 step 2) +"""task_claims — a task can say a session is working it Revision ID: 0110 Revises: 0109 diff --git a/alembic/versions/0113_system_path_patterns.py b/alembic/versions/0113_system_path_patterns.py index e63e3c90..c51f53c8 100644 --- a/alembic/versions/0113_system_path_patterns.py +++ b/alembic/versions/0113_system_path_patterns.py @@ -1,5 +1,4 @@ """system_path_patterns — a System names the files that are its area -(milestone 444 step 3, #4756) Revision ID: 0113 Revises: 0112 diff --git a/alembic/versions/0114_system_usage_events.py b/alembic/versions/0114_system_usage_events.py index 86734a83..79c190cf 100644 --- a/alembic/versions/0114_system_usage_events.py +++ b/alembic/versions/0114_system_usage_events.py @@ -1,5 +1,5 @@ """system_usage_events — were an area's rulings read once its files were -touched? (milestone 444 step 4, #4757) +touched? Revision ID: 0114 Revises: 0113 diff --git a/alembic/versions/0115_retrieval_judgments.py b/alembic/versions/0115_retrieval_judgments.py index 6ed638bd..d48a5f7f 100644 --- a/alembic/versions/0115_retrieval_judgments.py +++ b/alembic/versions/0115_retrieval_judgments.py @@ -1,5 +1,4 @@ """retrieval_judgments — a reviewer's verdict on each line of a logged menu -(#4772) Revision ID: 0115 Revises: 0114 diff --git a/alembic/versions/0119_rule_moment_misfires.py b/alembic/versions/0119_rule_moment_misfires.py index 655a4f74..16f50e37 100644 --- a/alembic/versions/0119_rule_moment_misfires.py +++ b/alembic/versions/0119_rule_moment_misfires.py @@ -1,5 +1,5 @@ """rule_moment_judgments.misfire — a mount reported as arriving where it does -not apply (milestone 458 step 7b, #4955) +not apply Revision ID: 0119 Revises: 0118 diff --git a/alembic/versions/0122_seal_forge_tokens.py b/alembic/versions/0122_seal_forge_tokens.py index 067f41e1..86c8bacd 100644 --- a/alembic/versions/0122_seal_forge_tokens.py +++ b/alembic/versions/0122_seal_forge_tokens.py @@ -1,4 +1,4 @@ -"""Seal forge-connection tokens at rest (milestone 523) +"""Seal forge-connection tokens at rest Revision ID: 0122 Revises: 0121