> ## Documentation Index
> Fetch the complete documentation index at: https://harisfazillah.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# 🏛️ The Hub-and-Spoke Collaboration Model

> OKF-compliant documentation for HUB-AND-SPOKE-MODEL.md. Deep State of Mind framework. Deep State of Mind framework. Deep State of Mind framework.

### 📜 docs/HUB-AND-SPOKE-MODEL.md (v2.0)

# 🏛️ The Hub-and-Spoke Collaboration Model

> **"Federated Intelligence. Centralised Strategy. Zero Conflict."**

## 1. Executive Overview

To enable multiple architects and developers to work within a single sovereign repository without triggering Git merge conflicts or "Context Leakage," the DSOM Protocol employs the **Hub-and-Spoke** model. The `global/` directory serves as the **Hub** (Strategic High-level Vision), while the `member/` directories serve as the **Spokes** (Tactical Individual Execution).

***

## 2. 🏛️ Detailed Brain Structure Display

The `.agents/brain/` directory is partitioned to ensure absolute isolation between technical roles and project management.

```text theme={null}
.agents/brain/
├── global/
│   └── task-master.md      <- THE HUB: Managed by Lead Architect (Haris).
│                           Summarises progress from all members.
│                           Defines the "Official" project status.
│
├── wings/                  <- THE PALACE: Sovereign Markdown Palace v1.0
│   ├── palace_registry.md  <- Master spatial index (AI reads this at SOD via Section [14])
│   ├── wing_[name]/        <- One Wing per domain (e.g., wing_elasticsearch/)
│   │   └── room_[name]/    <- One Room per component
│   │       └── closet.md   <- Structured knowledge: decisions, bugs, patterns
│   └── room_uncategorised/ <- Staging area for unplaced discoveries
│       └── closet.md
│
└── member/                 <- THE SPOKES: Individual sandboxes.
    ├── haris/              <- Senior Systems Architect (Sovereign Lead)
    │   ├── task.md         <- Haris's specific daily checklist.
    │   └── walkthrough.md  <- Haris's technical logs/decisions.
    ├── hisham/             <- Security & Tuning (Wazuh Specialist)
    │   ├── task.md         <- Wazuh focus & deployment tasks.
    │   └── walkthrough.md  <- Installation and tuning logs.
    ├── mawi/               <- Automation & Orchestration (Shuffle)
    │   ├── task.md         <- Workflow automation milestones.
    │   └── walkthrough.md  <- Logic logs for SOAR automation.
    ├── hidzuan/            <- Documentation & Compliance (URS/UAT)
    │   ├── task.md         <- Document draft status.
    │   └── walkthrough.md  <- Feedback and revision logs.
    └── hadi/               <- Project Coordinator (Client Interface)
        ├── client-logs.md  <- Meeting minutes & client feedback.
        ├── task.md         <- Milestone tracking & coordination.
        └── walkthrough.md  <- Communication strategies & status updates.

```

***

## 3. 🤝 The 3 Golden Rules (Workflow)

To ensure a smooth collaboration, all team members MUST adhere to these laws:

### Rule 1: Isolation (Conflict Prevention)

Members **only** edit files inside their own named folder (e.g., `member/hisham/*`). Because Git tracks changes by file path, multiple members can commit simultaneously without merge conflicts.

### Rule 2: The Daily Branch Ritual

Every member uses the `tools/git-ritual.sh` script to maintain **Atomic Git Hygiene**.

* **Start of Day (SOD):** Run `./tools/git-ritual.sh sod <username>`. This creates a semantic personal branch (e.g., `member/hisham-20260127`).
  * **Lead Architect (T2):** Also run `bash tools/sod-palace.sh  # (Windows: .\tools\sod-palace.ps1)` to pull, audit, and load the Palace Registry before starting.
* **Active Work:** Commit all technical progress and brain updates specifically to this branch.
* **End of Day (EOD):** Run `./tools/git-ritual.sh eod`. This merges the day's work into `main` and pushes it to the sovereign repository.
  * **Lead Architect (T2):** Also run `bash tools/eod-palace.sh  # (Windows: .\tools\eod-palace.ps1)` to validate, palace-sync, and commit Palace updates atomically.

### Rule 3: The Synchronisation (Lead Architect Role)

As the Lead Architect, Haris periodically audits the `member/*/walkthrough.md` files.

1. **Summarise:** Progress is pulled from Spokes into the `global/task-master.md`.
2. **Archive:** Major technical milestones are recorded in the `HISTORY.md` Ledger.
3. **Coordinate:** Use the `task-master.md` as the agenda for team sync meetings.
4. **Palace Sync:** Review the `palace_update_proposal_YYYY-MM-DD.md` generated by `eod-palace.yml` and update relevant closets in `wings/` to keep the spatial knowledge current.

***

## 4. 💻 Operational Commands

### Visualise the Full State

To see the expanded tree including all member brains:

```bash theme={null}
tree -a .agents/brain

```

### Discovery (Post-Absence)

If returning after time away, check for team updates before starting work:

```bash theme={null}
git pull origin main
ls .agents/brain/member/

```

*Action: Read the `walkthrough.md` of other members to catch up on logic changes.*

***

*Author: Harisfazillah Jamel | Lead Architect*
*Standard: UK English & DBP-Malay (Piawai)*
*Protocol Version: DSOM v6.1 + Palace v1.0*

***

### 🧠 Pedagogical Logic: Why this format?

1. **Separation of Concerns:** By including **Hadi** (Coordination) as a Spoke, we acknowledge that project management is as critical to the "Brain" as technical code. This follows the **ITIL 4 Service Value Chain**.
2. **Operational Sovereignty:** The 3 Golden Rules ensure that the project is not dependent on any one person's memory; the repository *is* the memory.
3. **LDP Compliance:** The clear structure and command examples follow the **Linux Documentation Project** standards for technical manuals.

***

***

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


## Related topics

- [🏥 DSOM ITIL 4 Alignment Strategy](/governance/itil-alignment.md)
- [📜 DSOM Master Directive: AI Governance Protocol (v6.1 + Palace v1.0)](/governance/ai-master-protocol.md)
- [🎓 DSOM Team Masterclass: Project Creation, GitOps & Multi-Agent Collaboration](/tutorials/team-dsom-masterclass.md)
- [🛡️ DSOM Guardrail Catalog & Guardrails AI Submission Review Document](/governance/dsom-guardrails-catalog-submission-review.md)
- [Tutorial: Getting Started with DSOM Tools](/tutorials/getting-started.md)