Organization System Map
Researcher, underwriter, CGO, ops, and QA as scoped profiles/tool bundles with explicit guardrails.
Researcher, underwriter, CGO, ops, and QA are explicit scopes — not random dashboard cards.
This follows the structure from /home/azureuser/temp/mermaid1.txt and treats /home/azureuser/temp/mermaid2.txt as an example of what proper profile, scope, skill-bundle, and tool-bundle management can become. It is intentionally an operating model, not a claim that every profile is fully live today.
Command + strategy
Owner/partner authority plus Hermes orchestration. Material actions stay approval-gated.
Core OS layers
Memory, reporting, anomaly detection, quality gates, and scheduled strategic review loops.
Researcher profile
Read-only diligence indexing and source-linked facts before recommendations or underwriting claims.
Underwriting track
Evidence saturation first; final underwriting only after data room, workflow, and risk unknowns are resolved.
Growth/CGO engine
Uses the research base to propose scale bets, channels, referral systems, and automation initiatives.
Ops automation engine
CRM, lead-flow, support, calendar, and utility agents can be scoped as profiles/tool bundles.
Research bundle
scopedScope: Data-room read, web research, source notes, question packs
Guardrail: No contact/outreach
Underwriter bundle
scopedScope: Financial extraction, risk questions, evidence checks
Guardrail: No final call before saturation
Growth bundle
scopedScope: SEO, referral, paid/social, email strategy
Guardrail: No live publishing/sends without approval
Ops bundle
scopedScope: Zoho, lead intake, routing, support automations
Guardrail: Read-only until write approvals exist