Skip to content

fix(coding-agents): keep knowledge pages current - #3483

Open
Sanderhoff-alt wants to merge 1 commit into
vectorize-io:mainfrom
Sanderhoff-alt:fix/knowledge-pages-current-state
Open

fix(coding-agents): keep knowledge pages current#3483
Sanderhoff-alt wants to merge 1 commit into
vectorize-io:mainfrom
Sanderhoff-alt:fix/knowledge-pages-current-state

Conversation

@Sanderhoff-alt

Copy link
Copy Markdown
Contributor

Summary

Knowledge pages can keep presenting facts that were true in the past but were later replaced, removed, or superseded. This is especially risky for coding agents because the pages are injected as current repository guidance.

This change addresses the issue by making coding-agent knowledge page refreshes explicitly use full mode and by adding a shared current-state policy to the page queries. The policy asks synthesis to prefer later evidence and label historical or superseded facts instead of presenting them as current.

Changes

  • Set mode: "full" for the five seeded knowledge pages and dynamically created initiative pages.
  • Apply the same current-state policy to all seeded page queries and initiative page queries.
  • Extend page seeding tests to verify the refresh mode and policy are sent to the API.

This is a focused mitigation. It does not introduce fact validity windows or a new supersession data model.

Verification

  • npm test in hindsight-integrations/coding-agents: 499 tests passed.
  • npm run build in hindsight-integrations/coding-agents: passed.
  • git diff --check: passed.

Fixes #3475

@Sanderhoff-alt
Sanderhoff-alt force-pushed the fix/knowledge-pages-current-state branch 3 times, most recently from 3abeba9 to d23129b Compare August 14, 2026 08:46
Knowledge pages can present historical facts as current guidance when later
evidence replaces, removes, or supersedes those facts.

Record full refresh mode explicitly for the five seeded knowledge pages and
dynamic initiative pages so their behavior does not rely on the API default.
Add a shared current-state policy to their source queries so synthesis
prefers later evidence, labels historical or superseded facts, and reports
uncertainty when the current state is unclear.

Expose one helper for applying that policy so seeded and dynamic page queries
use the same prompt construction. Reuse the shared page trigger for both
creation paths to prevent refresh configuration drift.

Extend page seeding tests to verify the full refresh mode and policy marker for
both page creation paths.

Tests: npm test
Build: npm run build
@Sanderhoff-alt
Sanderhoff-alt force-pushed the fix/knowledge-pages-current-state branch from d23129b to 8f18178 Compare August 14, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant