Rendering v0 accepts simple Mermaid flowcharts. Other Mermaid families remain syntax-validation only.
Artifact Ops · Bounded review artifacts
Bounded diagrams and evidence reports
Turn one typed Context Pack into a deterministic Markdown or standalone HTML report, or render bounded Mermaid flowcharts as SVG, HTML, or PNG. Browser-local and response-only paths stay explicit; no screenshot service, arbitrary HTML, public file host, or artifact storage.
Exact contract
Small enough to trust
SVG: utilito-mermaid-renderer-v0-flowchart-svg · 0.1.0
PNG: utilito-mermaid-renderer-v1-flowchart-png · 0.2.0Source over 100,000 bytes fails with a typed error before rendering.
The SVG output contract is capped at 250,000 bytes before optional standalone HTML wrapping.
PNG is capped at 1,000,000 bytes, 10,000 pixels per side, and 2,000,000 pixels total.
Complexity is bounded and reported instead of silently truncated.
Elapsed render time is checked after rendering. This is a measured limit, not a hard process-interruption claim.
Examples include EMPTY_INPUT, UNSUPPORTED_EXPORT_FORMAT, NO_RENDERABLE_FLOWCHART_EDGES, NODE_LIMIT, OUTPUT_TOO_LARGE, and UNSAFE_SVG. The API contract publishes the exhaustive list.
Browser-local
Inspect and render without upload
The browser tool imports the shared SVG renderer directly and creates a browser-local PNG download without upload. Use it for sensitive one-off diagrams.
Open Mermaid Syntax Validator →HTTP API
One deterministic request
Call POST /api/run with tool_id: mermaid-renderer. Choose svg, html, or png; PNG returns base64 image/png bytes.
MCP
Use the compact router
Load the mermaid-renderer schema, then call run_tool. Artifact Ops does not add another top-level MCP tool.
Artifact Ops · Report families
Evidence reports and agent handoff reports from the same Context Pack
utilito.evidence-report.v1 · 1.0.0Context Ops prepares bounded machine context; Artifact Ops turns that exact pack and omission receipt into Markdown or standalone HTML for a human reviewer. The Agent handoff report preserves submitted state without a second model call and does not verify that submitted claims are true.
Share retained source IDs and exact submitted quotes alongside dedupe, omission, and byte receipts.
Preserve bounded failure neighborhoods and original line ranges. This is evidence, not root-cause analysis.
Show which records and fields reached model context instead of making an unsupported token-savings claim.
Carry goals, decisions, completed work, blockers, next actions, artifacts, and evidence into Agent/session continuation or human review without inferred state.
Review breaking drift, diagnostics, and unsafe retry state while raw argument values remain omitted.
Carry fixture identities, statuses, and issue codes without executing or grading submitted fixtures.
Preserve a metadata-only failed-run timeline without replay, provider calls, or inferred root cause.
Prioritize submitted deterministic findings without crawling a URL or claiming WCAG certification.
Render allowlisted recipe step identities as bounded SVG, HTML, or PNG documentation without executing the recipe or exposing argument values.
Review submitted patch file operations and conflicts without reading a repository, applying a patch, or retaining source text.
Carry bounded submitted log ranges and severity metadata without replay, monitoring, raw log retention, or inferred root cause.
Review format, profile, malformed-row, and rule-violation metadata without retaining rows, cells, or enum members.
Prioritize submitted header findings without fetching a URL, retaining header values, or claiming a security certification.
Review submitted manifest-diff or verification metadata without reading files, retaining digests, or claiming provenance or safety.
Download a stable text artifact for pull requests, issues, runbooks, or agent handoffs.
Download escaped, fixed-style HTML with no scripts, forms, remote resources, or arbitrary user markup.
No PDF, arbitrary HTML input, URL screenshot, public hosting, report storage, or generic rendering is included.
Boundaries
No artifact storage
Response-only
Generated SVG, HTML, and PNG artifacts are returned in the response. They are not stored or indefinitely retained by Artifact Ops.
Cache metadata is not storage
The response includes deterministic cacheability metadata and a cache key. That metadata is not evidence that an artifact was persisted.
No product measurement
Utilito does not collect product analytics. API and MCP responses emit no metrics response header. Raw source and generated output remain response-only.
One existing plan
Artifact Ops is a module in the Context Ops Builder Pilot, not a separate subscription. Free browser and light API/MCP access remain available.
Evidence before expansion
Request a named output format
Need PDF or another bounded export? Name the format and workflow. A real request can select a later export; it does not authorize a generic screenshot or storage platform.