Which is not contradicting with what I have said. If you do everything via the proper OH2 APIs (REST for UIs and console for command line users) then it will be in the jsondb including all runtime information (states, properties, api-tokens, passwords etc).
Textual configured things use a different code-path and that is what I’m aiming for removing from the core to reduce complexity, errors, slowness. This will be done via a separate, in the future also replaceable or extendable IO service that imports / exports based on custom triggers (like for example file system changes).