Personal Context Management Audit — 2026-06-08¶

Inspected¶

~/hermes-vault/README.md
~/hermes-vault/Meta/Hermes Memory Architecture.md
~/hermes-vault/Meta/Hermes Vision.md
~/hermes-vault/Knowledge/LocalStack-First-30-Days-Context-Layer-Framework.md
~/hermes-vault/Knowledge/Parallel-Agent-Orchestration-Playbook — LocalStack Application: First 30 Days.md
~/hermes-vault/Knowledge/Agentic-Analytics-Engineering.md
~/context-portfolio/*.md
~/.hermes/memory/context_map.yaml
~/.hermes/memory/system/active_context.md
~/.hermes/memory/knowledge/news-briefing.md
~/projects/prefect-flows/flows/morning_news.py
~/projects/prefect-flows/tasks/classifier.py
~/projects/prefect-flows/tasks/deep_research.py
~/projects/prefect-flows/tasks/formatter.py
~/projects/prefect-flows/docs/plans/tech-news-briefing-rebuild.md

~/hermes-vault/ already acts as a synthesis layer with career-strategic Knowledge pages and wikilinks.
deep-dive-to-wiki already defines the right behaviour for promoting research into durable context.
Tech news already has collection, freshness filtering, dedup, theme clustering, editorial scoring, deep research, deferred research, and Slack delivery.
~/context-portfolio/ already provides portable personal context files and can become the base for agent-ready packs.
Existing LocalStack notes already frame onboarding as context acquisition, not passive learning.

~/context-portfolio/current-projects.md still references Tem preparation and older Bio Bridge details.
~/context-portfolio/tools-and-systems.md, preferences-and-constraints.md, current-projects.md, and ~/.hermes/memory/system/active_context.md still include Discord-era delivery/routing even though Slack is now primary.
~/context-portfolio/goals-and-priorities.md still says "PKM Orchestrator" and Tem career target rather than LocalStack and PCM.
~/context-portfolio/domain-knowledge.md references Hermes v0.10.0 and older Bio Bridge/Discord descriptions.
~/.hermes/memory/context_map.yaml has empty descriptions for all files and is dated 2026-04-20, reducing retrieval value.
~/.hermes/memory/knowledge/news-briefing.md still describes old cron/Discord architecture, not Prefect/Slack production.
~/hermes-vault/Meta/Hermes Vision.md still names "PKM Orchestrator" as the vision.

No explicit context inbox with a durable schema, status lifecycle, and processing rules.
No standard distinction between "raw dump", "needs extraction", "needs synthesis", "action", and "ignore/dedup".
No clear failure policy for unreadable URLs, blocked articles, PDFs, or missing transcripts.
No export/privacy labels at the intake stage.

Tech-news deep research enriches story cards but does not systematically store full extracted source text with hash/provenance.
No canonical raw source folder tied to vault/wiki promotion.
No source registry that maps raw captures to wiki/context pages they updated.

Context portfolio is general-purpose and stale; it does not yet expose compact work-ready packs.
Existing LocalStack vault notes are useful but too long for routine Claude context.
No explicit Claude instructions for how to use Adam's context, what to avoid exporting, and how to preserve confidentiality.

No context_fate field after classification/research.
No deterministic sink that writes raw sources or context-candidate records.
No integration point from high-signal stories to wiki promotion or context-pack refresh.
No tests asserting that high-signal items receive a valid post-briefing fate.

Treat [[Personal-Context-Management]] as the new operating architecture.
Process all new dumps through ~/.hermes/context-inbox/ with explicit metadata.
Add a context_fate stage to the tech-news flow in shadow mode first.
Refresh stale context-portfolio files, especially Slack/Discord, Tem/LocalStack, Bio Bridge, and PKM/PCM language.
Use ~/context-portfolio/packs/localstack/ as the first deployable context product.