Markdown in. An interactive page out.
Declarative pages for agent handoffs
Turn declarative Markdown into a finished interactive page an agent can hand to a human—locally, with one build command and no frontend project.
npx --yes agentic-report init ./my-page --starter landing --json
Fictional sample · built by agentic-report from the repository source.
Single HTML by default
Choose a content-addressed directory artifact when the page is large.
Opens directly through file://
The package-owned browser runtime is included and required for normal interactive output.
No author JSX, JS, or CSS
Authors use Markdown, frontmatter, confined Markdown partials, and local assets.
One source. A finished artifact.
The source on the left is a verbatim excerpt from the fictional launch example. The view on the right is an actual local build of that same source, not a design mockup or a second private renderer.
Verbatim declarative source
---
contractVersion: 1
title: Regional beta launch readiness
description: A fictional launch decision combining audience value, activation evidence, operational gates, and a reversible rollout.
language: en
theme: light
layout: landing
preset: studio
tokens:
accent: teal
---
# Regional beta launch readiness
**Fictional showcase · 19 August 2026 · conditional go**Compiled result
The same compiler adds accessible navigation, interactive components, local assets, and its packaged browser runtime.
npx --yes agentic-report build ./website/landing --output ./site/index.html --jsonFrom empty folder to reviewable page.
Use Node.js 24.18.0 or newer. The first npx run needs registry and network access so npm can retrieve the
package; compilation and the generated page then run locally.
First useful result
- Initialize with
npx --yes agentic-report init ./my-page --starter landing --json. - Edit the generated declarative Markdown and add only confined partials or local assets.
- Run
npx --yes agentic-report validate ./my-page --jsonandnpx --yes agentic-report inspect ./my-page --json. - Run
npx --yes agentic-report build ./my-page --output ./my-page.html --json, then open the result throughfile://.
Realistic pages, not toy cards.
Each example is a separate publishable page compiled from public declarative source. Every organization, person, event, metric, and decision is fictional sample data.
OrbitDesk P1 incident review
Fictional sample. Reconstruct a 47-minute checkout incident from the failure curve, causal diagram, evidence tabs, response timeline, and accountable action register.
What to try: switch the Evidence and limits tabs, then open the customer communication disclosure.
AI support vendor decision
Fictional sample. Separate non-negotiable procurement gates from weighted preference and inspect why the highest-scoring candidate is not eligible.
What to try: open the ranking explanation and the reviewer evidence checklist.
Regional beta launch readiness
Fictional sample. Judge a bounded beta from activation, retention, operational gates, a hold condition, and a reversible rollout.
What to try: switch the audience tabs and reveal the automatic hold condition.
Built for handoff, across seven page types.
Report
Turn findings, evidence, decisions, and owned follow-up into a reviewable handoff. Start with report.
Research
Present method, competing evidence, confidence, and a bounded recommendation. Start with research.
Architecture
Explain system boundaries, alternatives, trade-offs, and a rollout. Start with architecture.
Tutorial
Guide a reader through ordered steps, code, progressive detail, and bounded practice. Start with tutorial.
Dashboard
Make operating signals, charts, filters, thresholds, and exceptions easy to scan. Start with dashboard.
Decision
Separate gates, evidence, alternatives, conditions, and reversibility. Use the existing report or
architecture starter; the fictional vendor decision is the proof,
not a made-up seventh starter.
Landing
Build a restrained proof-first product or project page with the same public engine. Start with landing.
This site is one of the outputs.
The public site uses the same section, navigation, preset, action, local-asset, and restrained-motion contracts as every other page. There is no landing-only renderer, hidden theme, author stylesheet, or post-build DOM patch.
Build proof
npx --yes agentic-report build ./website/landing --output ./site/index.html --jsonRead the complete source · Open the landing starter · Release identity
Ordinary engine features
- eight semantic sections derived into navigation;
- the reusable
studiopreset and responsive content tracks; - ordinary safe action links and local screenshots;
- one optional progress line and three bounded one-time reveals.
Know what it does—and what it doesn’t.
Included
- a local declarative compiler;
- confined Markdown, partials, and local assets;
- deterministic validate, inspect, and build commands with structured JSON output;
- a required package-owned interactive runtime;
- single-file output by default and optional directory output.
Not included
- a hosted editor, backend, or collaboration service;
- deployment or account management;
- arbitrary author HTML, JSX, CSS, or browser JavaScript;
- remote source, asset, script, font, or style fetching;
- print or disabled-JavaScript parity.
For humans and agents.
Human guide
Start with the page you need, then follow task-oriented commands and examples.
Agent guide
Retrieve concise Markdown directly with an ordinary file or HTTP request—no checkout, authentication, or browser JavaScript required.
Source contract and skill
Use the closed authoring reference and canonical skill without downloading a documentation application.
agentic-report --help, validate --json, and inspect --json remain the local executable truth.
Build the page your agent needs to hand off.
Use Node.js 24.18.0 or newer. The first zero-install run retrieves the package from the npm registry.
npx --yes agentic-report init ./my-page --starter landing --jsonNo signup, hosted project, or telemetry promise is required to produce the local artifact. ::::