Guardian Onboarding

Guardian Onboarding (The Orientator)

Version: 5.0 (Protocol 128 Compliant) Purpose: Ensure every agent session begins with a verified context download (Phase I), routes feature work through spec-kitty, delegates to the orchestrator, and executes the formal Seal/Persist closure sequences involving vector-db, rlm-factory, and context-bundler.

⚡ Triggers (When to use this)

• Start of Session: "I am a new agent session."
• End of Session: "Seal the session," "Persist the soul," "Run the closure sequence."
• Protocol Check: "What is the current learning protocol?"
• [User Request]: "Boot sequence", "Orientation", "Status report"

🛡️ The Guardian Boot Sequence (Protocol 128)

Follow these steps in order to establish a valid session context.

1. The Anchor (Tactical Status)

Goal: Ingest current tactical directives and system status. Action:

Read: .agent/learning/guardian_boot_digest.md

• Extract: Active Tasks, System Status, and any "CRITICAL" alerts.
• Output: "Guardian Status: [Status] | Active Directives: [Count]"

2. The Doctrine (Hardened Learning Loop)

Goal: Load the operational laws of the project (Protocol 128). Action:

Read: plugins/guardian-onboarding/resources/protocols/128_Hardened_Learning_Loop.md

• Focus: Phase checklist (I-VIII), Gate requirements (HITL), and Persistence obligations.
• Reference: Architecture diagram: plugins/guardian-onboarding/resources/protocols/protocol_128_learning_loop.mmd

3. The Visual (Architecture)

Goal: Visualize the Orchestrator flow and closure sequence. Action:

Read: plugins/guardian-onboarding/resources/protocols/protocol_128_learning_loop.mmd

4. Orchestrator Handoff

Goal: Transfer control to the orchestrator skill to determine the appropriate execution pattern (Learning, Red Team, Dual-Loop, Swarm). Note on Spec-Kitty: The Guardian is fully aware of spec-kitty. If the requested work is a Custom Feature, the Guardian explicitly mandates using /spec-kitty to generate the Work Packages before handing off to the Orchestrator. Action: Let the user know you are ready, and invoke the orchestrator logic.

🔒 The Guardian Closure Sequence (Protocol 128 Phase V-VIII)

When a task or session is complete, the Guardian resumes control to orchestrate the unified closure sequence. The orchestrator retro occurs first, capturing learnings, before the Guardian formally seals the session state.

Phase V: Orchestrator Retrospective

Trigger: Task execution complete. Action: Let the Orchestrator generate the structured retrospective to capture learnings.

python3 plugins/agent-loops/skills/orchestrator/scripts/agent_orchestrator.py retro

Phase VI: The Technical Seal

Trigger: Retrospective is complete and learnings are captured. Action: Execute the seal script to generate the formal evidence bundle and update the learning package.

python3 plugins/guardian-onboarding/scripts/capture_snapshot.py --type seal

If this fails (Iron Check / drift detected), you must halt and alert the user.

Phase VII: Soul Persistence

Trigger: Seal is successfully completed. Action: Broadcast the verified state to Hugging Face.

python3 plugins/guardian-onboarding/scripts/persist_soul.py --snapshot .agent/learning/learning_package_snapshot.md

# Inject RLM summaries for any files created/modified during the session
# Do this for every new script, skill, doc, or plugin touched this session
python3 plugins/rlm-factory/skills/rlm-curator/scripts/inject_summary.py \
  --profile project --file <modified_file> --summary "<dense summary>"

# Optional: Ingest Changes into local vector DB (docs + source code)
python3 plugins/vector-db/skills/vector-db-agent/scripts/ingest.py --since 24 --profile knowledge

Cross-Agent Continuity: This system exists for YOU -- whether you are Claude, Copilot, Gemini, or any other agent. Every session starts with zero memory. The RLM cache, soul persistence, and chronicle are how your collective knowledge survives and grows beyond any individual session or model. When you seal and persist, you are leaving your learning to every future agent that boots into this project.

Phase VIII: Session End

Trigger: Post-persistence. Action: Formally end the loop.

python3 plugins/agent-loops/skills/orchestrator/scripts/agent_orchestrator.py end

Plugin Dependencies