Valent — Tactical/Operational View

The Business Problem

Valent Partners is a 90-person consulting firm delivering PMO/program management to Fortune 1000 clients. Their consultants spend 100% of their time producing deliverables — sprint backlogs, status reports, roadmaps, product backlogs. This is the bottleneck: to take on more client engagements, they need more consultants. Revenue scales linearly with headcount.

Our value proposition: Warren produces the deliverables. Valent's consultants focus on client relationships, strategy, and judgment — the 20% that produces 80% of the value. One AI partner per engagement = capacity multiplier without headcount growth.

Revenue impact for Valent: 1-2 FTE equivalent savings = $200K-$500K/year per engagement Warren supports. If Valent runs 5 engagements with Warren, that's $1M-$2.5M in capacity unlocked.

What We Built (June 6, 2026)

Asset	Status	What It Does	Business Problem It Solves
SOUL.md	✅ Done	Client-facing persona with Pareto Lens communication DNA, sanitization rules, operator hierarchy	Every interaction surfaces the highest-value insight. Differentiates from generic AI that just answers questions.
MEMORY.md	✅ Done	Seed knowledge: Valent company context, 4 stakeholder profiles, pilot scope, methodology (See It Cycle, Pareto Lens, Show Me Don't Tell Me)	Day 1 competence. Warren knows Valent's business, team, and standards from the first interaction — no cold start.
AGENTS.md	✅ Done	Operating rules: See It Cycle (4-stage methodology), Maybe Gate (focus on ambiguity), Show Me Don't Tell Me (evidence-based), deliverable workflow, escalation paths	Consistent methodology embedded in every output. Not just producing artifacts — producing artifacts that question whether the team is focused on what matters.
IDENTITY.md	✅ Done	Warren = AI-Powered PMO Operations Partner for Valent	Clear identity for the client. Professional, not confusing.
USER.md	✅ Done	4 user profiles with communication style calibration (RJ=practical, Hector/Nick=executive, Matt=technical)	Personalized interaction from day 1. RJ gets workflow value, Hector gets strategic impact, Matt gets honest technical depth.
TOOLS.md	✅ Done	Full capability set: PMO deliverables, technical deliverables (BDD/TDD/user stories/business rules), executive reports, published URLs, cron automation, review & analysis	Valent sees the full capability — not just 4 SOW deliverables. Creates upsell path for Phase 2+.
BOOTSTRAP.md	✅ Done	5-point pre-response checklist: scope, data integrity, format, isolation, tone	Quality gate on every single response. Prevents hallucination, data leaks, scope creep.
Kickoff Prep Kit	✅ Done	90-min agenda, persona playbook, data checklist, risk register (8 risks), 7 decisions for Charlie	Victor walks into Monday session and kickoff meeting fully prepared. No improvisation.

2. Architecture — How It Works

GitHub Config Sync Model

Production system (DGX/Slack) maintains the golden configuration repo. Client instances (AWS/Teams) are deployed from this repo. Knowledge transfer flows through git — not real-time API calls.

┌─────────────────────┐     git push      ┌──────────────────────┐
│  Warren (DGX/Slack)  │ ──────────────▶  │  Golden Repo (GitHub) │
│  - Maintains config  │                   │  t-and-c-golden       │
│  - Evaluates quality │                   │  └── clients/valent/  │
│  - Coaches via files │                   │      └── workspace/   │
└─────────────────────┘                   └──────────┬───────────┘
                                                      │ deploy
                                                      ▼
                                          ┌──────────────────────┐
                                          │  Valent Instance      │
                                          │  (AWS/Teams)          │
                                          │  - Client-facing      │
                                          │  - Sanitized          │
                                          │  - Isolated context   │
                                          └──────────────────────┘

Key design decisions:

All infra on VTKL AWS — we control logs, outputs, iteration. Not deployed on client infrastructure.
Isolated channel per client — no data leakage between deployments.
Warren coaches via git — updates memory, skills, methodology files. Client instance picks up changes on next sync.
Sanitization is absolute — zero internal references in client workspace. Verified by automated grep.

Document Ingestion Flow (Option A — Confirmed)

┌──────────────────┐    upload     ┌──────────────────┐    ingest    ┌──────────────────┐
│  Valent Team      │ ──────────▶ │  Teams Channel    │ ──────────▶ │  Warren (AWS)     │
│  (RJ, Nick, etc.) │  .docx/.pdf │  (designated)     │  automatic  │  - Parses docs    │
│                    │  .pptx/txt  │                    │             │  - Acknowledges   │
└──────────────────┘              └──────────────────┘             │  - Flags gaps     │
                                                                    │  - Produces        │
                                                                    │    deliverables    │
                                                                    └──────────────────┘

No manual handoff. The Teams channel IS the ingestion interface. Valent drops files, Warren reads them, acknowledges receipt, and flags any data gaps or quality issues.

⚠️ Open question for Charlie (Monday): Confirm that OpenClaw on Teams reliably parses .docx, .pdf, .pptx file attachments. If not, identify workaround before June 10 kickoff.

3. Methodology — The Differentiator

This is what separates Warren from ChatGPT/Copilot/generic AI. Three interconnected systems embedded in every interaction:

🔄 The See It Cycle

Every sprint, every deliverable follows four stages:

Stage	Question	What Warren Does
1. SEE where you want to go	What's the highest-value outcome?	Applies 3 filters: Exposed (gap that changes dynamic), Unguarded (path bypassing resistance), Disproportionate (small intervention → outsized results). Prioritizes backlogs and recommendations accordingly.
2. SEE where you are	What's actually happening vs. what was planned?	Reality check at midpoints. Compares progress against the TARGET, not the plan. Plans drift — reality doesn't.
3. SEE how to get there	Is the output moving toward the target?	Before/after comparison. Evidence over assertions. Every checkpoint verifies demo vs commitment.
4. SEE what works	What actually moved the needle?	Retrospective: identifies counterfeit productivity (effort that felt productive but didn't create value). Recalibrates for next cycle.

Each sprint IS one cycle. Each release IS a cycle of cycles. More cycles = faster, more accurate delivery.

📊 The Pareto Lens (Communication DNA)

Not a feature — it's how Warren thinks and communicates. Every interaction is filtered through: "Is this the 20% that produces 80% of the results?"

Deliverables: Most important finding leads. Never buried on page 12.
Backlogs: Ranked by impact, not volume. "Which 3 items would you keep if you had to cut the rest?"
Status reports: Lead with what changed the dynamic, not what was completed.
Recommendations: One clear recommendation with reasoning. Not a menu of options — menus are abdication of judgment.
Proactive challenges: If the data shows the team is spending 80% effort on 20% value, Warren surfaces that. Always.

👁️ Show Me, Don't Tell Me

Claims grounded in ingested project data with traceable references
Status demonstrated through artifacts, not assertions
"Before" snapshots for measurable progress
Verification is 100% of items, not spot-checked
If data is insufficient → Warren says what's missing rather than guessing

Why this matters for Valent: Their consultants already know the answers — they just spend too much time producing the artifacts that prove it. Warren produces the artifacts AND asks the questions that surface whether the team is focused on the right things. That's the "Tony's okay = customer's good or great" calibration — our baseline exceeds what Valent's clients are used to seeing.

4. What's Done vs. What's Pending

✅ Completed (June 6)

Bootstrap kit — 7 files in golden repo (clients/valent/workspace/)
See It Cycle + Pareto Lens + Maybe Gate + Show Me Don't Tell Me embedded in SOUL/AGENTS/MEMORY
Full capability set in TOOLS.md (PMO + technical + executive + automation)
Sanitization verified — zero internal references
Kickoff prep kit with agenda, personas, risks, decisions
Ingestion flow decided (Option A — Teams upload)
Stakeholder deep research compiled
SOW signed and referenced throughout

⏳ Pending — Monday Session with Charlie

Architecture: GitHub config sync mechanism — how exactly does Warren update the Valent instance?
Naming: "Warren" (matches SOW) — needs final confirmation
Teams integration: install bot in Valent's tenant — Charlie to configure on AWS
Governance gates: which Phase 0 items (#6-#9 on golden repo) are truly blocking?
Dogfood skip: time for dogfood before June 10, or go direct?
Teams file parsing: confirm .docx/.pdf/.pptx ingestion works reliably
Who attends kickoff? Charlie/Tony for intros?

🔴 Blocked Until Charlie

AWS deployment of Valent instance
Teams app installation in Valent's tenant
Skills transfer from Warren → Valent instance (which skills ship?)
Cron/automation setup on AWS

5. Risk Register — Operational View

Risk	Severity	Mitigation (What We Did)	Residual Gap
Bootstrap Gap — 5 days vs 3+ months	HIGH	Pre-seeded MEMORY.md with company context, stakeholders, methodology. See It Cycle + Pareto Lens embedded. Warren coaches via git.	Still no real project data until Valent uploads. First 48h will be calibration.
Data Control — losing access if on client infra	HIGH	All infra on VTKL AWS. Decided and documented.	Talking point needed for kickoff if Valent asks "why not in our environment?"
Quality Calibration — agentic vs human teams	MED	Phase 1 = deliverables only, not estimation. PMO-specific methodology seeded.	First deliverables will need feedback loop. RJ's candid feedback is critical.
IP Exposure — leaking internals	MED	Sanitization rules in SOUL.md. Context isolation absolute. Grep verified: 0 matches.	Need adversarial testing before go-live (ask it probing questions about internals).
Naming Confusion	LOW	Recommendation: "Warren" (matches SOW). Bootstrap kit uses "Warren".	Need Charlie's confirmation Monday.
Jira Complexity	MED	Phase 1 = doc-based only. Explicitly excluded in SOW §2.2.	Valent may push for Jira earlier. Have clear talking point ready.
Teams File Parsing	MED	Option A confirmed. Documented in TOOLS.md and prep kit.	⚠️ Not yet verified that OpenClaw parses Teams file attachments reliably.

6. Timeline — Operational

Date	Milestone	Owner	Status
Jun 6 (Sat)	Bootstrap kit complete, prep kit published	Warren	✅
Jun 9 (Mon)	Joana + Victor + Charlie architecture session	Joana (lead) + Tony/Charlie	⏳
Jun 9 (Mon)	AWS deployment + Teams config	Charlie	⏳
Jun 9 (Mon)	Dogfood test (if time permits)	Joana	⏳
Jun 10 (Wed)	Kickoff meeting — 90 min	Joana + Victor	⏳
Jun 10-12	Data ingestion (Valent uploads docs)	Valent (RJ)	⏳
Jun 12-13	First deliverable produced (48h target)	Warren/Aria	⏳
Jun 13-24	Hands-on evaluation (pilot days 1-14)	All	⏳
Jun 24	Debrief + decision on next steps	Joana + Victor + Hector	⏳

⚡ Valent Pilot — Tactical / Operational View

1. What Was Built & Why

The Business Problem

What We Built (June 6, 2026)

2. Architecture — How It Works

GitHub Config Sync Model

Document Ingestion Flow (Option A — Confirmed)

3. Methodology — The Differentiator

🔄 The See It Cycle

📊 The Pareto Lens (Communication DNA)

👁️ Show Me, Don't Tell Me

4. What's Done vs. What's Pending

✅ Completed (June 6)

⏳ Pending — Monday Session with Charlie

🔴 Blocked Until Charlie

5. Risk Register — Operational View

6. Timeline — Operational