My OS

03-workspace-lifecycle.md

Workspace Lifecycle

Workspaces are durable rooms for work. They are not decorative folders.

As of 2026-06-29, MyOS-Core is the primary Hermes instance. PRISM and CurioQuest are external systems/products, not MyOS-Core workspaces. Do not treat their reference folders as active internal execution rooms unless Arijit explicitly changes the boundary.

Lifecycle Stages

Stage Meaning Required Artifact
Idea Interesting but not yet structured Idea note
Brief Problem, audience, outcome, constraints are named Project overview
ELT review Company-level critique has happened ELT critique note
Approved Arijit and Athena agree to proceed Decision note
Active workspace Durable context and artifacts are needed Workspace index.md
Execution Team is recruited and work is running Tasks/status/logs
Review Output is being tested, validated, or judged QA/review evidence
Dormant No active work, but worth preserving Status note
Archived Not active and not expected to resume soon Archive note

Workspace Folder Pattern

Use this only when a workspace is active enough to deserve it.

Projects/{Workspace Name}/
  index.md
  decisions/
  logs/
  wiki/
  artifacts/
  raw/
  .company/              # only for active execution work

State Rule

Markdown explains the work. .company/ state runs the work.

Do not create .company/ folders for every idea. Create them only when tasks, agents, quality gates, or recurring execution need structured state.

Dedicated Bot Rule

A dedicated Telegram bot is justified only when the workspace needs one or more of:

  • Separate system prompt.
  • Separate memory profile.
  • Separate permission model.
  • Separate cadence or scheduled delivery.
  • High-frequency interaction that would pollute My OS HQ.
  • Different audience or artifact destination.

Default progression:

idea note -> workspace -> Hermes profile -> Telegram bot

Workspace Closure Rule

Every workspace should have a status:

  • Active.
  • Proposed.
  • Dormant.
  • Archived.

If no one can name the next action, owner, or reason to keep context warm, the workspace is dormant.