Version 0
Package Overview
Reference index for public MortelOS packages.
MortelOS follows the same documentation shape as Laravel: packages have their own navigation section, and every installable package gets a focused page. This page is the index.
Start with mortelos/starter, then add the package that matches the portal surface, integration channel or widget you need.
Foundation
| Package | Type | Use when |
|---|---|---|
mortelos/starter |
Host app template | You need a new Laravel portal host with shell routes, auth baseline, dashboard, inbox, governance, users, settings and diagnostics. |
mortelos/app-standards |
Host runtime defaults | You need MortelOS-owned Laravel defaults for a concrete host app. |
mortelos/framework |
Core library | You need MortelOS primitives: entities, links, events, projections, tenant primitives, access resolution, MCP runtime and reusable application services. |
mortelos/ui |
UI library | You need shared Flux-aligned UI primitives for a host app or reusable package surface. |
Capability Surfaces
| Package | Type | Use when |
|---|---|---|
mortelos/chat |
Workspace package | You need the tenant-gated chat workspace, conversation panel and chat widget registry. |
mortelos/overviews |
Workspace package | You need reusable flexible overviews with datasource wiring, save-flow behavior, chat widget support and agent tools. |
mortelos/entity-graph |
Workspace package | You need entity graph traversal, API routes, visualization, search, path-finding, chat widget support and agent tooling. |
mortelos/mail |
Workspace package | You need reusable mail read models, indexing and search context for communication workflows. |
Channels
Channel packages connect MortelOS to external systems. Install them only when the portal needs that integration.
| Package | External system | Use when |
|---|---|---|
mortelos/channel-fireflies |
Fireflies | You need inbound webhook handling and transcript ingest from Fireflies. |
mortelos/channel-gmail |
Gmail | You need Gmail channel access for workspace communication or ingestion flows. |
mortelos/channel-google-drive |
Google Drive | You need Drive delivery for attachments, briefings or exported workspace material. |
mortelos/channel-moneybird |
Moneybird | You need scheduled invoice and contact sync from Moneybird. |
mortelos/channel-plaud |
Plaud | You need Plaud channel ingestion for recorded or transcribed source material. |
mortelos/channel-telegram |
Telegram | You need bidirectional Telegram Bot API communication. |
Widgets
Widget packages add focused chat or workspace UI on top of the foundation packages.
| Package | Type | Use when |
|---|---|---|
mortelos/widget-compliance |
Chat widget package | You need compliance-focused chat widgets inside a MortelOS workspace. |
mortelos/widget-document-feedback |
Chat widget package | You need document feedback flows inside the MortelOS chat surface. |
Tooling
These packages support development and governance. They are not feature packages for every portal.
| Package | Type | Use when |
|---|---|---|
mortelos/dev-tools |
Development tooling | You need Artisan commands for package decisions, governance checks and package-ready feature workflow support. |
mortelos/agent-standards |
Agent instructions | You need shared AI agent rules merged into host AGENTS.md files. |
Package Boundaries
Use mortelos/starter for the host, mortelos/app-standards for concrete host runtime defaults, mortelos/framework for core primitives, mortelos/ui for shared interface primitives and dedicated packages for reusable capabilities. Keep tenant-specific branding, policy defaults, local orchestration and one-off integrations in the host until they can serve more than one installation.
Package pages should describe stable contracts, not tenant-specific implementation details. Planned package names stay out of this index until source is available.
Use sibling local repositories as package sources while developing: ~/Sites/mortelos-* for MortelOS packages, ~/Sites/channel-* for channel packages and ~/Sites/widget-* for widget packages. Host-local packages/ folders are temporary test scaffolding, not canonical package source.