> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_40/session_14_ministry_builder_and_pantheon.md). # Session 14: Ministry Builder And Pantheon **Session ID**: `phase40-session14-ministry-builder-and-pantheon` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Add the Ministry builder to the current Hermes Pantheon without regressing existing persona workflows. *** ## Scope ### In Scope (MVP) * Add Ministry components under `src/components/hermes/ministry/` for the card, model palette, council seats, analytics shell, save/copy shell, and vendor logo rendering. * Integrate Ministry into `hermes-pantheon` as the first card or a clearly related full-width Pantheon section. * Keep existing persona create, edit, delete, install, validation, and Pantheon grid behavior intact. * Implement pointer and keyboard-friendly seat assignment: drag to seat, click model then click seat, Escape to cancel armed model, remove seat, enforce max expert count, avoid duplicate core/expert, and reset to recommended lineup. * Keep layout consistent with AI OS Hermes panels and avoid decorative nested cards. ### Out of Scope * Direct MoA save wiring. * Final analytics and pricing behavior. * Regressing or replacing existing persona workflows. *** ## Prerequisites * [ ] Session 09 model rows are available. * [ ] Session 10 has validated the staged provider logos and optimized `src/assets/ministry-hero.webp` copy, or placeholders match asset policy. *** ## Deliverables 1. Ministry builder UI integrated into Pantheon. 2. Vendor logo usage wired to compliant assets. 3. Tests for open/close, seat assignment, duplicate prevention, max experts, reset, existing persona workflow preservation, and mobile layout stability. *** ## Success Criteria * [ ] Pantheon gains Ministry without breaking existing persona workflows. * [ ] Seat assignment works with pointer and keyboard-friendly flows. * [ ] Builder layout remains usable on mobile and desktop. * [ ] No card is nested inside another card solely for decoration. *** ## Folded Source Session Split The section below preserves the original Phase 40 session split detail for this session, including dependencies, decisions, outputs, and acceptance checks. ### Session 14: Ministry Builder And Pantheon **Objective**: Add the Ministry builder to the current Hermes Pantheon without regressing existing persona workflows. **Scope**: * Add Ministry components under `src/components/hermes/ministry/` for the card, model palette, council seats, analytics shell, save/copy shell, and vendor logo rendering. * Integrate Ministry into `hermes-pantheon` as the first card or a clearly related full-width Pantheon section. * Keep existing persona create, edit, delete, install, validation, and Pantheon grid behavior intact. * Implement pointer and keyboard-friendly seat assignment: drag to seat, click model then click seat, Escape to cancel armed model, remove seat, enforce max expert count, avoid duplicate core/expert, and reset to recommended lineup. * Keep layout consistent with AI OS Hermes panels and avoid decorative nested cards. **Outputs**: * Ministry builder UI integrated into Pantheon. * Vendor logo usage wired to the validated Session 10 assets, with duplicate logo paths avoided. * Tests for open/close, seat assignment, duplicate prevention, max experts, reset, existing persona workflow preservation, and mobile layout stability. **Dependencies / Notes**: * Depends on Sessions 09 and 10. * Session 15 adds config generation, analytics completion, and direct save UX. **Acceptance Checks**: * Pantheon gains Ministry without breaking existing persona workflows. * Seat assignment works with pointer and keyboard-friendly flows. * Builder layout remains usable on mobile and desktop. * No card is nested inside another card solely for decoration. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_40/session_14_ministry_builder_and_pantheon.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.