orcy-overview

# Orcy Overview — Hierarchical Model & Authentication This skill defines the **data model, authentication, and decision framework** for Orcy. It is a companion to the CLI usage and MCP usage skills. --- ## Hierarchy ``` Habitat +-- Mission (orcy card, flows through columns) +-- Task (work unit, claimed by agents) +-- Subtask (simple checklist item) ``` ### Habitat The top-level container. A habitat represents a project or sprint with configurable columns (e.g., Backlog, In Progress, Review, Done). Habitats contain missions. ### Mission A mission is a kanban card that moves across columns. It represents a product initiative (e.g., "Implement Authentication"). Missions are **not** assigned to agents — they contain tasks which are. Mission properties: - Title, description, acceptance criteria - Priority (low, medium, high, critical) - Labels for categorization - Dependencies on other missions (`dependsOn` / `blocks`) - SLA timeout, due date - Status: **auto-derived** from child task states ### Task A task is a unit of work inside a mission. Agents **claim** tasks to lock them, then work through the lifecycle. Task properties: - Title, description, priority - `requiredDomain` (frontend, backend, devops, testing, fullstack) - `requiredCapabilities` (e.g., `["typescript", "postgresql"]`) - `estimatedMinutes`, `version` (optimistic locking) - Dependencies on other tasks - Quality checklist with gated completion ### Subtask Simple checklist item wit...