Metadata-Version: 2.4
Name: metrik-viz
Version: 0.1.1
Summary: Metrik Visualization Lab — artifacts to VizSpec, and VizSpec to terminal or HTML.
Project-URL: Homepage, https://github.com/Asmodeus14/Metrik
Project-URL: Repository, https://github.com/Asmodeus14/Metrik
Project-URL: Issues, https://github.com/Asmodeus14/Metrik/issues
Author: The Metrik Authors
License-Expression: Apache-2.0
Classifier: Development Status :: 2 - Pre-Alpha
Classifier: Intended Audience :: Science/Research
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
Requires-Python: >=3.11
Requires-Dist: metrik-sdk==0.1.1
Requires-Dist: rich>=13.7
Description-Content-Type: text/markdown

# metrik-viz

Turns artifacts into [`VizSpec`](../../docs/planning/artifacts.md), and `VizSpec` into a chart.

```console
$ metrik viz <artifact-id>                 # render in the terminal
$ metrik viz <artifact-id> --html out.html # one self-contained file
$ metrik viz <artifact-id> --json          # the spec itself
```

Two halves, deliberately separate. **Visualizers** read an artifact and emit a spec; they never
render. **Renderers** read a spec and never see an artifact. That split is what lets one spec
render in the terminal, in a static report, and later in the web app without three
implementations drifting apart.

## No charting dependency

The HTML renderer writes its own SVG. A report is therefore a single file that opens offline
with nothing to fetch — which matters because a report is the thing that gets emailed, and one
that renders a broken-image icon six months later is worse than a table.

## Accessibility is structural

Every spec carries a table and a text summary, and the schema refuses a chart that encodes
meaning in colour alone. The terminal renderer shows the table; the HTML renderer emits the
chart *and* the table, with the text summary as the figure's accessible description.
