ISON Documentation

1. Core structure

Each block starts with kind.name, followed by field headers and one or more value rows.

table.users
id name role active
1 "Andy" admin true
2 "Lin" analyst true

2. Value typing

• Boolean: true, false
• Null: null
• Number: integers and floats
• String: quoted when needed
• Reference: prefixed with colon, for example :users:1

3. References and linking

References make graph-like relationships explicit while keeping payloads compact.

table.orders
id user_ref total status
5001 :users:1 245.99 paid
5002 :users:2 91.00 pending

4. Prompt-focused best practices

• Keep one domain concept per block.
• Use explicit names for fields and references.
• Normalize repeated nested objects into references.
• Validate before sending payloads to LLM endpoints.