Honest trade-offs
by•
Since transparency builds trust: what NAEOS is not.
It's not a "no-code, describe and never code again" tool. For systems where the spec IS the artifact (APIs, services, schemas, governance), it shines. It's not magic for arbitrary bespoke UI.
The spec language has a learning curve ($ref, $include, $fn, $if). We document it thoroughly, but it's real syntax.
Generated code is a consistent starting point — you own and modify it. The pipeline keeps the spec authoritative, and the diff engine shows drift.
I'd rather say this than have people discover it later. Questions welcome.
1 view
Replies