Dashboard/My OS
Project

My OS

Vault: myos   Path: My OS

index.md

My OS

My OS is the company operating system for Arijit's work.

There is one OS. Do not split this into Work OS, Company OS, Founder OS, or separate "OS" brands unless Arijit explicitly decides to create a new company/system.

The Model

Arijit
  founder, owner, final decision-maker

My OS
  company operating system: governance, memory, workspaces, decisions, and team model

Athena
  CEO agent and strategic mind of My OS

Athena's ELT
  company-level advisory council available to critique, expand, and remember ideas

Project workspaces
  durable rooms for individual products, companies, research programs, or operating workflows

Workspace execution teams
  role-based project teams recruited by Athena based on the work required

Runtime Implementation

Chowmes
  host/runtime environment for Athena and Hermes

Hermes
  agent platform running inside Chowmes

Obsidian / MyOS vault
  durable source of truth

Telegram
  interface for Arijit and Athena

Core Operating Flow

  1. Arijit and Athena brainstorm an idea, problem, company, product, or initiative.
  2. Athena turns the conversation into a short project overview.
  3. Athena brings the overview to the company-level ELT for multi-angle critique.
  4. The ELT expands the idea into business, product, technical, financial, market, and launch implications.
  5. Athena synthesizes the expanded plan and brings it back to Arijit.
  6. Arijit and Athena review, challenge, simplify, and approve or reject the plan.
  7. If approved, Athena creates or updates the project workspace.
  8. Athena recruits the execution roles the workspace actually needs.
  9. The workspace team executes, writes durable state, and reports back through Athena.

Important Separation

The ELT does not get copied into every workspace as a fake mini-corporation.

The ELT is a company-level advisory council available to Arijit and Athena. Some ELT roles are now live Hermes profiles because they need independent memory, evolving judgment, long-running dialogue, or recurring advisory work across projects: Vulcan (vulcan) for CTO, Arjuna (arjuna) for Product / UX Strategy, Kubera (kubera) for Revenue / Business, and Prometheus (prometheus) for Legal / Risk. Project workspaces still get execution roles only: PM, architect, developer, QA, researcher, analyst, writer, designer, DevOps, sales enablement, or other specialists as needed.

This preserves persistent executive minds without turning every project into a fake miniature corporation.

What Belongs Here

  • My OS structure and rules.
  • Athena's CEO operating model.
  • ELT roles and decision rights.
  • Workspace lifecycle and activation criteria.
  • Role library and skill map.
  • Cross-project decision log.
  • Vault migration notes.

What Does Not Belong Here

  • Deep execution details for PRISM, CurioQuest, Competitive Intelligence, or other projects.
  • Chowmes/Hermes infrastructure details except where they affect the My OS operating model.
  • Raw Telegram transcripts except as linked evidence.
  • Runtime troubleshooting logs except when they affect the My OS model.
  • A full .company/ state folder unless My OS itself becomes an active build project.

Canonical Notes

Legacy Material

Old WorkOS, Company-OS, Founder-OS, and ArijitOS-style notes were consolidated on 2026-06-18.

Live work should use this project only. No archive is kept for the old duplicate OS structures; useful material was merged into canonical My OS notes and project-specific notes.

Current System Lanes

Lane Purpose Status
MyOS-Core Primary Hermes instance for Athena, ELT profiles, operating memory, Argus, and company-level orchestration Canonical
Chowmes Server and DNS/service umbrella: Docker, networking, permissions, health checks Active host
Competitive Intelligence MyOS-Core function: public-source CI engine, Algolia pack first, generic CI OS later Active function
Content Engine Content strategy, creation, repurposing, publishing Proposed
PRISM Independent Hermes and webapp External system
CurioQuest Personalized curriculum-aligned STEM story/activity book product External system for now
Scout Browser-capture/service surface External service

Anti-Overengineering Rules

  1. Add structure only when it makes work easier to run, remember, or repeat.
  2. Start with an idea note before creating a workspace.
  3. Start with a role card before creating a live Hermes profile.
  4. Create a live Hermes profile when persistent role memory, evolving judgment, recurring advisory work, distinct tools, distinct permissions, scheduled work, or separate artifacts justify it.
  5. Start with a workspace before creating a workspace-specific execution profile.
  6. Start with a Hermes profile before creating a dedicated Telegram bot.
  7. Do not create .company/ execution state for passive ideas.
  8. Do not give every workspace its own C-suite.
  9. Keep raw transcripts as evidence, not as the default operating context.
  10. If a layer creates more management work than execution clarity, collapse it.

Success Standard

My OS is working when Athena can:

  • Understand which workspace a task belongs to.
  • Decide whether an idea deserves a project workspace.
  • Bring the right ELT perspectives to planning.
  • Recruit the right execution roles for a workspace.
  • Keep durable decisions out of scattered Telegram threads.
  • Report status to Arijit without flooding him with raw agent output.

All files (28)