Events

Every Laravel event LaRecipe dispatches. LaRecipe stores no traffic and no feedback: your app listens and forwards. For what to do with them, see analytics and events.

use Illuminate\Support\Facades\Event;
use LaRecipe\Domains\Delivery\Events\PageViewed;

Event::listen(function (PageViewed $event) {
    // $event->set, $event->page->path, $event->format, $event->kind
});

Traffic events live in LaRecipe\Domains\Delivery\Events, content events in LaRecipe\Domains\Sources\Events. Each payload table below is read from this app by an <Event> live reference, with this app's listeners (only ContentChanged has one: LaRecipe's cache warmer).

The request kind

Traffic events carry a kind: human, crawler or agent. The first rule that matches decides it:

llms.txt, llms-full.txt, skill.md, hand-written skill files, the skills index and the /ask endpoint exist for agents, so a fetch of them that does not ask for HTML counts as agent unless its user agent names a crawler. MCP calls are always agent. The kind feeds events only: it never changes what is served.

Traffic events

PageViewed

Fires for every page served as HTML, as Markdown or as the JSON the reader UI fetches when it navigates (format is html, markdown or json), after access checks pass. A missing page, or one the reader may not see, fires nothing.

MarkdownServed

Fires next to PageViewed when the page's Markdown twin is served. explicit is true for a .md URL and false for Accept: text/markdown.

LlmsTxtServed

Fires when an llms.txt index or an llms-full.txt file is served. file says which, and group is set for a file split by navigation group.

SkillServed

Fires when skill.md, a file of a hand-written skill or /.well-known/agent-skills/index.json is served. set and skill are null for the index, which covers every set.

McpToolCalled

Fires for every tool call on a set's web MCP endpoint or on the local server (transport is web or local). arguments holds the scalar arguments, with values longer than 200 characters shortened. Ask AI's own tool calls do not fire it.

SearchPerformed

Fires for every search, with its source:

The palette reports its searches in small batches to POST {prefix}/_search/report (with the locale and version in front for other scopes). Only a settled query counts, not each keystroke. The route is rate limited to 30 reports a minute per reader and stores nothing. A static export leaves the reporting out. The counts come from the browser: treat them as analytics, never as a security signal.

zeroResults marks the searches your docs could not answer.

FeedbackSubmitted

Fires when a reader answers "Was this page helpful?" (source is reader), when a reader gives an Ask AI answer a thumbs up or down (ask, with the question the answer was for, and the page the reader asked from), or when an agent calls the MCP submit_feedback tool (agent). LaRecipe keeps nothing: forward it.

AskAiAnswered

Fires when Ask AI finishes an answer. covered is false when the assistant said the docs do not cover the question, citations lists the page URLs it cited, and the token counts come from the provider.

PageRendered

Fires when LaRecipe renders a page, for work that should follow a render. format is html when the article was rendered because the render cache did not have it (a changed page, a cold cache, or larecipe:optimize); a cached answer fires nothing. format is markdown on every request for a Markdown twin, which is not cached. It carries the page and its content hash, never the reader: count readers with PageViewed. The MCP read_page tool and llms-full.txt do not fire it.

Content events

Content events fire when a change goes through LaRecipe's write path: the MCP author tools, the admin UI, larecipe:sync, a docs migration, larecipe:source:import or larecipe:source:move. Editing a Markdown file in your editor fires nothing.

PageWritten

Fires when a page is written, moved or deleted, live or as a draft, and when a docs migration's change to a page is held as a conflict. The revision says which, by whom and through which channel.

DraftCreated

Fires when a change waits for review: under review: required for a change an agent made outside a pull request, or when a draft was asked for.

DraftPublished

Fires when a reviewer publishes a draft or resolves a conflict by taking the migration, at the pass in the admin UI.

DraftRejected

Fires when a reviewer rejects a draft, with their reason, or resolves a conflict by keeping production, at the pass in the admin UI.

ContentChanged

Fires when a set's live content changes: a published change to a page, the navigation or the manifest (docs migrations included), an asset upload or deletion, an import, a source move or a docs migration rollback. pages lists the pages that changed, when known. LaRecipe listens to it itself, with a queued listener that warms the set's cache.

DocsMigrationConflicted

Fires when a docs migration finds that production changed since the migration was written. It does not overwrite: its version waits as a conflict draft next to production's, and the deploy carries on.

Next

• Analytics: forward these events to your own tools.
• Agent surfaces: the files agents fetch.