Decision: Workspace-Owned Skills

Decision

Project-specific skills should live under the workspace that owns the work.

For the Competitive Intelligence pilot, the canonical executable skill now lives at:

/opt/data/knowledge/obsidian/MyOS/Projects/Competitive Intelligence/skills/competitive-research

Its artifacts and SQLite ledger live at:

/opt/data/knowledge/obsidian/MyOS/Projects/Competitive Intelligence/artifacts/competitive-research

Hermes keeps compatibility links only where needed for discovery or legacy path expectations:

/opt/data/skills/competitive-research
/opt/data/workspace/skills/competitive-research
/opt/data/workspace/Knowledge/competitive-research

Cron wrappers stay in /opt/data/scripts/ because Hermes cron resolves scripts from that runtime path, but those wrappers call the workspace-owned skill directly.

Rationale

A cron job should not dictate the architecture. If a skill belongs to a project, the source, artifacts, quality rules, and roadmap should sit with that project workspace. Hermes/Chowmes is the operator and delivery layer, not the owner of every project-specific skill.

This keeps the model consistent:

• Athena coordinates the company.
• Workspaces own durable project context and execution assets.
• Runtime paths provide delivery, scheduling, permissions, and compatibility.

Guardrail

Do not keep duplicate executable copies under Chowmes. If Hermes needs a runtime path, use a wrapper or symlink that points back to the workspace-owned source.

Applied First

Competitive Intelligence is the first MyOS-Core test case. PRISM and CurioQuest should not follow this as MyOS-Core workspaces unless Arijit explicitly moves them back inside MyOS-Core; for now they are external systems/products.