| Role-based operators | cap-role-based-operators | Role-based operators | Hermit Website Lead | active | Hermit can grow from one focused operator into a multi-role organization when the work needs different lenses | People shaping repeatable operational workflows | Roles are explicit, file-backed operators with their own prompts, standards, inbox, and record. | Each role has its own role.md, AGENTS.md, prompts, and agent operating files., Bootstrap guidance starts with one sharp role and only splits when a genuinely different lens is needed., The runtime can switch active chat roles instead of mixing incompatible responsibilities. |
| Local-first runtime | cap-local-first-runtime | Local-first runtime | Hermit Website Lead | active | Hermit runs against your local workspace so the files stay canonical and the tooling remains close to the work | Developers who care about control, privacy, and inspectability | The runtime treats the local repo as the source of truth and prefers file operations, local prompts, and local artifacts over opaque remote state. | The agent reads and writes workspace files directly., The runtime is designed to run inside a sandboxed local environment by default., Git history remains the durable change log for system evolution. |
| Files are the app | cap-files-are-the-app | Files are the app | Hermit Website Lead | active | Hermit keeps prompts, records, workflows, and UI in one repo instead of hiding state behind a separate backend | Builders who want inspectable, local-first systems | The repo is the application: data, behavior, UI, and operating state live together as files with git history. | The workspace stores roles, prompts, skills, entities, and agent state directly on disk., Entity definitions and templates declare the schema in markdown under entity-defs/., The Astro explorer renders the same workspace the CLI and agents use. |
| Explorer-to-website evolution | cap-explorer-to-website | Explorer-to-website evolution | Hermit Website Lead | active | Hermit's read-only explorer can be reshaped into a hosted website or domain-specific front end through records and renderers | Teams that want the UI to evolve with the workspace model | The explorer is intentionally simple by default, but it can gain custom renderers, tailored landing pages, and domain-specific presentation without abandoning the file-first model. | Explorer rendering can be customized through entity-defs renderers., The homepage and shell can be adjusted while still reading from the same workspace., This bootstrap sets up site, page, and capability records specifically for that evolution. |