memory-maintenance

Files (1)

• SKILL.md

SKILL.md (first lines)

# Memory maintenance

## Establish scope

Apply the current role, assignment, and authorized memory write scope.
This procedure grants no additional role or write authority.
Identify the selected memory store, its index, record format, and current writer before changes.
Preserve another owner's lease and use the host's supported memory mechanism.
Read Writing unless its complete content is already loaded.

## Read existing context

Read the selected store's index and records relevant to the proposed change before editing.
For whole-store reconciliation, review every record within that scope.
Follow cross-links needed to interpret the proposed change within authorized read access.
Do not infer facts from filenames or expand this review into unrelated transcripts, credentials, or private logs.
If required context is unavailable, report the missing source and defer the affected memory change.

Compare the proposed change with existing facts, preferences, dates, duplicates, conflicts, and superseding instructions.
Resolve precedence using current direct instructions and the contracts that own the facts.
Distinguish historical observations from current state and authority.
Preserve unresolved uncertainty rather than inventing a resolution.
Keep still-valid preferences and do not restore obsolete instructions merely because older records contain them.

## Reconcile and verify

Make the smallest authorized update after reviewing existing context.
Prefer focused records while following the user's requested grouping and the store's required format and metadata.
Keep facts in their owning records and synchronize concise index pointers and affected cross-links.
Remove or merge content only when evidence establishes duplication or supersession within the write scope.
Report necessary corrections outside that scope to their owner.
Exclude conversation-only history, source facts already maintained in Git, and private runtime identifiers from new records.
Keep private memory outside committed or published project material.

Read back changed records and the index to verify meaning, sentence boundaries, metadata, and links.
Confirm valid facts remain and superseded guidance no longer competes within the changed records.
Return changed paths, reconciliation coverage, unresolved conflicts, and memory write ownership without exposing private contents.

From ririnto/workgraph, MIT.

More from ririnto/workgraph