Documents and model cards

Attach the documents that explain an asset — model cards, explanation reports, evaluation reports, data sheets — to its row in the register. Each file is fingerprinted when it arrives and listed in every Evidence Pack, inside the signed part, so an auditor can check the copy they hold is the one you attached.

Note
Documents are available on the Growth plan and above; Evidence Packs on the Business plan and above.

What to attach

  • Model card — what the model or agent is for, how it was built and evaluated, who should not use it, and its known limits. Vendor cards for the foundation models you build on belong here too.
  • Explanation report — how the asset reaches its outputs: the factors that drive a decision, the logic it follows, worked examples.
  • Evaluation report — accuracy, robustness, bias and red-team results.
  • Data sheet — where the training or grounding data came from and how it was prepared.
  • Other — anything else an auditor should read beside the asset.

Explanation reports describe how an asset behaves in general. What one run actually did — the conversation, the execution trace and the authority chain behind each action — is already recorded for every run and sits on the event itself.

Wytness also generates a model card or system card from the register row itself, signed and fingerprinted — see model cards and system cards.

Adding a document

Open the asset from the register, and on its Profile tab choose Add document on the Documents card. Pick the kind, choose the file and, if it helps, add a note such as the version. PDF, Markdown, plain text, JSON, HTML, PNG and JPEG files up to 25 MB are accepted. Members, admins and owners can add documents; anyone in the organisation can download them.

The same file attached twice to the same asset is refused, and the existing copy is pointed out instead.

Where the files are stored

Documents go to your organisation's archive storage, the same place as your event archive. If you bring your own storage, they land in your own container and never in Wytness storage; while your storage is unreachable an upload is refused rather than redirected.

How documents appear in the Evidence Pack

Every Evidence Pack lists each document attached to each asset — the asset, the kind, the file name, its SHA-256 fingerprint, who uploaded it and when, and the note — in the Appendices. The listing sits inside the signed pack, so changing a fingerprint breaks the signature; see verifying reports. To check a file, compute its SHA-256 (for example shasum -a 256 model-card.pdf) and compare it with the pack. The printed agent register shows how many documents each asset carries.

Removing a document

Admins and owners can remove a document. A written reason is required; the file is deleted from storage and leaves future Evidence Packs, and the upload and the removal — with the reason — stay on your audit log. Packs you have already downloaded keep the listing they were signed with.

We set no cookies. Sign-in and preferences use essential first-party browser storage only — no tracking, advertising, or third-party analytics. Privacy Policy

Documents and model cards
TABLE OF CONTENTS