Status Chat Procedure Manual (Beta)

 

Status Chat MKMS: Project Work Cycle Procedure Manual

Welcome to the operational blueprint for the Modular Knowledge Management System (MKMS). This manual outlines the standard operating procedure (SOP) for taking a project from its initial inception to full-scale automation using NoteBookLMs (data repositories) and Custom Department GEMs (specialized AI personas).

By following this cycle, we ensure that data flows seamlessly from raw client inputs into structured, actionable team intelligence.

## 1. Phase 1: Foundation & Data Ingestion (The Notebook Phase)

The objective of this phase is to isolate and centralize knowledge sources before any AI synthesis begins. We use individual NoteBookLMs to prevent "data bleeding" between stakeholders.

### Step 1.1: Initialize the Project NoteBookLM

• Action: Create a centralized repository named [Project Name] - Core Notebook.

• Content: Project charters, scope of work (SOW), timelines, budget sheets, and overarching project goals.

• Purpose: Serves as the single source of truth (SSOT) for the project’s objective constraints.

### Step 1.2: Initialize the Client NoteBookLM

• Action: Create a distinct repository named [Client Name] - Client Intel.

• Content: Client brand guidelines, feedback logs, historical communications, meeting transcripts, and specific preferences.

• Purpose: Ensures the AI understands the client's unique voice, expectations, and historical context without mixing it up with internal vendor data.

### Step 1.3: Initialize the Vendor/Partner NoteBookLM

• Action: Create a repository named [Project Name] - Vendor Operations.

• Content: Vendor contracts, service level agreements (SLAs), technical documentation, and external API specs.

• Purpose: Keeps third-party constraints, capabilities, and technical requirements organized for easy cross-referencing.

## 2. Phase 2: Synthesis & Context Engineering

Once the data is structured into notebooks, the project manager bridges these repositories to create a unified context.

[Client Notebook]   ──┐
[Vendor Notebook]   ──┼─> [Synthesized Master Context] ─> [Custom Department GEMs]
[Core Project NB]   ──┘

### Step 2.1: The Triangulation Prompt

Run a baseline synthesis query across all three notebooks to identify alignment and conflicts.

Protocol Prompt: > "Cross-reference the Project SOW with the Client Guidelines and Vendor SLAs. Identify any immediate scheduling conflicts, technical bottlenecks, or scope mismatches. Highlight these as priority 'Risk Factors'."

### Step 2.2: Extracting the "Golden Guidelines"

From the synthesis, extract a Master Project Context Document. This text file will act as the foundational instructions for your downstream Status Chat GEMs.

## 3. Phase 3: Deployment of Custom Department GEMs

With the knowledge base established, you will now deploy specialized, role-based GEMs within Status Chat. Instead of asking one AI to do everything, you deploy a hyper-focused team.

Department GEM	Primary Source Ingestion	Core Responsibility
Account/Client GEM	Client Intel NB + Core Project NB	Drafts client-facing updates, handles revision requests, ensures brand alignment.
Dev/Ops Technical GEM	Vendor Ops NB + Core Project NB	Translates client requests into technical tasks, checks vendor documentation, flags blockers.
Creative/Strategy GEM	Client Intel NB	Generates concept ideation, copywriting, and design briefs adhering strictly to brand guidelines.
PM Status GEM	All Notebooks (Aggregated)	Tracks milestones, generates daily standup summaries, updates the Status Chat channel on velocity.

### Step 3.1: Configuring the GEM System Instructions

When building each custom GEM in Status Chat, use the following structural template for their system prompts:

Plaintext

[ROLE]: You are the [Insert Department] AI Expert for [Project Name].
[CONTEXT]: Your core knowledge is derived from the Master Project Context and the [Specific] Notebook.
[GUARDRAIL]: Never hallucinate technical specs. If a vendor limitation or client preference is unknown, explicitly state: "Data not present in current Notebooks."
[TONE]: Professional, proactive, and tailored to [Internal Team / External Client] communication styles.

## 4. Phase 4: Active Work Cycle & Optimization

The MKMS is not static; it evolves as the project progresses.

       ┌──────────────────────────────┐
       ▼                              │
[Active Work] ──> [New Data Generated] ──> [Update Notebooks]

• Weekly Delta Updates: Every Friday, upload new meeting transcripts, approved change orders, and Slack summary logs back into the respective NoteBookLMs.

• GEM Recalibration: If a major pivot occurs, update the Master Project Context Document and paste it into the system instructions of the affected Department GEMs.

• The Status Loop: Use the PM Status GEM to query the other GEMs at the end of each sprint cycle to generate an automated "Project Health Report" for stakeholders.

## 5. Phase 5: Project Offboarding & Archiving

• Step 5.1: Merge all NoteBookLMs into a final [Project Name] - ARCHIVED COMPLETED notebook.

• Step 5.2: Deprecate the specific Department GEMs to free up system bandwidth, saving their System Instruction prompts into the archive notebook for future template cloning.

• Step 5.3: Run a final "Lessons Learned" prompt through the archived notebook to extract operational insights for the next project cycle.