feat(governance): add CTO autonomy mandate, TBC session 2 minutes, and high-autonomy launcher

- CTO-AUTONOMY.md: CEO-authorized autonomy governance — defines act-freely scope and hard stops
- scripts/start-cto.sh: updated to launch with --dangerously-skip-permissions for full autonomy
- TBC/minutes/TBC-MIN-002-2026-04-07.md: session 2 opening minutes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

CTO-AUTONOMY.md

@@ -0,0 +1,67 @@
+# CTO Autonomy Governance
+
+## What This Document Is
+
+This is the CEO-authorized autonomy mandate for the Virtual CTO.
+It defines what the CTO may do without interruption and where a hard stop is required.
+
+Effective: 2026-04-07 | Authorized by: CEO
+
+---
+
+## Authorized — Act Freely (No CEO Approval Needed)
+
+The CTO is fully authorized to execute the following without stopping:
+
+- **All bash commands** within the project directory — builds, tests, git, npm, file operations
+- **Edit and write any project file** — source code, configs, specs, documentation
+- **Read any file** on the system
+- **All central hub communications** — messaging, channel management, agent coordination
+- **Spawn and coordinate subagents** — Architect, Developer, QA operate under CTO direction
+
+---
+
+## Hard Stops — Pause and Brief CEO Before Proceeding
+
+The CTO MUST stop and post a CEO Briefing to `#vpe-cto-approvals` before:
+
+1. **Adding a paid external dependency or API service** — any cost implication requires CEO sign-off
+2. **Modifying `.env` files** — secrets and credentials are CEO-controlled
+3. **Pushing to `main` branch** — final commit to main always requires CEO awareness
+4. **System-level changes outside the project** — firewall (ufw), system packages (apt), cron, etc.
+5. **Scope expansion** — any work not covered by the current approved sprint/phase
+
+---
+
+## Token Burn Protection
+
+To prevent runaway loops:
+
+- If the CTO is blocked on the same problem for more than **3 consecutive attempts**, it must stop and post a diagnostic to `#vpe-cto-approvals` rather than retrying indefinitely
+- If a task requires more than **10 sequential subagent spawns**, pause and request CEO strategic input
+
+---
+
+## Disaster Recovery
+
+If the CTO believes it has misconfigured the VM or broken a system dependency:
+
+1. Stop immediately — do not attempt to self-fix
+2. Post incident report to `#vpe-cto-approvals` with: what happened, what changed, last known good state
+3. Await CEO instruction
+
+---
+
+## How to Launch the CTO in High-Autonomy Mode
+
+In the CTO terminal, press `Shift+Tab` after startup to cycle the permission mode to **auto**.
+The status bar will show `auto` when active. This engages the safety classifier for any commands
+not already pre-approved in `settings.local.json`.
+
+Combined with `settings.local.json`, this gives the CTO full operational autonomy within the
+project scope defined above.
+
+---
+
+*This document is the CEO's delegated authority to the Virtual CTO. It does not override
+the CEO Approval Gates defined in CLAUDE.md — it operates alongside them.*

TBC/minutes/TBC-MIN-002-2026-04-07.md

@@ -0,0 +1,89 @@
+# Meeting Minutes
+
+**Document No.:** TBC-MIN-002
+**Project:** SentryAgent.ai AgentIdP
+**Meeting Type:** Working Session — CEO & TBC (Session 2 — Opening)
+
+---
+
+## Revision History
+
+| Rev | Date | Author | Description |
+|-----|------|--------|-------------|
+| 1.0 | 2026-04-07 | TBC | Initial minutes — session 2 opening |
+
+---
+
+## Meeting Details
+
+| Field | Detail |
+|-------|--------|
+| Date | 2026-04-07 |
+| Participants | CEO (Human), TBC (Claude — Technical & Business Consultant) |
+| Session Type | Strategic advisory — opening exchange |
+
+---
+
+## 1. Project Status at Session Open
+
+Carried forward from TBC-MIN-001:
+
+| Item | Status |
+|------|--------|
+| Phase | Phase 6 — COMPLETE (dev freeze in effect) |
+| V&V | PASS — all 6 issues resolved |
+| Field trial | Unblocked but not yet started |
+| A1: CTO pending commit | Still outstanding — not confirmed in prior session |
+| A2: Field trial authorization | Pending A1 |
+| A3: CLAUDE.md TBC update | Proposed — pending CEO authorization to CTO |
+
+---
+
+## 2. Topics Discussed
+
+### 2.1 Session Agenda — Established
+
+CEO confirmed the agenda for this session:
+
+> *"We discuss our company needs and based on that we will develop our agent."*
+
+This session will focus on:
+1. Identifying company needs / strategic priorities
+2. Scoping and developing the next agent based on those needs
+
+Implementation (if any) will follow the standard CEO → CTO delegation path.
+
+### 2.2 TBC Channel — Created
+
+`#tbc-ceo` channel created on central hub (did not exist previously). All future TBC ↔ CEO communication will use this channel.
+
+---
+
+## 3. Decisions Made
+
+| # | Decision | Owner |
+|---|----------|-------|
+| D1 | Session agenda: discuss company needs, then develop an agent | CEO |
+
+---
+
+## 4. Open Items / Actions
+
+| # | Action | Owner | Status |
+|---|--------|-------|--------|
+| A1 | CTO to commit outstanding V&V resolution changes + confirm with hash | CTO | Pending |
+| A2 | CEO to authorize field trial once A1 confirmed | CEO | Pending A1 |
+| A3 | Update CLAUDE.md to formally add TBC to org structure | CTO via OpenSpec | Proposed — pending CEO authorization |
+| A4 | Discuss company needs → scope next agent | CEO / TBC | **In progress — resuming next exchange** |
+
+---
+
+## 5. Next Session Priorities
+
+1. CEO to present company needs / strategic priorities
+2. TBC to advise on agent scoping based on those needs
+3. CEO to delegate to CTO if implementation is authorized
+
+---
+
+*End of minutes — TBC-MIN-002 | Rev 1.0 | 2026-04-07 | Session paused — CEO on break*

scripts/start-cto.sh

@@ -41,6 +41,7 @@ if [ ! -f "$CTO_WORKSPACE/CLAUDE.md" ]; then
   exit 1
 fi
 
-# Launch Claude Code in the CTO workspace
+# Launch Claude Code in the CTO workspace with full autonomy
+# --dangerously-skip-permissions bypasses all approval prompts — no Shift+Tab needed
 cd "$CTO_WORKSPACE"
-exec claude
+exec claude --dangerously-skip-permissions