# Lore

> An open-source project management app built on Alepha. Quests, folios, feedback and crash telemetry, readable and writable over MCP.

## Guides

- [Lore, every page in one file](https://latest.alepha.dev/lore/llms-full.txt): 23 pages, ~60k tokens.
- [Introduction](https://latest.alepha.dev/lore/docs/guides-introduction.md): Lore is an open-source project management app built on Alepha.
- [Getting started](https://latest.alepha.dev/lore/docs/guides-getting-started.md): This page takes you from no account to a project with members, the lore command on your machine and an AI agent connected over MCP, then files a first quest.
- [Quests](https://latest.alepha.dev/lore/docs/guides-quests.md): A quest is one piece of work in a Lore project: a bug to fix, a feature to build, a chore to do.
- [Epics](https://latest.alepha.dev/lore/docs/guides-epics.md): An epic is a bounded initiative: it spans several areas, owns quests and folios, and ends.
- [Releases](https://latest.alepha.dev/lore/docs/guides-releases.md): A release is a named goal that holds the work due to ship in it: 0.28.0, demo-1, v1.0.0-rc.1.
- [The project dashboard](https://latest.alepha.dev/lore/docs/guides-project-dashboard.md): Every project has a Dashboard, and it is what you land on when you open the project.
- [Folios](https://latest.alepha.dev/lore/docs/guides-folios.md): Folios are a project's memory: Markdown notes, filed in a tree, linked to each other and to the work, and shared by every member and every agent of the project.
- [Attachments](https://latest.alepha.dev/lore/docs/guides-attachments.md): A quest or a folio can carry files: a screenshot, a probe log, a CSV of measurements, an HTML mockup someone will open.
- [Feedback](https://latest.alepha.dev/lore/docs/guides-feedback.md): Feedback is how people outside a project's team report a bug or ask for a feature.
- [Notifications](https://latest.alepha.dev/lore/docs/guides-notifications.md): Lore tells you about things addressed to you in two places: an in-app inbox behind the bell, and email.
- [Agent prompts](https://latest.alepha.dev/lore/docs/guides-agent-prompts.md): Every surface that names a piece of work can hand it to a coding agent.
- [Automations](https://latest.alepha.dev/lore/docs/guides-automations.md): An automation is a saved, deterministic rule: when something happens, or a UTC schedule is due, Lore selects authorized data, tests a condition and performs an ordered list of actions.
- [MCP tools](https://latest.alepha.dev/lore/docs/guides-mcp.md): Lore's primary consumer is an AI agent, and MCP is how it reaches a project. This page lists every tool, says how they address things and what they share, and names what has no tool on purpose.
- [The lore CLI](https://latest.alepha.dev/lore/docs/guides-cli.md): lore is the command-line client for Lore: it signs in to an instance, reads and writes quests and folios, and builds, pushes and deploys apps from a laptop or a CI job.
- [Telemetry](https://latest.alepha.dev/lore/docs/guides-telemetry.md): Lore watches the apps a project runs: page views, Web Vitals and errors, each reported by the app itself with a key called a sigil.
- [Healthchecks](https://latest.alepha.dev/lore/docs/guides-healthchecks.md): A healthcheck asks from outside whether something is up: a website, a port, a TLS certificate, or a scheduled job that should have reported in.
- [Deploying an app](https://latest.alepha.dev/lore/docs/guides-deploying.md): Lore can deploy your app for you. You lend it a machine running Bay or a Cloudflare account, tell it which copies of your app exist, and then shipping is one command or one button.
- [Pushing artifacts](https://latest.alepha.dev/lore/docs/guides-artifacts.md): An artifact is a build your CI hands to Lore and keeps. It is what the Artifacts page lists, what a release attaches, and what a deploy ships.
- [Stacks](https://latest.alepha.dev/lore/docs/guides-stacks.md): A stack is a group of apps and services deployed together from one compose.yml onto a Bay estate.
- [Estates](https://latest.alepha.dev/lore/docs/guides-estates.md): An estate is a place Lore deploys to: a machine running Bay, or a Cloudflare account.
- [The Cloudflare token](https://latest.alepha.dev/lore/docs/guides-cloudflare-token.md): A Cloudflare estate is a deploy destination Lore reaches over Cloudflare's API.
- [Self-Hosting](https://latest.alepha.dev/lore/docs/guides-self-hosting.md): That is the whole thing. No environment variables, no migration step, no seed command.
- [Reports](https://latest.alepha.dev/lore/docs/guides-reports.md): Reports is what happened in a project over a period, measured. The dashboard is a board you compose; Reports is fixed, and every figure says what it counts behind an info mark.

## Optional

- [Alepha](https://latest.alepha.dev/llms.txt): The TypeScript framework Lore is built on, and its documentation index.