[0.1 draft] [guide 15 · spec 15 pages]

guide/metadata

Metadata (meta-*)

txtab

# meta-source sales_db.orders
# meta-author alex@example.com
# meta-as-of 2026-11-01
# meta-grain one row per order

meta-<key> followed by free text — no quotes, no escaping. In the file block it describes the file; in a table block, that table. The two don't inherit from each other.

Keyword Meaning
meta-source Where the data came from — a system, table or file
meta-author Who made it
meta-comment A description of the dataset
meta-grain What one row is: one row per order, one row per customer per day
meta-created When the file was written
meta-exported When the data was exported
meta-as-of The date the data is current as of
meta-license The data's license, e.g. CC-BY-4.0
meta-tool The tool that wrote the file
meta-tags Comma-separated tags

Use any other key you like: meta-project q4-review. A meta-* line with no text is a flag — its presence is the value.

Three different dates

A snapshot of balances taken at the end of October, exported on 3 November, and written into a file on 4 November:

txtab

# meta-as-of 2026-10-31
# meta-exported 2026-11-03T09:00:00Z
# meta-created 2026-11-04T10:15:00Z

meta-as-of is the one that matters for analysis: it's the moment the numbers describe.

Grain

meta-grain answers the question everyone asks first: what does one row mean? "One row per order" and "one row per order line" give very different sums. Write it down once.

guide/metadata.md on GitHub