Independent websites from a shared core. Engineering that stays reviewable.
Product · AshaCore WebPlatform
A website for your organisation—from a shared, tested core, not as an individual software project. Operated in Germany.
Engineering system · AECP
A control system that translates intent into identifiable, budgeted and evidence-bound work—for agents and people. AgnoOS is the engine, the Command Center the interface.
Product · AshaCore WebPlatform: independent websites from a shared, tested core. Engineering system · AECP: traceable, budgeted and evidence-bound work for agents and people.
AECP
Control system · AgnoOS as engine · Command Center as interface
AshaCore Engineering Control Plane
A control system that translates intent into identifiable, budgeted and evidence-bound work—for agents and people.
Engineering system, product to follow
Current status
As of
Documented
The plan, foundations and the ratified starting point are documented.
In progress
The first dispatches on both tracks are running; the kernel foundation and delivery capability are advancing in parallel.
Next proof
The next planned milestone is the go proof for the durable runtime.
The published overview separates the internally documented state, active construction and the next check; it does not promise public availability.
Systems
Clear product and system boundaries
AECP combines AgnoOS as its engine and the Command Center as its user interface. The AshaCore WebPlatform is developed as a separate product.
Traceability
Work leaves documented traces
Orders, hand-offs, tests, reviews and run state are kept as reviewable artefacts wherever possible.
Boundaries
The unfinished part stays visible
Anything that only works with fixtures, lacks end-to-end proof or requires human approval is named as such.
Our development · selected milestones
Practical product work shapes our engineering principles.
The WebPlatform and the internal engineering system address different tasks. Their shared lesson: explicit boundaries, a readable data model and verifiable outcomes need to be built in early.
June 2026
The shared platform foundation
The architecture establishes one generic application for multiple websites and an explicit account boundary. Reusable content, roles and tenant isolation become its foundation.
July 2026
Products and quality standards take shape
Nido and Sede receive a defined product and package structure. Reviewable security and privacy evidence becomes part of ordinary development work.
15 August 2026
An audit sharpens the approach to AI work
A technical assessment of AECP and AgnoOS distinguishes architectural intent, implementation and runtime evidence. It clarifies priorities for harnessing, context boundaries and reliable outcome states.
September 2026
Making the lessons accessible
We explain the product lines and the reasons behind the architecture: bounded autonomy, focused retrieval, verifiable work and secure platform operations. Development goals remain clearly identified.
Who builds
Ashkan is accountable. Agents take on clearly bounded work.
The collaboration is organised by function: context and order first, isolated implementation next, independent review before hand-off.
Accountable human
Ashkan Nezami
Founder, product accountability and final decision
Ashkan sets vision and priorities, decides on risk and keeps public releases, production and direction in human hands.
Functional AI agent roles
01
Product & architecture
Sharpen goals, shape work and keep system boundaries coherent.
02
Engineering
Build in isolated work states and produce reproducible technical proof.
03
Review & quality
Review the same state independently and make disagreements visible.
04
Design & research
Translate vision into understandable interaction and challenge assumptions early.
The documented state, not a polished retrospective.
Short dated notes record what is internally documented and which gap matters next.
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.