Astent — Product Documentation
An explanation of how the Astent AI-Configurable ERP program fits together — the concepts, the architecture, and the cases that test it.
Scaffold. The deployment pipeline is live; the content is not written yet. Pages are tracked as issues in the Website: Product Documentation project.
This deployment is not yet gated. The Astent identity service does not exist yet, so nothing drawn from customer research, product strategy, credentials, or any protected sandbox may be published here until it does.
Written
- The architecture — how the two repositories, the harness, the adapter, the ERPNext substrate and the case packages fit together.
Planned
- What Astent is — the research question and the thesis.
- The core concepts — the vocabulary everything else assumes.
- The layer stack — ERPNext core → Astent core → client app → client policy, in depth.
- The multi-case pattern — what a case contributes, and why isolation is one site per case.
- The lifecycle — the eight commands and what each guarantees.
- The cases — Fenestra and Kler, including what each does not model.
- Reading paths — where to go next in the source repos, by audience.