Expose an __atom as internal api, or ...

[blaggacao]

https://github.com/ekala-project/atom/blob/master/src%2Fatom%2Fcompose.nix#L28

... or only expose selected keys?

Expose selected keys meant for regular usage while exposing the raw __manifest (maybe better than __atom), for introspection, potentially only when feature flagged (similar to tests).

This forces us to expose a stable api of the manifest to internal code and makes it more stable, while limiting a bit its (hypothetically useful) flexibility.

Some of the keys to expose would be:

• atom — for its name & version
• features — for feature flagging
• matrix values (tbd)

[nrdxp]

yes, I was thinking along the same lines, for now the whole config is exposed, since we don't have a fully stable config surface yet. Once the core is a bit more stabilized we can decide what is appropriate to pass here and what isn't.