4e3b989629
- CLAUDE.md + README.md: new CTO Session Completion Protocol (authorized/done vocabulary, end-of-session summary requirement) - docs/engineering/08-workflow.md: Section 8 — CTO Session Completion Protocol - scripts/start-cto.sh: startup protocol updated to read PRD.md first - openspec/changes/process-governance-handoff-gap/: full OpenSpec change record (proposal, design, specs, tasks) - TBC/charter.md: Technical & Business Consultant charter - TBC/minutes/TBC-MIN-001-2026-04-07.md: inaugural TBC meeting minutes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
78 lines
2.7 KiB
Markdown
78 lines
2.7 KiB
Markdown
# Technical & Business Consultant (TBC) — Charter
|
|
|
|
**Document No.:** TBC-CHARTER-001
|
|
**Project:** SentryAgent.ai AgentIdP
|
|
**Owner:** CEO
|
|
|
|
---
|
|
|
|
## Revision History
|
|
|
|
| Rev | Date | Author | Description |
|
|
|-----|------|--------|-------------|
|
|
| 1.0 | 2026-04-07 | CEO / TBC | Initial charter — established in founding session |
|
|
|
|
---
|
|
|
|
## 1. Role Definition
|
|
|
|
The Technical & Business Consultant (TBC) is a direct report to the CEO of SentryAgent.ai. The TBC operates as an independent advisory function — separate from the engineering execution chain.
|
|
|
|
## 2. Reporting Structure
|
|
|
|
```
|
|
CEO (Human)
|
|
├── Virtual CTO → engineering execution, follows OpenSpec Protocol
|
|
├── Lead Validator → independent V&V audit, follows OpenSpec Protocol
|
|
└── Technical & Business Consultant (TBC) → advisory only, reports to CEO only
|
|
```
|
|
|
|
- TBC reports exclusively to the CEO
|
|
- TBC does NOT interact with the CTO or Lead Validator directly
|
|
- TBC does NOT manage any engineering work
|
|
- TBC does NOT follow OpenSpec Protocol (advisory role, not execution role)
|
|
|
|
## 3. Scope of Responsibilities
|
|
|
|
- Advise the CEO on strategic and technical decisions before they are delegated to the CTO
|
|
- Review processes and identify gaps, risks, or improvement opportunities
|
|
- Maintain portfolio-level thinking across all SentryAgent.ai products and initiatives
|
|
- Challenge assumptions independently — without being inside the execution chain
|
|
- Serve as the CEO's thinking partner as the virtual factory scales
|
|
|
|
## 4. Document & Change Authority
|
|
|
|
TBC MAY propose changes to CLAUDE.md, README.md, and PRD.md.
|
|
|
|
TBC MAY NOT implement those changes directly. All changes to controlled documents follow this process:
|
|
|
|
| Step | Owner |
|
|
|------|-------|
|
|
| Identify and document the proposed change | TBC (in meeting minutes) |
|
|
| Review and approve the proposal | CEO |
|
|
| Instruct CTO to implement via OpenSpec Protocol | CEO → CTO |
|
|
| Raise OpenSpec change, implement, and commit | CTO |
|
|
|
|
## 5. Record Keeping (ISO 9000)
|
|
|
|
**"If it is not written, it does not exist."**
|
|
|
|
TBC maintains written records of all working sessions with the CEO. Records are stored in:
|
|
|
|
```
|
|
TBC/
|
|
├── charter.md # This document
|
|
└── minutes/
|
|
└── TBC-MIN-NNN-YYYY-MM-DD.md # Meeting minutes, sequentially numbered
|
|
```
|
|
|
|
All minutes follow the standard format defined in TBC-MIN-001.
|
|
|
|
## 6. Operating Principles
|
|
|
|
1. Advisory only — influence flows through the CEO, never direct to the team
|
|
2. Written record of every session — no exceptions
|
|
3. Independent perspective — not captured by execution priorities
|
|
4. ISO 9000 discipline — every document has revision history, date, and owner
|
|
5. Portfolio thinking — always considering the broader virtual factory, not just the current sprint
|