Design review · active default

The new default artifact template

Chris's clean-document system, adapted into a complete Artifact Studio page with responsive diagrams, evidence, actions, and review controls.

Bottom line

Implemented: this restrained, bottom-line-first document system now replaces the warm editorial scaffold as the default.

The previous scaffold is archived. The standalone bundled mode remains separate. Existing artifacts, IA rules, privacy checks, hosting, and diagram ownership do not change.

What changes

SurfaceDecisionReason
Current scaffold Archive Its oversized hero, step selector, sticky inspector, pill button, and studio footer are too product-like for the new default.
Clean document Default It starts with the bottom line, uses restrained typography and rules, and keeps evidence and action in one readable document.
Standalone bundle Keep It is a one-file packaging method, not a competing visual default.

The missing diagram treatment

Chris's document specified the report system. Artifact Studio still needs a governed way to carry relationships that prose or a table cannot explain efficiently.

How does a source-backed idea become a reviewable artifact?

The IA contract passes first. The clean document then renders the verdict, evidence, and a tool-diagrams-owned figure. Finally, the human keeps it or names the exact change.
The diagram is an embedded evidence form, not decoration. `tool-diagrams` owns its source and render; the document owns its placement, caption, and text equivalent.
  1. The IA contract fixes claims, scope, and the representation before visual work starts.
  2. The clean-document shell presents the verdict, evidence, and selected figure.
  3. The reviewer keeps the result or names the exact change required.

The reusable system

PartDefault behaviorWhen it earns its place
Verdict A bordered bottom-line box near the top. When the reader needs truth, meaning, and next action immediately.
Evidence Semantic tables, notes, exact labels, and tabular numbers. When precision or comparison would otherwise require mental joins.
Diagram Local responsive render, caption, text equivalent, and safe source copy. Only when a relationship is easier to understand visually.
Action A leverage-ordered list and one small review control. When the artifact changes a decision or next move.
Audit detail Progressive disclosure and private build records. When traceability matters but should not interrupt the primary path.
Boundary. This is a visual grammar, not a mandatory five-section template. The passed IA storyboard still decides what the page contains.

Your review

  1. Keep it as-is
    The installed clean-document scaffold remains the default for new public artifacts.
  2. Or revise it precisely
    Name the component, hierarchy, spacing, typography, diagram, or interaction that should change.
Migration boundary

The previous warm editorial scaffold is preserved in the workspace archive. The standalone bundled template remains available for one-file/offline delivery. Previously published artifacts are not restyled automatically.

Static Cloudflare artifacts remain public review pages, not editable or commentable documents. Editable or Lavish artifact requests are routed separately.