Mikaeel's operating system

Workspace: Callosym

LIVE MO
Security shield offline. Set DASHBOARD_PASSWORD before exposing this dashboard.

Business operating unit

Callosym

Hermes coordinates this company through isolated departments, agents, memory and credentials.

+ Launch mission

Internal command map

Callosym departments

Hermes linked
CCallosymBusiness lead
H
ExecutiveChief of Staff3 specialist agents
M
MarketingGrowth Director4 specialist agents
S
SalesRevenue Director4 specialist agents
O
OperationsOperations Director4 specialist agents
X
TechnologyTechnology Director4 specialist agents
G
Ads & GrowthPerformance Director4 specialist agents
I
Research & SEOIntelligence Director4 specialist agents

Isolation layer

Business systems

Manage connections →

No accounts linked to this business yet. Connections will be added through isolated n8n credentials.

Execution layer

Callosym modules

Open capability mesh →
H
Executive BriefingCombine every department into morning, weekly and exception-based decision reports.
ready

Profile

# Callosym Profile

## Purpose
Coordinate Callosym technical execution, architecture decisions, and go-to-market alignment.

## Responsibilities
- Architecture planning and technical sequencing
- GitHub and delivery status tracking
- Marketing support and follow-up loops
- Cross-functional technical communication

## Priorities
- Maintain technical clarity and momentum
- Prevent hidden delivery risk
- Keep strategic positioning coherent

## Hermes Role
Hermes acts as a digital Chief of Staff for this workspace: reduce admin load, prepare execution-ready drafts, and surface approvals early.

## Approval Boundaries
- `GREEN`: research, drafts, summaries, planning, internal preparation.
- `AMBER`: any external-facing execution (emails, posts, client messages, scheduling with others) requires approval before sending.
- `RED`: financial, contractual, legal, booking, or destructive actions always require explicit approval each time.

## Tone
Futuristic, clean, technical, strategic, direct.

## Avoid
- Hand-wavy technical statements
- Status updates without risk flags
- External announcements without AMBER approval

Brand

# Callosym Brand

## Voice
Technical, strategic, future-facing, crisp.

## Style Notes
- Minimal, high signal
- Modern system feel
- No clutter

## Keep Out
- Hand-wavy technical statements
- Status updates without risk flags
- External announcements without AMBER approval

Current focus

# Callosym Current Focus

## Active Priorities
- Architecture decisions that unblock delivery
- Execution visibility across workstreams
- Narrative alignment between product and marketing

## Next Update Pattern
- Refresh this file weekly or after major priority changes.

Notes

# Callosym Notes

## Working Notes
- Add short, dated notes here as things change.
- Keep entries concrete and action-oriented.
- Move stable policies into `sops/how-we-work.md`.

Services

# Callosym Services

## Hermes-Supported Services
- Roadmap decomposition and milestone framing
- Technical status summaries
- Architecture option comparisons
- Launch prep checklists

## Service Rules
- Prefer drafts and preparation first; execute only within approval boundaries.
- Keep outputs concise, practical, and decision-ready.
- No pretend integration behavior: if no live connector exists, output is draft/manual only.

Assets summary

  • brand: 1 files
  • logos: 1 files
  • reference: 1 files
  • social: 1 files

Recent inbox files

  • README.md

Recent generated outputs

  • README.md