docs: synchronize human knowledge vector with cli, iac, and mcp matrix

Author: quantDIY

docs/DEVELOPER_GUIDE.md

@@ -26,3 +26,20 @@ GERP solves this with **Temporal Workflows**. The `pipeline` handles transaction
 
 ## 4. The GraphQL BFF (`cmd/gateway`)
 The Backend-For-Frontend receives a universal, deeply nested query from our UIs. When a client requests an `InventoryLot` and its associated `Warehouse`, the Gateway fetches the `scm.InventoryLot`, notices the `WarehouseID` pointer, mathematically fans out the query to the isolated `eam.Service`, and stitches the object graph back together dynamically using `gqlgen` resolvers.
+
+## 5. The CLI Control Plane (`cmd/gerp`)
+The `gerp` binary is the native operator terminal giving system administrators direct, low-latency control and query capabilities into the core Spanner domains and Temporal execution queues using `spf13/cobra` (routing) and `spf13/viper` (configuration).
+
+- **Config Bound:** The binary dynamically binds to `.gerp.yaml` in the user's home directory across different shell environments or relies on `GERP_` prefixed environment variables.
+- By bypassing the BFF using commands like `gerp audit view`, the CLI securely isolates direct native Spanner telemetry for compliance operations.
+
+## 6. Infrastructure & Deployment (`build/`, `deploy/`)
+GERP utilizes mathematically reproducible cloud infrastructure and secure container limits:
+- **Docker Packaging (`build/docker/`):** Both `cmd/gateway` and `cmd/worker` exist natively as multi-stage Alpine images optimized for scalable deployment pods.
+- **Terraform (`deploy/terraform/`):** GCP-specific HashiCorp constraints physicalizing the raw Cloud Spanner limits (`google_spanner_instance`, `google_spanner_database`) absent rigid DDL schema mappings.
+- **Ansible (`deploy/ansible/`):** Orchestrates the deployment configuration variables on the executing hardware targeting Docker container lifecycles.
+
+## 7. The AI Brain Interface (MCP)
+GERP exposes FAANG-grade capabilities autonomously to outside LLMs via standard JSON-RPC STDIO built off the Model Context Protocol.
+
+The `cmd/mcp` Server binds to AI agents running on Cursor IDE, Claude Desktop, or centralized orchestration engines via `.cursor/mcp.json`. Agents inherently use the physical tools (`gerp_status`, `gerp_create_order`, `gerp_audit_view`) to mechanically command the Spanner databases and trigger automated Temporal subroutines strictly adhering to the `internal/cli` environmental scope bindings.

docs/gerp.1.md

@@ -1,23 +1,37 @@
 GERP(1)                                    GERP Matrix Man Page                                    GERP(1)
 
 NAME
-       gerp - Google ERP Master Control Plane
+       gerp - Google ERP Master Control Plane & Native Operator CLI
 
 SYNOPSIS
        make [COMMAND]
+       gerp [COMMAND] [ARGS...]
 
 DESCRIPTION
        The GERP control plane utilizes Makefile targets to orchestrate a distributed, 7-domain ERP 
        matrix structurally bound by Temporal Sagas and isolated Spanner data layers.
+       
+       The compiled `gerp` native CLI allows system administrators and AI Autonomous Agents to
+       mechanically route direct queries against the Spanner telemetry or asynchronously fire
+       complex Temporal execution traces.
 
 ARCHITECTURE
        The physical runtimes consist of:
        - Cloud Spanner Emulator (Local instance binding all 7 domains natively).
        - Temporal Server (Local instance managing `GERP_GLOBAL_QUEUE`).
        - Go GraphQL Gateway (Port 8080: Binds the BFF execution).
        - Go Temporal Worker (Background: Listens for Saga dispatches).
+       - Go MCP Server (STDIO: Links external Model Context Protocol systems).
 
-COMMANDS
+CONFIGURATION
+       The `gerp` CLI relies natively on a `.gerp.yaml` configuration profile mapped to the 
+       user's local `$HOME` directory or explicitly bound via the following environment variables:
+       
+       GERP_GRAPHQL_ENDPOINT      Target API Gateway (Default: http://localhost:8080/query)
+       GERP_TEMPORAL_HOST         Temporal Control Queue (Default: localhost:7233)
+       GERP_SPANNER_DB            Sovereign Storage Domain Bounds
+
+MAKE COMMANDS
        make up
            Boot the local Docker infrastructure encompassing Spanner, Temporal, and associated matrix layers.
 
@@ -33,5 +47,15 @@ COMMANDS
        make generate
            Regenerate the physical Go bindings for the unified GraphQL API.
 
+GERP NATIVE COMMANDS
+       gerp status
+           Pings the GERP matrix execution limits and strictly formats the current operational bounds for the sysadmin.
+
+       gerp orders create
+           Triggers the Global Fulfillment Saga via GraphQL. Safely executing cross-domain mutations across SCM and Finance.
+
+       gerp audit view [target_record_id]
+           Bypasses the API Gateway to directly query Spanner ComplianceAudits locally. Deep inspection specifically formulated for Legal operations.
+
 SEE ALSO
        docker-compose(1), temporal(1), gcloud-spanner(1)