# HTML Artifact Collaboration Audit

Use this worksheet with the [HTML Artifact Collaboration Checklist 2026](https://www.html-docs.com/guides/html-artifact-collaboration-checklist). Test one representative artifact as publisher, signed-out reviewer, and API, CLI, or MCP client. Save a URL, date, screenshot or response, and documentation link for every result.

For automated audits, use the [JSON Schema](https://www.html-docs.com/research/html-artifact-collaboration-audit-schema-2026.json) and start from the [valid example record](https://www.html-docs.com/research/html-artifact-collaboration-audit-example-2026.json).

Validate a completed JSON audit with the pinned AJV CLI:

```bash
curl -fsSLO https://www.html-docs.com/research/html-artifact-collaboration-audit-schema-2026.json
npx --yes --package=ajv-cli@5.0.0 --package=ajv-formats@3.0.1 \
  ajv validate --spec=draft2020 -c ajv-formats \
  -s html-artifact-collaboration-audit-schema-2026.json \
  -d your-audit.json
```

The schema requires all 15 result IDs exactly once. A score of 2 must use `pass` and include evidence; a score of 1 must use `workaround` and include evidence; a score of 0 must use `unverified`.

## Audit metadata

- Platform:
- Artifact title:
- Artifact URL:
- Auditor:
- Test date:
- Browser and version:
- API, CLI, or MCP client and version:
- Access mode tested:

## Scoring

- **2 — Reproducible pass:** the behavior works as described and has saved evidence.
- **1 — Documented workaround:** the outcome is possible through an extra, documented step.
- **0 — Missing or unverified:** the capability is absent or the result cannot be reproduced.

## Results

| ID | Criterion | Score (0–2) | Evidence URL or file | Finding and limitations |
|---|---|---:|---|---|
| A1 | Stable HTTPS URL |  |  |  |
| A2 | Explicit access mode |  |  |  |
| A3 | Rendered browser view |  |  |  |
| R1 | Contextual feedback |  |  |  |
| R2 | Resolvable discussion |  |  |  |
| R3 | Version recovery |  |  |  |
| G1 | Machine-readable state |  |  |  |
| G2 | Scoped updates |  |  |  |
| G3 | Durable identifiers |  |  |  |
| G4 | Concurrent update safety |  |  |  |
| P1 | Authorship and revision provenance |  |  |  |
| T1 | Indexing intent |  |  |  |
| T2 | Share preview metadata |  |  |  |
| T3 | Accessible reading path |  |  |  |
| T4 | Active content boundary |  |  |  |
|  | **Total** | **/ 30** |  |  |

## Interpretation

- **26–30 — Collaboration-ready:** the workflow survives review and revision with little manual handoff.
- **17–25 — Shareable with gaps:** the artifact works, but feedback or automation still depends on side channels.
- **0–16 — Fragile handoff:** treat the link as a preview, not a durable collaboration record.

## Reproduction notes

Record the exact steps another evaluator should follow, including any account state, permissions, commands, request payloads, and expected results. Do not include passwords, tokens, API keys, private URLs, or personal data.

1.
2.
3.

## Summary

- Total score:
- Strongest capability:
- Largest collaboration gap:
- Required workaround:
- Recommended next test:

## Attribution

Based on [HTML Artifact Collaboration Checklist 2026](https://www.html-docs.com/guides/html-artifact-collaboration-checklist) by Raunaq Naidu, HTML Docs. Version 1.8, updated 2026-08-23.