@karthikrajkumar.kannan/get-things-done 1.0.3 → 1.0.4

package/README.md

@@ -36,6 +36,7 @@ npx @karthikrajkumar.kannan/get-things-done@latest
 - [What Makes GTD Different](#what-makes-gtd-different)
 - [Installation](#installation)
 - [MCP Server -- Use GTD as Tools from Any Language](#mcp-server----use-gtd-as-tools-from-any-language)
+- [Cloud-hosted code and local access](#cloud-hosted-code-and-local-access)
 - [SDK for CI/CD](#sdk-for-cicd)
 - [Architecture](#architecture)
 - [Document Formats](#document-formats)
@@ -582,6 +583,60 @@ You should see two JSON responses: server info + list of 19 tools.
 
 ---
 
+## Cloud-hosted code and local access
+
+GTD runs against a **project directory on the machine** where you use slash commands, the MCP server (`--project`), or the SDK. If the source of truth lives in the cloud, use one of these patterns to get (and keep) that tree locally.
+
+### 1. Git
+
+Code lives in **GitHub, GitLab, Azure DevOps, Bitbucket**, or another Git host. Locally: `git clone`, then `git pull` / `git fetch` for updates; use branches and remotes as usual.
+
+**When to use:** Default for ongoing development when the repo is the artifact.
+
+### 2. Remote development
+
+**VS Code Remote-SSH**, **JetBrains Gateway**, **GitHub Codespaces** (browser or VS Code), **cloud workstations**, etc. The canonical tree may stay in the cloud while your editor connects over SSH or a vendor tunnel; some setups also mirror files to disk.
+
+**When to use:** You want a powerful or standardized environment without maintaining it on the laptop.
+
+### 3. Download / export
+
+**Release zips**, **CI artifacts**, **container images** with source, or **object storage** (S3, Azure Blob) with folder download.
+
+**When to use:** One-off copies, releases, or generated drops rather than daily edit loops.
+
+### 4. Sync clients
+
+Cloud folders synced to a local directory (Dropbox-style). Possible for files; **risky for active Git repos** (conflicts, corrupted `.git`) unless the team standardizes carefully.
+
+**When to use:** Non-Git assets or small teams with clear rules; usually prefer Git instead.
+
+### 5. Private network access
+
+Source on a **VM or file share** in a VPC: **VPN**, **ExpressRoute** / private link, **bastion + scp/rsync**, or **SMB/NFS mounts** so your machine sees the path.
+
+**When to use:** Enterprise code that never leaves a private boundary except over approved network paths.
+
+### 6. API or internal portal
+
+Internal “download project” APIs, **package registries** (npm, PyPI, NuGet, Artifactory), or portals that ship **libraries / SDKs** rather than a full app repo.
+
+**When to use:** Consuming versioned packages; partial source compared to a full monorepo clone.
+
+### Summary
+
+| Need | Typical approach |
+|------|------------------|
+| Full project, day-to-day | **Git** clone + pull/push |
+| Edit on a managed remote machine | **Remote dev** / cloud IDE |
+| Snapshot or release | **Download** / artifact / image |
+| Code only inside corporate cloud | **VPN** + Git or **rsync/SSH** |
+| Consume binaries or APIs | **Registry** / internal **API** |
+
+For embedding GTD in your own app (SDK, MCP, prompts), see **[docs/CUSTOM-INTEGRATION-GUIDE.md](docs/CUSTOM-INTEGRATION-GUIDE.md)**.
+
+---
+
 ## SDK for CI/CD
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@karthikrajkumar.kannan/get-things-done",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "description": "Bidirectional spec-driven agentic framework — Forward (idea to code to deploy), Backward (code to docs), Sync (drift detection and reconciliation). The first framework that goes both ways.",
   "keywords": [
     "ai",