📊 Report
Hybrid entities: D1 metadata for indexing + static HTML for rich content. Published via the
create-report skill.
Schema
D1 reports table
Metadata registry. The actual content lives in static HTML files.
idTEXT PK — UUID
titleTEXT — Report title
slugTEXT UNIQUE — URL slug (e.g.
entity-architecture)
descriptionTEXT — Short
description for index listing
workspaceTEXT — agentic | dev |
work | life
typeTEXT — normal | slide
statusTEXT — Active |
archived
task_idTEXT — Linked task
(optional)
tagsTEXT — Comma-separated
tags
created_atTEXT — ISO
timestamp
updated_atTEXT — ISO
timestamp
How Reports Work
Hybrid model: D1 stores metadata (title, slug, description, tags). The actual report content
is a self-contained HTML file at
/reports/{slug}/index.html. This lets reports be rich
interactive pages while remaining queryable via API.
Two Modes
| Type | Description | Example |
|---|---|---|
normal |
Article-style report with sections, tables, charts | Entity Architecture |
slide |
Slide deck format with navigation buttons | Capability presentations |
Publishing Flow
Agent creates HTML
→
Save to
public/reports/{slug}/
→
POST to /api/reports
→
Deploy portal
The create-report skill automates this: it generates the HTML, creates the D1 record, and
deploys in one step.
API
| Method | Endpoint | Description |
|---|---|---|
GET |
/api/reports |
List. Filter: ?status=Active, ?workspace=agentic |
POST |
/api/reports |
Create metadata. Body: { title, slug, description, type, workspace } |
PATCH |
/api/reports?id=xxx |
Update fields. { status: "archived" } |
Design Decisions
Clara archives linked reports: When archiving a task, Clara also PATCHes any linked report to
status: archived. This prevents stale reports staying "Active" indefinitely.
Self-contained HTML: Reports use inline CSS (no external dependencies). They match the
portal's dark theme (Inter font, indigo accent, card-based layouts). This means reports work even if the
portal CSS changes.