DSH Plugin Registry
中文EN
Submit plugin
Plugins/dsh-observational-memory

dsh-observational-memory

Automated evidence available

Distills session work into background observations and reflections to preserve context across compaction.

Author: EPCN-fla · Memory · Catalog snapshot: 2026-09-19

What it may solve

Distills session work into background observations and reflections to preserve context across compaction.

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

EPCN-fla/dsh-observational-memory

— stars · — downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.

Not analyzed

Source structure

Source structure has not been analyzed.

Not analyzed

Repository health

Repository metadata has not been analyzed.

Not analyzed

npm release

npm release metadata has not been analyzed.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: The dependency audit did not produce a complete report.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis complete

Static risk scan

Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.

Analysis complete

Package integrity

Conclusion: Package structure or integrity validation did not pass.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-observational-memory. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.

Install or update the plugin manager (latest)