Run artifact

workspace/logs/20260814.050808.885Z_toml_lineage_attribute_codex.output.txt

<requirement name="document-lexing" stories="lexical-whitespace-comments">
A TOML file must be a valid UTF-8 encoded Unicode document.
</requirement>
<requirement name="comments" stories="lexical-whitespace-comments">
A hash symbol marks the rest of the line as a comment, except when inside a string.
</requirement>
<requirement name="key-forms" stories="keys-forms">
A key may be either bare, quoted, or dotted.
</requirement>
<requirement name="key-semantics" stories="keys-semantics">
Defining a key multiple times is invalid.
</requirement>
<requirement name="string-forms" stories="lexical-strings">
There are four ways to express strings: basic, multi-line basic, literal, and multi-line literal.
</requirement>
<requirement name="numeric-values" stories="lexical-numbers">
Integers are whole numbers.
</requirement>
<requirement name="floating-point-values" stories="lexical-numbers">
Floats should be implemented as IEEE 754 binary64 values.
</requirement>
<requirement name="boolean-values" stories="lexical-numbers">
Booleans are just the tokens you're used to. Always lowercase.
</requirement>
<requirement name="date-time-values" stories="lexical-datetime">
To unambiguously represent a specific instant in time, you may use an RFC 3339 formatted date-time with offset.
</requirement>
<requirement name="arrays" stories="structures-arrays">
Arrays are square brackets with values inside.
</requirement>
<requirement name="standard-tables" stories="tables-standard">
Tables (also known as hash tables or dictionaries) are collections of key/value pairs.
</requirement>
<requirement name="table-redefinition" stories="tables-redefinition">
Like keys, you cannot define a table more than once. Doing so is invalid.
</requirement>
<requirement name="inline-tables" stories="structures-inline-tables">
Inline tables provide a more compact syntax for expressing tables.
</requirement>
<requirement name="inline-table-closure" stories="structures-inline-table-closure">
Inline tables are fully self-contained and define all keys and sub-tables within them. Keys and sub-tables cannot be added outside the braces.
</requirement>
<requirement name="arrays-of-tables" stories="tables-arrays">
The last syntax that has not yet been described allows writing arrays of tables.
</requirement>
<requirement name="arrays-of-tables-ordering" stories="tables-arrays-ordering">
If the parent of a table or array of tables is an array element, that element must already have been defined before the child can be defined.
</requirement>
<requirement name="filename-extension" stories="">
TOML files should use the extension `.toml`.
</requirement>
<requirement name="mime-type" stories="">
When transferring TOML files over the internet, the appropriate MIME type is `application/toml`.
</requirement>
<unattached story="architecture"/>
<unattached story="decoder-contract"/>
<unattached story="decoder-invalid-input"/>
<unattached story="decoder-tagged-json"/>
<unattached story="conformance"/>