From the title, I thought this was a specification for configuring humans. I don't quite know what that means, and I'm disappointed still not to know.

Ironically the project seems LLM-generated.

I don't want to read Claude's interpretation of why your project matters. I want you to tell me directly.

What I'm missing:

1. The readme doesn't make it clear what its "float" type is. A double, a decimal, implementation defined. I'm generally not a fan of restricting numbers to what a double can represent, like toml does.

2. It doesn't have a good way to model key-value pair like types such as tagged unions, polymorphic types, or function invocations. Simply allowing a key-value pair as a value (right associative) where the key is a string matching the keys of an object would fix this. Alternatively a function call syntax would fix this, which would also enable tuples as a concept distinct from arrays.

Looks like Windows *.ini format except ":" instead of "="...

So a stripped down variant of cue? Why not use cue directly?

Can you add README sections for the schema and supported types?

> Top-level arrays. A TOML file is always a table, so a list of records needs a wrapper key.

I'm curious for example configs that are top-level lists?

See also: HUML [1]

1: https://huml.io/