القائمة
Protect namespace-local identifiers when a shared queue schema only has one key column
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Resolve knowledge gaps: fetch unresolved gaps, assess sensitivity, generate research queries, ingest findings, and close gaps with a resolution slug.
Interrupt-driven alerts: detect and surface new contradictions, stale pages, resolved gaps, and embedding drift. Priority-classified with deduplication.
Ingest meeting notes, articles, documents, and conversations into Quaid. Handles idempotent ingestion for exact-byte duplicates and vault-backed sync.
Keep the brain healthy: detect and resolve contradictions via the correction / supersede workflow, validate referential integrity, triage knowledge gaps, find orphaned pages, and compact the database.
Answer questions from the brain using FTS5 + semantic search + structured queries. Synthesize across multiple pages. Cite sources.
Agent-guided binary upgrades: version check, channel detection, download via install.sh (or manual asset fetch + SHA-256 verify), and post-upgrade validation.
| name | namespace-qualified-queue-keys |
| description | Protect namespace-local identifiers when a shared queue schema only has one key column |
| domain | stateful storage, queueing, namespaces |
| confidence | medium |
| source | earned |
Use this when callers see identifiers as namespace-local (session_id, slug, etc.) but the backing queue or job table stores only a single key column. Without an internal qualification step, identical ids from different namespaces collapse onto the same pending row and silently corrupt queue semantics.
<namespace>::<id> right before enqueue/dequeue bookkeeping.