Intelligence · vault
Memory vaultApproved context agents are allowed to reuse.
What this is
Persistent context that gets injected into agent prompts. Each memory is operator-approved — no implicit retention.
What to do
Add memories you want every relevant mission to know. Pin the load-bearing ones. Review pending suggestions inferred from past runs.
What happens next
On every mission run, the selector picks the most relevant memories and the audit log records exactly which ones were used.
Hermes memory sync available
Local origin: 8 · Hermes-origin: 1
Active
9
Pinned
3
Local
8
Hermes-origin
1
Pending suggestions (3)
memory suggestionCREWpaper-tradingpaper-trade · sizing · preference↗ AAPL & NVDA — weekly paper trade thesis
[demo] User prefers max paper-trade risk below 1.5%
Paper Trading Desk should size simulated trades so max loss stays under 1.5% of book; reject anything looser.
Reason · Inferred from approved trade ticket — operator accepted a 1.4% sizing without changes.
[demo] User wants accessibility issues grouped by severity
Bug Hunter QA reports should group findings by severity (high → low), not by page. Apply on every audit.
Reason · Inferred from operator note on QA report approval.
[demo] Default refund follow-up window: 7 business days
Operator approved the +7d follow-up window twice in a row. Make it the default for all life-admin disputes.
Reason · Inferred from repeated approvals of the same follow-up plan.
New memory
9 memories
GLOBALHERMESHERMESpinnedlast used 15m ago
[demo] Operator timezone: Europe/London (UK)
Schedules and follow-ups should default to UK time unless the user specifies otherwise.
operatortimezone
hermes externalId · hm_op_tz_001
CREWUSERLOCALpinnedPaper Trading Desklast used 3h ago
[demo] Always state simulation only on paper trades
Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.
paper-tradesafety
CREWUSERLOCALpinnedLife Admin Crewlast used 4h ago
[demo] Prefer calm, firm tone for refund disputes
When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
drafttonepreferencecalm
CONTACTAGENTLOCALcreated 4h ago
[demo] Vendor 'Acme' takes 5–7 business days to respond
Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
vendorfollow-up
confidence 0.85
CREWAPPROVALLOCALPaper Trading Desklast used 3h ago
Approved paper-trade pattern
Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
paper-tradepatternapproved
confidence 0.85
CREWUSERLOCALBug Hunter Crewlast used 3h ago
[demo] Bug Hunter — concise bullets in reports
QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
reportconcisebriefbullets
CREWAGENTLOCALBug Hunter Crewlast used 3h ago
[demo] Use verbose, detailed bug reports
Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.
reportdetailedverbose
confidence 0.55
CREWAGENTLOCALPaper Trading Desklast used 3h ago
Approved paper-trade structure
Operator accepted a simulated trade with explicit invalidation, stop, target, and confidence. Keep this exact shape.
paper-tradestructure
confidence 0.85
CREWAGENTLOCALLife Admin Crewlast used 4h ago
[demo] Calm, firm refund email tone
When drafting refund disputes, use a calm but firm voice. Avoid ALL CAPS, exclamation marks, or threats. 7-day window before escalation.
drafttone
confidence 0.70