Publish a report

Publish#

$ L80 templates list$ L80 publish report.json --template generic.report.v1$ L80 publish report.json --template bench.report.v1 --dry-run

Each prints a URL on its last line. --dry-run validates locally and reports without publishing. Pick the layout from Templates; each links to a complete valid payload. For a BetterBench run, use L80 betterbench instead of publishing the file directly.

Naming the template#

--template on the command line and "$template" in the JSON both work. Use both and they must agree, or the command stops with E_TEMPLATE_CONFLICT rather than guessing.

What a published page is#

• Public. Anyone with the link can read it.
• Immutable. To change something, publish again and share the new link. Verification changes a page's badge, never its content.
• Unindexed. Search engines are told to stay out; sharing the link is unaffected.
• Self-contained. No scripts, fonts or trackers load.
• Labelled. Every page carries its trust tier: “Self-reported” until a verifier stamps it. Tiers.
• Kept 5 days, then removed. Republish to keep a result around.

History#

$ L80 history                  # newest first: time, template, tier, URL, title$ L80 history --all --json     # everything this key ever published$ L80 history --local          # only this machine, with each source file$ L80 history --tier verified

The server lists every page published with your key, from any machine. Each publish is also recorded in ~/.config/L80/history.jsonl, which works offline and is the only record of which file each page came from. It is also the provenance a verification request carries.