Role Agent Build Plan

This plan tracks role research and live Hermes profile creation. Some advisory profiles now exist; future profiles should still be created deliberately, one at a time, only when Arijit explicitly starts or approves that build step.

Current Existing Advisory Profiles

Role	Profile	Name	Profile Status	Gateway Status
CEO / Orchestrator	default	Athena	Existing profile	Running primary Telegram gateway
CTO	vulcan	Vulcan	Existing profile	May be running or stopped depending on use
Product / UX Strategy	arjuna	Arjuna	Existing profile	May be running or stopped depending on use
Business / Revenue Advisor	kubera	Kubera	Existing profile	May be running or stopped depending on use
Legal / Risk Advisor	prometheus	Prometheus	Existing profile	May be running or stopped depending on use
COO	none	none	Deferred	None
CFO	none	none	Role card only	None
CMO	none	none	Role card only	None

Build Philosophy

Build durable advisors, not decorative executives.

Each live role profile needs:

• Name.
• Purpose.
• SOUL.
• Memory rules.
• Context boundaries.
• Model routing.
• Default tools.
• Workspace access rules.
• Output contract.
• Escalation rules.
• Fresh-session verification.

Build Order And Status

1. CTO

Status: Live as Vulcan (vulcan).

Reason: Most likely to need persistent memory and long-running founder/advisor conversations immediately.

Initial scope: Architecture, build philosophy, platform choices, technical feasibility, security, integrations, and technical tradeoffs.

Do not grant broad runtime write power by default.

2. Product / UX Strategist

Status: Live as Arjuna (arjuna).

Reason: Product shape, workflow, MVP boundary, and user assumptions will recur across workspaces.

Initial scope: Product strategy plus UX/workflow design, not marketing execution.

3. Business / Revenue Advisor

Status: Live as Kubera (kubera).

Reason: Combines CFO and Head of Sales until separate financial and sales memory streams prove necessary.

Initial scope: Pricing, monetization, buyer, ROI, sales motion, objections, and business model.

4. Risk Advisor

Status: Live as Prometheus (prometheus).

Reason: Useful when data, scraping, public claims, privacy, IP, or customer-facing artifacts become recurring.

Initial scope: Operational risk triage only, not legal advice.

5. COO

Status: Deferred.

Reason: Useful after My OS has enough recurring operating loops, Kanban boards, scheduled reports, QA loops, and handoffs.

Initial scope: Operating cadence, role handoffs, reporting, dependency management, process simplification.

Workspace Structure

Project workspaces remain durable rooms for work.

ELT profiles are company-level advisors. They may be invited into workspaces, but workspaces do not get their own C-suite.

Workspace execution roles remain project-specific and artifact-driven:

• PM.
• Architect.
• Developer.
• QA.
• Researcher.
• Analyst.
• Writer.
• Designer.
• DevOps.
• Product Marketing.
• Sales Enablement.
• Source Auditor.
• Data Engineer.
• Customer Researcher.

Profile Roster

Role	Profile name	Status
CTO	vulcan	Live
Product / UX Strategist	arjuna	Live
Business / Revenue Advisor	kubera	Live
Risk Advisor	prometheus	Live
COO	TBD	Later

Verification Required For Each Live Profile

Before calling a role profile live:

1. Create profile.
2. Add SOUL.
3. Set profile description for routing.
4. Set model and tool policy.
5. Set terminal working directory if needed.
6. Start a fresh session.
7. Ask the role to identify itself and boundaries.
8. Run a three-way Athena + Arijit + role smoke test.
9. Confirm memory behavior and artifact destination.
10. Record the result in My OS.

Not Yet Decided

• Exact profile names for any future COO, CFO, or CMO profiles.
• Which model each profile should use by default in the live VPS config.
• Whether role profiles should be addressable from Telegram directly or only through Athena.
• Whether all live profiles should use Kanban or only execution profiles.
• How cross-profile memory conflicts should be resolved.