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. Packages without a link do not have a documentation page yet.
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 the shared UI components (the own kit with the shadcn/ui look) 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. |
mortelos/document-studio |
Workspace package | You need document collections, structured registers and multi-approver sign-off packages. |
mortelos/daily-planner |
Workspace package | You need a per-user planner page with a backlog, a time-boxed day timeline and morning and evening rituals. |
mortelos/feedback |
Workspace package | You need signed-in users to report bugs, suggestions and questions from any page, delivered through a MortelOS channel. |
mortelos/policy-studio |
Workspace package | You need chat-driven access change proposals with admin approval, a governance overview widget and admin pages for grants, conditions and agent approvals. |
mortelos/record |
Workspace package | You need one record page per entity, built from declarative layouts that the framework, packages and the host app contribute to. |
mortelos/triage |
Workspace package | You need building blocks for a mail triage loop: one judgement per thread, a doubt check and a receipt for every decision. |
mortelos/booking |
Workspace package | You need personal appointment links with open times, booking questions, an embeddable public booking form and bookings in the owner's calendar. |
mortelos/sidecar |
Workspace package | You need heavy chat questions handed to Claude Code on the asking user's own Claude account, in a closed sandbox. |
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-github |
GitHub | You need GitHub pull requests in the inbox through a GitHub App, with approval-bound documentation publication and explicit merge or close decisions. |
mortelos/channel-gmail |
Gmail | You need Gmail channel access for workspace communication or ingestion flows. |
mortelos/channel-google-calendar |
Google Calendar | You need per-user Google Calendar access to read upcoming events through Google OAuth. |
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-pocket |
You need Pocket conversation recordings stored as meeting entities with transcript, summary and action items. | |
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. |
mortelos/issue-factory |
Development tooling | You need issue dossiers, a ready queue and lifecycle commands for an agent-driven TDD build loop. |
Internal Repositories
The registry serves exactly the packages on this page. Two other Composer projects in the MortelOS organization are internal: no host app installs them, so they are neither listed here nor served by the registry.
| Repository | Why it is not listed |
|---|---|
mortelos/package-registry |
It builds the private Composer registry that distributes the packages on this page. |
mortelos/site |
It runs the public website and renders this documentation. |
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.
A host never changes a package to make it fit. Every package lists its outlets in resources/mortelos/outlets.json: the contracts, registries, events, config files and view outlets your app can plug into. Each package page has an Outlets section with that list, and Outlets explains what to do when none fits.
Package pages should describe stable contracts, not tenant-specific implementation details. Planned package names stay out of this index until source is available.
Installing A Package
Every package on this page is distributed from the private Composer registry at https://packages.mortelos.com. Configure registry access once per machine, then install a package by name:
composer require mortelos/chat
Host apps depend on version ranges ("mortelos/chat": "^0.3") and commit composer.lock, so an install is reproducible and a package upgrade is a deliberate composer update mortelos/chat. See Installation for the credential and repository entry.
Each package has its own Git repository; check them out as siblings in one workspace directory while developing. To try a local change against a host app, symlink the checkout into vendor/ after installing — never add a path repository to the committed composer.json. Host-local packages/ folders are temporary test scaffolding, not canonical package source.