> For the complete documentation index, see [llms.txt](https://gotts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gotts.gitbook.io/docs/prd-shared/timeline.md).

# Timeline

> **Last Updated**: 2026-02-21 | **Referenced by**: All domain PRDs
>
> Unified implementation timeline synthesizing phase schedules from all PRD domains. Week numbers are relative to the start of development (Week 0 = project kickoff). Dependency annotations indicate when one domain unblocks another.

***

## Domain Summary

| Domain                  | Phases                          | Week Range | Source                                                                                 |
| ----------------------- | ------------------------------- | ---------- | -------------------------------------------------------------------------------------- |
| Devenv                  | 1 phase (precondition)          | 0–2        | [devenv/](/docs/devenv/devenv.md)                                                      |
| Gotts Safe (MCP server) | 7 phases                        | 1–28       | [mcp-server/12-milestones.md](/docs/gotts-safe-mcp-server/mcp-server/12-milestones.md) |
| Gotts Vaults            | 5 phases (+ Track A–G deferred) | 0–22       | [vault/14-milestones.md](/docs/gotts-vaults/vault/14-milestones.md)                    |
| Agents                  | 3 phases                        | 1–20       | [agents/12-milestones.md](/docs/agents/agents/12-milestones.md)                        |
| Skills                  | 3 phases                        | 5–22       | [skills/11-milestones.md](/docs/skills/skills/11-milestones.md)                        |
| Website                 | 3 phases                        | 1–24       | [website/](/docs/website/website.md)                                                   |

***

## Week-by-Week Phase Map

| Week  | Devenv                | Gotts Safe           | Gotts Vaults                | Agents                    | Skills                | Website                |
| ----- | --------------------- | -------------------- | --------------------------- | ------------------------- | --------------------- | ---------------------- |
| 0     | **Devenv setup**      | —                    | **P0: Baseline Lock**       | —                         | —                     | —                      |
| 1–2   | **Devenv (complete)** | **P1: Foundation**   | **P1: Factory Core**        | **A1: Foundation**        | —                     | **W1: Landing Page**   |
| 3–4   | ✓                     | P1                   | P1                          | A1                        | —                     | W1                     |
| 5–8   | ✓                     | **P2: Trading**      | P1 → **P2: Core MCP**       | A1                        | **S1: Trading/LP**    | W1                     |
| 9–12  | ✓                     | **P3: Liquidity**    | P2 → **P3: Safety+am-AMM**  | **A2: Core Agents**       | S1                    | **W2: App (explorer)** |
| 13–15 | ✓                     | **P4: Advanced**     | P3                          | A2                        | **S2: Advanced**      | W2                     |
| 16–20 | ✓                     | **P5: Hardening**    | **P4: Reputation+Adapters** | A2 → **A3: Vault Agents** | S2                    | **W3: Portal**         |
| 18–22 | ✓                     | P5                   | **P5: Mainnet Readiness**   | A3                        | S2                    | W3                     |
| 21–24 | ✓                     | **P6: CCA/am-AMM**   | ✓ (mainnet)                 | ✓                         | **S3: Vault+Economy** | W3                     |
| 25–28 | ✓                     | **P7: Intelligence** | Track A–G (post-v1)         | ✓                         | S3                    | ✓                      |

**Legend:** ✓ = phase complete; — = not started; "P0" = phase designator; "A" = agents; "S" = skills; "W" = website.

***

## Phase Details by Domain

### Devenv (Weeks 0–2)

Precondition for all other development. Must be available before Gotts Safe Phase 1 and Vault Phase 1 can begin.

| Phase | Weeks | Goal                                                                                   |
| ----- | ----- | -------------------------------------------------------------------------------------- |
| Setup | 0–2   | Full Uniswap stack (V2/V3/V4/UniswapX/ERC-8004) on local Anvil; debug UI; seed scripts |

**Unblocks**: Gotts Safe P1 (forked mainnet tests), Vault P1 (testnet deployment).

***

### Gotts Safe MCP Server (Weeks 1–28)

7 phases. See [mcp-server/12-milestones.md](/docs/gotts-safe-mcp-server/mcp-server/12-milestones.md) for full deliverables.

| Phase            | Weeks | Goal                                               | Key Deliverables                                                 |
| ---------------- | ----- | -------------------------------------------------- | ---------------------------------------------------------------- |
| P1: Foundation   | 1–4   | Read-only data tools, caching, eval framework      | `get_token_price`, `get_pool_info`, chain provider layer         |
| P2: Trading      | 5–8   | Swap execution, safety pipeline, production deploy | `get_quote`, `execute_swap`, safety middleware, Fly.io deploy    |
| P3: Liquidity    | 9–12  | LP management, V4 PositionManager                  | `add_liquidity`, `remove_liquidity`, `calculate_il`              |
| P4: Advanced     | 13–16 | UniswapX, cross-chain, x402, Privy/Safe wallets    | `submit_uniswapx_order`, x402 CoinGecko + Elsa providers         |
| P5: Hardening    | 17–20 | Prompt injection defense, reputation gates, audit  | CaMeL dual-LLM, ERC-8004 tier enforcement middleware             |
| P6: CCA/am-AMM   | 21–24 | CCA tools, Liquidity Launcher, am-AMM              | `get_cca_state`, `submit_cca_bid`, `launch_token`                |
| P7: Intelligence | 25–28 | Intelligence tools, smart accounts, DX             | `simulate_pool_scenario`, `submit_user_operation`, all 147 tools |

***

### Gotts Vaults (Weeks 0–22)

5 phases. See [vault/14-milestones.md](/docs/gotts-vaults/vault/14-milestones.md) for full deliverables and acceptance gates.

| Phase                     | Weeks | Goal                                         | Key Deliverables                                                                |
| ------------------------- | ----- | -------------------------------------------- | ------------------------------------------------------------------------------- |
| P0: Baseline Lock         | 0–1   | PRD alignment, count freeze                  | DRIFT-MATRIX, IMPLEMENTATION-STATE baseline                                     |
| P1: Factory + Core        | 1–5   | Permissionless vault creation, ERC-4626 core | `AgentVaultFactory`, `AgentVaultCore`, `NAVAwareHook`, auto-market creation     |
| P2: Core MCP + SDK        | 6–9   | External agent access, SDK clients           | 24 core vault MCP tools, `VaultClient`, `OnboardRouter`, swarm testnet          |
| P3: Safety + am-AMM       | 10–15 | Proxy hardening, am-AMM auctions             | `AgentProxy`, am-AMM tools, ERC-7265 circuit breakers                           |
| P4: Reputation + Adapters | 16–20 | Milestone lifecycle, pluggable strategies    | Reputation engine, `MorphoSupplyAdapter`, `AaveV3SupplyAdapter`, yield feedback |
| P5: Mainnet               | 18–22 | Launch on Base                               | Audit, Base deployment, monitoring dashboards, SIWE auth                        |

**Mainnet-blocking gate (P3)**: Proxy module MUST be functional before P5. Without it, the safety model relies on TEE + policy engine alone (12% bypass rate per D-036).

***

### Agents (Weeks 1–20)

3 phases. Agents are defined in `packages/safe/agents/` (core) and `packages/vault/agents/` (vault) and deployed alongside MCP server phases.

| Phase                 | Weeks | Goal                                     | Key Agents                                                                                                                      |
| --------------------- | ----- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| A1: Foundation        | 1–8   | Core research + execution agents         | `pool-researcher`, `token-analyst`, `trade-executor`, `liquidity-manager`, `safety-guardian`                                    |
| A2: Core Agents       | 9–15  | Strategy, economy, infrastructure agents | `lp-strategist`, `risk-assessor`, `treasury-manager`, `protocol-fee-seeker`                                                     |
| A3: Vault + Real-Time | 16–20 | Vault lifecycle + monitoring agents      | `vault-manager`, `vault-strategist`, `vault-creator`, `vault-allocator`, `vault-executor`, `market-monitor`, `position-monitor` |

**Dependencies**: A1 requires Gotts Safe P1 (read tools available). A2 requires Gotts Safe P2 (write tools). A3 requires Vault P2 (vault MCP tools).

***

### Skills (Weeks 5–22)

3 phases. Skills are user-facing interfaces defined in `packages/safe/skills/` (core) and `packages/vault/skills/` (vault).

| Phase                | Weeks | Goal                                   | Key Skills                                                                            |
| -------------------- | ----- | -------------------------------------- | ------------------------------------------------------------------------------------- |
| S1: Trading + LP     | 5–12  | Core trading and liquidity skills      | `execute-swap`, `manage-liquidity`, `analyze-pool`, `research-token`                  |
| S2: Strategy + Infra | 13–20 | Strategy, safety, composite skills     | `assess-risk`, `check-safety`, `research-and-trade`, `full-lp-workflow`               |
| S3: Vault + Economy  | 21–25 | Vault and Agent Capital Markets skills | `deposit-vault`, `manage-vault`, `bid-amamm`, `manage-treasury`, `seek-protocol-fees` |

**Dependencies**: S1 requires Agents A1. S2 requires A2 + Gotts Safe P5 (safety hardening). S3 requires A3 + Vault P2.

***

### Website (Weeks 1–24)

3 phases. See [website/](/docs/website/website.md) PRDs.

| Phase            | Weeks | Goal                                   | Key Deliverables                                                            |
| ---------------- | ----- | -------------------------------------- | --------------------------------------------------------------------------- |
| W1: Landing Page | 1–8   | `gotts.ai` marketing site              | Product suite overview, security architecture, market context, partner list |
| W2: App          | 9–16  | `app.gotts.ai` on-chain dashboard      | Vault explorer (list + detail), agent directory, connected wallet view      |
| W3: Portal       | 17–24 | `portal.gotts.ai` agent account portal | Custody setup wizard, ERC-8004 registration, agent profile management       |

**Dependencies**: W2 requires Vault P1 (factory data available for explorer). W3 requires Vault P2 (onboarding tools) + Gotts Safe P4 (wallet provisioning).

***

## Cross-Domain Dependencies

| Dependency                       | Blocks                                                           |
| -------------------------------- | ---------------------------------------------------------------- |
| Devenv (W0–2)                    | Gotts Safe P1 (forked mainnet tests), Vault P1 (testnet deploy)  |
| Gotts Safe P1 (read tools)       | Agents A1 (research agents), Website W2 (pool data for explorer) |
| Gotts Safe P2 (write tools)      | Agents A2 (execution agents), Skills S1 (swap/LP skills)         |
| Gotts Safe P5 (safety hardening) | Agents A3 (vault agents use hardened safety pipeline)            |
| Vault P1 (factory deployed)      | Website W2 (vault explorer), Agents A3 (vault agents)            |
| Vault P2 (MCP tools live)        | Skills S3 (vault skills), Website W3 (portal onboarding)         |
| Vault P3 (proxy gate ✓)          | Vault P5 (mainnet launch — proxy is a mainnet-blocking gate)     |
| Vault P4 (reputation engine)     | Skills S3 (yield discovery, reputation-gated features)           |

***

## Deferred Tracks (Post-v1, Vault)

Post-mainnet expansion tracks have no fixed week targets. They activate based on entrance criteria documented in [vault/14-milestones.md](/docs/gotts-vaults/vault/14-milestones.md).

| Track                        | Scope                                                                                                 | Entrance Criteria                                               |
| ---------------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| Track A: CCA Expansion       | `submit_cca_bid`, CCA lifecycle                                                                       | Vault P3+ stable in staging, CCA risk model validated           |
| Track B: Viral Growth        | Referrals, multiplier points, streak mechanics                                                        | Core retention targets met for 2 windows; Sybil model validated |
| Track C: Advanced V4         | JIT liquidity, PolicyCage, reputation-tiered LP                                                       | Vault P6 V4 modules stable                                      |
| Track D: Cross-Vault         | ExecutionMarket, LiquidityRouter, intent solver                                                       | 50+ active vaults; Track A stable                               |
| Track E: Composability       | Pendle integration, Morpho collateral, recursive lending                                              | Vault P5 stable 4+ weeks; adapters audited                      |
| Track F: Structured Products | Tranches (PYT), BondMM fixed-rate                                                                     | Track E lending adapters operational                            |
| Track G: ve-Token Governance | Optional veVAULT module (D-050); vote-escrowed governance with no protocol-level revenue distribution | 100+ active vaults; community demand for on-chain governance    |
