Building in public
What is documented - and which gap matters next.
This log is not a release history or marketing feed. It records the current state of knowledge in short, reviewable notes.
Two products, two audiences.
The product pages now separate the AshaCore WebPlatform (product in pilot phase, KitaNido as the first product, Leovino as the first Sede pilot) from AECP (engineering system with AgnoOS and the Command Center, product to follow). Both pages name their building blocks; status statements follow the internal plan. Internal terms and third-party building blocks are limited to one technology block.
AshaCore.de moves to a vision-first structure.
The public structure foregrounds the vision, AECP and WebPlatform while separating documented state, active construction and next test targets.
Local work flow documented; production path still open.
Orders, dispatches, local state views and isolated runs are internally documented; recovery and the complete order-to-proof chain remain the next test targets.
Tenant core documented; editorial journey still in build.
Isolation, reproducible provisioning and publishing boundaries work at the core; editing, migration and operations still need to meet end to end.