Skip to content

chore: recycle unused frame-drift monitoring - #1544

Closed
serefyarar wants to merge 3 commits into
devfrom
cursor/recycle-frame-drift-monitoring-57e9
Closed

chore: recycle unused frame-drift monitoring#1544
serefyarar wants to merge 3 commits into
devfrom
cursor/recycle-frame-drift-monitoring-57e9

Conversation

@serefyarar

@serefyarar serefyarar commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Recycle the unused daily frame-drift observation pipeline (IND-430 / IND-468). It had no API, UI, or product consumer. The writer, tests, design doc, and four snapshot/ledger tables go away.

Why

  • Nothing in the product read frame_centroid_snapshots or cross_network_yield_snapshots.
  • The user_context centroid corpus was already dead after user_contexts dropped; the adapter measured only premise and intent embeddings.
  • Keeping a daily BullMQ scheduler and two adapters with no reader is maintenance for a question nobody is asking.

What changed

  • Delete FrameDriftQueue, FrameDriftMonitoringService, both adapters, config, and their tests.
  • Unwire startup/shutdown in main.ts; stop flushing the observation tables in db-flush.
  • Drop schema tables and unused bigint/check imports.
  • Remove the four deleted specs from services/api/.test-isolated.
  • Migration 0159_drop_frame_drift_monitoring drops:
    • frame_centroid_snapshots
    • cross_network_yield_snapshots
    • frame_drift_observation_runs
    • frame_drift_execution_attempts

Breaking: existing snapshot rows are capture-time measurements, not reconstructed history. They are deleted with the writer. No dual-read.

Restore

git checkout 061d0c51e -- \
  docs/design/frame-drift-monitoring.md \
  services/api/src/lib/frame-drift.config.ts \
  services/api/src/lib/tests/frame-drift.config.spec.ts \
  services/api/src/queues/frame-drift.queue.ts \
  services/api/src/queues/tests/frame-drift.queue.isolated.ts \
  services/api/src/queues/tests/frame-drift.hermetic.isolated.ts \
  services/api/src/services/frame-drift-monitoring.service.ts \
  services/api/src/services/tests/frame-drift-monitoring.service.spec.ts \
  services/api/src/adapters/frame-drift.database.adapter.ts \
  services/api/src/adapters/frame-drift-execution-attempt.database.adapter.ts \
  services/api/tests/frame-drift.database.adapter.isolated.ts \
  services/api/tests/frame-drift-execution-attempt.database.adapter.isolated.ts

Then restore the four tables from services/api/src/schemas/database.schema.ts at that SHA (create migrations 0093 / 0097 remain in history).

Recycle archive 404

indexnetwork/recycle/tree/main/frame-drift-monitoring is a 404 because cursor[bot] cannot write to that repo (git push and Contents API both 403). This PR does not link that path.

To publish the archive, grant Write to cursor[bot] on indexnetwork/recycle and ask this agent to push, or copy from 061d0c51e following the opportunity-discovery-dedup-merge/ layout.

Verification

  • bun run --cwd packages/protocol build && bun run --cwd services/api typecheck — pass
  • Isolated manifest loadIsolatedTestInventory — pass after dropping the four deleted files
  • Prior CI test / provider-free-security failed on that manifest; fix is on this revision
Open in Web Open in Cursor 

Drop the daily observation queue, service, adapters, and snapshot tables.
Nothing in the product read the measurements. Frozen copy is intended for
indexnetwork/recycle/frame-drift-monitoring; restore from 061d0c5 by path.

Co-authored-by: Seref Yarar <serefyarar@users.noreply.github.com>
@serefyarar
serefyarar marked this pull request as ready for review August 28, 2026 18:12
cursoragent and others added 2 commits August 28, 2026 19:21
cursor[bot] cannot write to indexnetwork/recycle, so that tree 404s.
Point restore at 061d0c5 until the archive is actually on recycle/main.

Co-authored-by: Seref Yarar <serefyarar@users.noreply.github.com>
The isolated-test inventory still listed the four deleted specs, so every
Bun preload failed before any suite could run.

Co-authored-by: Seref Yarar <serefyarar@users.noreply.github.com>
@serefyarar serefyarar closed this Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants