Interpretive mode

standards compliance

Compliance to browser standards and avoiding warnings from the browser during loading requires native HTML syntax.

<!doctype html>
<script>"interpretive"</script>
<style>body {display: none}</style>
<script src="https://triv.co/3v.js"></script>

Explanation:

<!doctype html>
Optional

Declaring a document type natively is currently the only implemented way to provide a doctype in interpretive mode.
<script>"interpretive"</script>
Required to declare interpretive mode

Otherwise, if 3v.js is invoked without a declaration, the operating mode will simply be “client-rendered” rather than “interpretive”.
<style>body {display: none}</style>
Optional

An inline style element is currently the only implemented way to avoid a FOUT for large documents or resource-limited machines.

(Any styling may be included)
<script src="https://triv.co/3v.js"></script>
Required to invoke interpretive mode

The intepretive browser instruction is processed differently from other native elements.

The interpretive browser instruction does not appear in the output.

HTML spacing options are respected.

(e.g. the instruction may be condensed onto a single line)

HTML and CSS comments are respected for each line before the script is invoked.

Preliminary testing indicates that the browser often makes a determination of character set before processing of the Triv document completes.

(A browser warning mentioning character set might appear in the browser's developer console)

Declaring the character set in the interpretive browser instruction is not yet implemented.

Just in case, the line: <meta charset="utf-8"> does not produce a Triv warning anywhere in the document, as a temporary feature.