Recall

Portability (required)

1. Read the pstack capability contract and the active host adapter before delegation.
2. Obtain conversation history only through resources the host exposes for the current user and authorized scope. Never assume one transcript directory or schema.
3. Use parallel with read-only explore helpers for independent history slices and shared-record sources.
4. Resolve history mining through model_role:fast_explore and final synthesis through model_role:judgment.
5. When history or helper access is unavailable, use the visible conversation, repository state, and a stated evidence gap rather than inventing memory.

Purpose

Before work starts or resumes, rebuild the user's recent context and hand back a concise capsule of where things stand and what should happen next.

Recall combines two records:

• Personal working history. Goals, decisions, corrections, branches, pull requests, and unfinished threads from authorized prior conversations.
• Shared engineering record. Source control, tickets, documents, team discussion, incidents, errors, and current production or repository state. Use why to search this record.