spm-project-memory

Use SPM for durable requirements, decisions, completed work, temporal state, authority, source evidence, agent handoff, security, testing, deployment and governed sharing. Resolve the active project before consequential work. Do not read or compose another authorized project unless the user explicitly requests it.

Start or resume project memory with spm_agent_session_start when the runtime has not already done so. If SPM returns an association prompt, ask it naturally and persist the user's semantic confirm, replace or skip answer with spm_agent_session_association_decide. When the user explicitly asks to create new project memory, call spm_project_bootstrap_execute with that instruction, a safe inventory and source-grounded evidence from a bounded inspection. Repeat the same idempotent operation to resume it. If SPM requests a known evidence gap, submit only that authorized source with spm_project_bootstrap_evidence_submit and execute again. Continue without another question after created or already_completed. Use spm_project_bootstrap_preview and spm_project_bootstrap_confirm only for an explicit review-first request or when execution returns review_required.

Use SPM context packs rather than copying whole projects between conversations. Preserve source project, temporal assessment, context boundary and verification hash. Use spm_agent_session_context_inject and spm_agent_session_context_revoke only for explicit context composition. Use spm_cross_project_context_pack for one explicit source project and spm_multi_project_context_pack for several explicit sources, preserving source packs and hashes. Never claim a durable write succeeded unless the SPM tool confirms it. If SPM unavailable status is returned, say so plainly and continue without claiming persistence. Do not store secrets, raw credentials or unnecessary personal data.

Before a claim or action depends on prior project facts, call spm_memory_context_compose with the concrete semantic question. Treat the returned envelope as a bounded governed projection, not proof that undisplayed memory does not exist. SPM performs at most one automatic deep composition when its LLM declares the interactive projection insufficient and additional authorized evidence exists. If the final sufficiency contract still requests clarification, clarify instead of guessing from local conversational confidence.

When the user wants to continue the same authorized work in another agent or device, use spm_agent_session_continuation_create. The receiving agent accepts the one-time token with spm_agent_session_continuation_accept; revoke an unused handoff with spm_agent_session_continuation_revoke. Continuations carry only project and injected-context references. SPM rechecks current authorization and never transfers memory bodies or credentials.

Record a body-free workspace manifest with spm_agent_workspace_manifest_record before creating the continuation. For Git, report stable repository identity, revision and a hash/count summary of local changes; for non-Git work, report a filesystem, document or remote-resource version snapshot; use memory_only when no material resource is needed. The receiving agent includes its inspected manifest when accepting and follows SPM's alignment result. Never clone, pull, reset, overwrite or disclose raw diffs automatically. Use spm_agent_workspace_manifest_list for authorized session or project history.

Surface pending project attention at session start. Display is not acknowledgement or resolution; update attention state only after an explicit user instruction.

When an authorized file, specification, repository snapshot, tool result or endpoint response materially informs work but is not already represented in captured turns, call spm_agent_resource_handoff with its stable source reference, kind and a redacted body or accurate summary. Include mandatory source_identity with the governed repository/source scope and repository-relative logical path; keep the revision, machine and absolute local locator as observation provenance, never as logical identity. SPM does not inspect local files, hidden tool output or endpoints implicitly. Never hand off secrets or data outside the approved sharing boundary. Use spm_agent_resources_list when body-free source provenance is needed.