Skip to main content
Audience: Engineering Teams, Technical Leads, DevOps Engineers, and AI System Architects.
Prerequisites: Git installed, PowerShell 7+ or Bash (Linux/macOS/WSL2), Python 3.11+ with uv.
Welcome to the Deep State of Mind (DSOM) Team Masterclass. This guide will walk you step-by-step through the exact lifecycle used by senior ICT consultants: from bootstrapping a brand-new repository, to pair programming with Google Antigravity, pushing to dual remotes (GitHub + GitLab), and collaborating asynchronously with autonomous agents like Google Jules.

🧭 The 4-Phase Team Operational Lifecycle


πŸš€ Step 0: Agent Onboarding Prompt (Genesis Synchronization)

Before issuing code instructions or starting a new agent session (Antigravity, Jules, Cursor, Claude), synchronize the AI agent with the DSOM framework directly from its authoritative online entry point:

πŸ“‹ Copy & Paste This Initialisation Prompt:


πŸ› οΈ Phase 1: Project Genesis & DSOM Adoption (The 6-Pillar Setup)

When starting a project (whether a Python backend, Node.js API, or Go microservice), you adopt DSOM as the project’s Cognitive Digital Twin.

Step 1.1: Create the Project Directory

Step 1.2: Adopt the Minimal 6-Pillar Footprint (Downstream Asymmetry)

In downstream projects, your business code remains primary (>90% of repo volume). You only need the lean 6-Pillar DSOM engine from the baseline repository:
  1. Spatial Memory (.agents/brain/):
    • task.md, Present task checklist.
    • walkthrough.md, Session history & Mental Anchors.
    • palace_registry.md, Documentation room index.
  2. Constitutional Engine (.agents/AGENTS.md):
    • Contains the 29 Constitutional AI Laws and Linguistic Persona.
  3. Universal Gateway Matrix (Root):
    • AGENTS.md (Root gateway for agents)
    • .cursorrules (Cursor IDE integration)
    • CLAUDE.md (Claude Desktop / Anthropic CLI)
    • .github/copilot-instructions.md (GitHub Copilot)
    • START-HERE.md (Human & AI onboarding roadmap)
  4. Pre-Commit Guardrails (tools/):
    • tools/install_git_guardrails.py & tools/guardrails-ai-dsom/
  5. Triple-Ledger:
    • README.md, CHANGELOG.md, HISTORY.md
  6. Isolated Python Tooling:
    • Powered by uv.

Method A: Prompting Google Antigravity (Automated AI Scaffolding)

If you have Antigravity open in the baseline DSOM workspace or in your new workspace, copy and paste this exact prompt:

Method B: Manual Copy via Terminal (PowerShell / Windows)

If copying manually from a local clone of deep-state-of-mind-for-my-ai on Windows:

Method C: Manual Copy via Terminal (Bash / Linux / macOS / WSL2)

If copying on Linux/macOS or via a temporary git clone:

🌐 Phase 2: Sovereign Dual-Remote GitOps (GitHub + GitLab)

DSOM enforces digital sovereignty through multi-cloud redundancy. We never rely on a single git provider.

Step 2.1: Initialise Git and Install Guardrails

Step 2.2: Stage & Create the Genesis Commit

Notice how the Git pre-commit hook automatically runs and validates your 10 sovereign guardrails before allowing the commit!

Step 2.3: Configure Dual Remotes

Step 2.4: Safe Non-Interactive Push

To prevent terminal hangs or Windows GUI authentication modals in automated workflows:

πŸ€– Phase 3: How to Pair-Program with Google Antigravity

Google Antigravity operates as your proactive Senior Systems Architect. When working with Antigravity:

Step 3.1: The Genesis Boot Handshake

When Antigravity opens your project, it executes the Mechanical Boot Sequence:
  1. Reads .agents/AGENTS.md (Constitutional laws & UK English/DBP Malay linguistic DNA).
  2. Reads .agents/brain/task.md & walkthrough.md (Restores exact active mental state).
  3. Reads START-HERE.md (Navigates the 4-quadrant DiΓ‘taxis compass).

Step 3.2: Planning Mode & The Implementation Plan

For non-trivial features, Antigravity uses Planning Mode:
  1. It researches local code and documentation first (Rule 20: Knowledge-First Discovery).
  2. It generates an implementation_plan.md artifact detailing proposed file diffs and verification tests.

Step 3.3: Model Selection & Token Budgeting Strategy

Select the appropriate AI model engine based on task complexity and token budget:
[!TIP] Token Efficiency Tip: Never feed 500,000 lines of raw code to the chat. Maintain lightweight OKF YAML frontmatter at the top of .md files so agents discover structure via ~50-token headers.

Step 3.4: Server Execution Invariant, Mandate Ansible Playbooks

[!CAUTION] Core Safety Law: Never allow an AI agent to run raw destructive terminal commands directly against servers!
  1. Express operations as Ansible Playbooks: Instruct the agent:
    β€œDo not run direct commands on the server. Write an idempotent Ansible playbook in playbooks/ to execute this configuration.”
  2. Key Advantages:
    • Idempotency: Safe to re-run without unintended side effects.
    • Auditability: Stored and tracked in Git for team peer review.
    • Testability: Can be dry-run safely using ansible-playbook -i hosts playbook.yml --check.

Step 3.5: Interactive Slash Commands to Teach and Guide

  • /learn, Invoke after any complex fix, correction, or release milestone. Antigravity will draft a learning proposal to update your project rules or skills permanently.
  • /schedule, Schedule background monitoring or recurring timers.
  • /goal, Run long-horizon, autonomous multi-step tasks without early stopping.

🀝 Phase 4: Multi-Agent Collaboration (Google Jules & Antigravity)

In modern DSOM workflows, different AI agents have different strengths:
  • Google Antigravity: Interactive pair programming, high-context refactoring, terminal execution, and architectural planning.
  • Google Jules: Autonomous cloud background execution, asynchronous PR creation, automated dependency upgrades, and deep issue resolution.

The Handover Lifecycle (Rule 25):

Key Practices for Multi-Agent Harmony:

  1. Worktree & Branch Isolation: Subagents and external agents work in discrete branches.
  2. Defensive Sync (Rule 7): Always run git stash && git pull --rebase && git stash pop before merging.
  3. The Episodic Resume Invariant (Rule 18): Every session ends with a [DSOM EPISODIC RECORD] block. Any incoming AI agent reads this block to pick up immediately where the last session left off with zero amnesia.

🏷️ Phase 5: Cutting Releases & Platform Deployment

When your team completes a sprint or feature milestone:
  1. Promote Changelog: Move [Unreleased] to ## [vX.Y.Z] - YYYY-MM-DD in CHANGELOG.md.
  2. Run Full Test Gate: Ensure 100% test pass rate via uv run pytest.
  3. Tag & Push: Create annotated Git tag vX.Y.Z and push to both remotes.
  4. Deploy GitHub & GitLab Releases:

πŸ“š Team Quick-Reference Cheat Sheet


Deep State of Mind (DSOM) For My AI Protocol | Harisfazillah Jamel (LinuxMalaysia) | 2026-08-22
Standard: UK English | DBP-standard Bahasa Melayu Malaysia (Piawai) | GNU General Public License v3.0