laqrumcode-forget

Estrellas11

Forks1

Actualizado24 de junio de 2026 a las 04:14

Selectively and REVERSIBLY forget stored memories/concepts (privacy / declutter) — soft-deactivate content matching a query or date so it stops surfacing in retrieval. Use when the user wants sensitive or unwanted data out of their laqrumcode graph.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

42U

42U/laqrumcode

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	laqrumcode-forget
description	Selectively and REVERSIBLY forget stored memories/concepts (privacy / declutter) — soft-deactivate content matching a query or date so it stops surfacing in retrieval. Use when the user wants sensitive or unwanted data out of their laqrumcode graph.

laqrumcode forget (reversible)

Soft-forget content so it stops surfacing in retrieval. Honors the D4 founder rule — nothing is deleted; matching rows are soft-deactivated with an audit annotation (archive_reason='forget:…') and can be fully reactivated.

Usage

node scripts/forget.mjs --query "api key"             # preview (DRY RUN)
node scripts/forget.mjs --query "api key" --commit    # apply
node scripts/forget.mjs --before 2026-01-01 --commit  # forget content older than a date
node scripts/forget.mjs --undo --commit               # reactivate everything forgotten by this tool

Behavior

DRY RUN by default — prints what would be forgotten (with samples); pass --commit to apply.
memory → status='archived'; concept → superseded_at set — both with archive_reason='forget:…'. The retrieval pipeline already excludes these, so they stop surfacing immediately, with no change to the hot retrieval path.
Reversible: --undo --commit reactivates everything this tool forgot.
Nothing is DELETEd — rows survive for forensic recovery (D4).

Scope (v1)

Selectors: --query (case-insensitive substring) and --before (ISO date).
Tables: memory + concept (the content tables whose retrieval candidate query already filters the deactivation flag).
Planned follow-ups: --project / --session (edge-scoped) and never-remember redaction at ingestion (privacy.json).
Env: SURREAL_URL/USER/PASS/NS/DB (same defaults as backup).

Más de este repositorio

mismo repositorio

audit-drift

42U/laqrumcode

Activate periodically (not per-session) to sample concepts from the graph and verify their claims against current state — code paths, recent sources, user-provided ground truth. Flag stale concepts for supersede-stale. Without this, knowledge rot poisons retrieval silently.

2026-06-2411

capture-insight

42U/laqrumcode

Activate when an insight worth keeping emerges mid-session — a surprising finding, a reusable pattern, a user correction, or a decision with rationale. Use this to write knowledge into the laqrumcode graph immediately rather than waiting for end-of-session daemon extraction (which is batch-only and can have hours of lag).

2026-06-2411

extract-knowledge

42U/laqrumcode

Activate when the user wants to distill lasting knowledge from ANY source — PDF, web article, pasted text, codebase file, transcript, markdown doc, or book chapter. Source-agnostic replacement for extract-pdf-gems. Same workflow core; source-type-aware quality rules.

2026-06-2411

extract-pdf-gems

42U/laqrumcode

Activate when the user asks to extract, mine, distill, or "pull gems" from a PDF, academic paper, book chapter, or research document into the laqrumcode memory graph. Also activate for phrases like "read this paper and remember it", "dense knowledge gems", "pull the insights", or when the user points at a PDF and asks to study it.

2026-06-2411

ground-on-memory

42U/laqrumcode

Activate when the user asks about state, history, prior work, codebase knowledge, or anything where injected memory should inform the response. Triggers include "what do you know about", "remember", "earlier", "last time", "we discussed", "in this codebase", "prior work", "previously", or any direct question about project/session state.

2026-06-2411

knowledge-gap-scan

42U/laqrumcode

Activate when the user wants to know what they DO and DON'T know about a topic, before starting research or a project. Turns the graph from a reference library into an active planning tool by reporting coverage and explicit gaps.

2026-06-2411

name	laqrumcode-forget
description	Selectively and REVERSIBLY forget stored memories/concepts (privacy / declutter) — soft-deactivate content matching a query or date so it stops surfacing in retrieval. Use when the user wants sensitive or unwanted data out of their laqrumcode graph.

laqrumcode forget (reversible)

Usage

node scripts/forget.mjs --query "api key"             # preview (DRY RUN)
node scripts/forget.mjs --query "api key" --commit    # apply
node scripts/forget.mjs --before 2026-01-01 --commit  # forget content older than a date
node scripts/forget.mjs --undo --commit               # reactivate everything forgotten by this tool

Behavior

DRY RUN by default — prints what would be forgotten (with samples); pass --commit to apply.
memory → status='archived'; concept → superseded_at set — both with archive_reason='forget:…'. The retrieval pipeline already excludes these, so they stop surfacing immediately, with no change to the hot retrieval path.
Reversible: --undo --commit reactivates everything this tool forgot.
Nothing is DELETEd — rows survive for forensic recovery (D4).

Scope (v1)

Selectors: --query (case-insensitive substring) and --before (ISO date).
Tables: memory + concept (the content tables whose retrieval candidate query already filters the deactivation flag).
Planned follow-ups: --project / --session (edge-scoped) and never-remember redaction at ingestion (privacy.json).
Env: SURREAL_URL/USER/PASS/NS/DB (same defaults as backup).