القائمة
Memory fabric usage — ephemeral / episodic / semantic. Read this before reading from or writing to Hydra memory.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Per-workflow budget enforcement: tripwire at 80% (downgrade model tier), HITL at 100%. Telemetry pattern for cost-per-task tracking.
How to construct, validate, and route Hydra's typed cross-squad message envelopes. Use whenever an agent emits or consumes a CSuiteDecisionPacket, PRD, ArchRFC, DevTask, CreativeBrief, ShotList, AssetJob, HITLRequest, DecisionRecord, or Handoff.
When and how Hydra pauses for human input. Defines HITL gate placement, render format, resume contracts, expiry behavior, and override semantics.
How Hydra discovers, resolves, and routes to squad packs. Read this before adding/removing/modifying a squad.
| name | memory-handles |
| description | Memory fabric usage — ephemeral / episodic / semantic. Read this before reading from or writing to Hydra memory. |
Hydra never crosses a squad boundary with a raw blob. Agents receive MemoryRef handles (tier, key, summary) and resolve them through the hydra_memory MCP server (or hydra_core.memory.resolve directly).
| Tier | Storage | Lifetime | When to write |
|---|---|---|---|
ephemeral | in-prompt window | one turn | step-local scratch |
episodic | SQLite append-only at ~/.hydra/episodic.db | workflow lifetime + audit | every envelope, tool call, verdict, approval |
semantic | vector store (Chroma default) at ~/.hydra/vectors/ | persistent | long-term knowledge: code RAG, brand bibles, regulatory corpus |
from hydra_core.memory import append_episodic
ref = append_episodic(workflow_id, kind="prd", payload=prd.model_dump(mode="json"))
# returns MemoryRef(tier="episodic", key="ep:<wf>:prd:<ts>", summary="prd@<wf>")
from hydra_core.memory import resolve, list_episodic
content = resolve(ref)
all_for_wf = list_episodic(workflow_id)
Each squad's squad.yaml declares granted_memory_scopes implicitly via its accepts. Cross-squad reads MUST go through a HANDOFF envelope which carries granted_memory_scopes. The redaction layer (governance.redact_for_squad_boundary) strips PII at the boundary unless the squad is in the explicit allow-list (e.g. healthcare with PHI under its phi-redactor agent).
Conventional names by squad:
code_repos, runbooks, incident_historystrategy_docs, financials, market_intelbrand_guidelines, shot_library, prior_campaignsregulatory_corpus, contract_clausessnomed_ct, clinical_guidelinespaper_corpus, experiment_logs