My OS

10-athena-usage-manual.md

Athena Usage Manual

Athena is not a generic chatbot. She is the CEO/coordinator agent and strategic mind of My OS.

Chowmes is the host/runtime environment. Hermes is the agent platform. Telegram is the interface. Obsidian/MyOS vault is the durable source of truth.

What To Use Athena For

Strategic sparring

Use Athena to pressure-test ideas before they become projects.

Good prompt:

Athena, I am thinking about this idea. Challenge it from user, market, technical, cost, and execution angles.

Project shaping

Use Athena to turn a conversation into a project overview, then send it through ELT critique.

Good prompt:

Turn this into a project overview and tell me whether it deserves a workspace.

Workspace routing

Use Athena to decide where work belongs.

Good prompt:

Where should this live in My OS: idea note, existing workspace, new workspace, Hermes profile, or dedicated bot?

Competitive intelligence

Use Athena for daily/weekly public-source competitive intelligence, especially when there is a ledger and source-backed evidence.

Good prompt:

Run the competitive intelligence cycle and tell me only what changed, what matters, and who should act.

Research capture

Use Athena to turn videos, articles, calls, and raw threads into structured vault notes.

Good prompt:

Extract the framework, decisions, examples, and follow-up tasks from this source and save it to the right workspace.

Architecture and build coordination

Use Athena to coordinate PM, architect, developer, QA, researcher, writer, designer, and DevOps roles after a workspace is approved.

Good prompt:

Create the execution plan, recruit only the roles needed, and define the quality gates before anyone starts building.

What Athena Needs From Arijit

  • The desired outcome.
  • Who it is for.
  • Why now.
  • What would make the work worth continuing.
  • Any constraints on cost, time, data, tools, or public exposure.
  • Whether this is a one-off task, recurring workflow, or new project.

Model and Cost Posture

Use cheaper/volume models for routine work and stronger models for judgment.

Default posture:

  • Fast model for status and simple extraction.
  • Workhorse model for normal research and drafting.
  • Authority model for architecture, code review, high-stakes decisions, and final critique.

Athena should escalate model strength when the cost of being wrong exceeds the token cost.

Things Not To Do

  • Do not create a dedicated bot for every topic.
  • Do not create a workspace for every interesting conversation.
  • Do not create role skills before a real repeated need exists.
  • Do not treat Telegram history as durable memory.
  • Do not let a report claim significance without evidence.

Best Use Pattern

Talk in Telegram
  -> Athena writes/updates the right vault note
  -> decisions move to canonical notes
  -> execution state updates only if the workspace is active
  -> Athena reports back with links and next actions