onec-frameworkModel the business. Generate the rest.

Reusable Spring Boot starters that turn typed Java metadata — catalogs, documents, registers — into a database schema, a generic REST API, a server-driven UI, and an MCP tool surface for AI agents.

Architecture

Configuration reference

View on GitHub

🗂️

Model the business

Catalogs, documents, tabular sections, accumulation/information registers, enumerations, and constants — all typed Java, compiler-checked. No tables or DTOs by hand.

⚙️

Generated, not hand-written

Schema, repositories, a type-safe query layer, the generic REST API, and migration history are all derived from the model at boot.

🖥️

Server-driven UI + MCP

A DivKit admin UI and a Model Context Protocol tool surface for AI agents, both generated from the same metadata and gated by the same RBAC.

📄

Docs from the source of truth

The configuration reference is generated from the @ConfigurationProperties Javadoc — and the build fails if it ever drifts from the code.

Get started

Add the starter (Java 21, Spring Boot 3.4.x). Packages are com.onec.*; the Maven group is io.github.onec-erp (open core, Apache-2.0).

xml

<dependency>
  <groupId>io.github.onec-erp</groupId>
  <artifactId>onec-framework-starter</artifactId>
  <version>0.10.0</version>
</dependency>

Then read Architecture for how it fits together, or the handoff guide for building an ERP on the published libraries.

How these docs are built

This site mixes hand-written guides with reference generated from the source of truth, so the reference can't drift from the code:

Surface	Source of truth	How it's produced
Configuration properties	the `@ConfigurationProperties` Javadoc	`./gradlew generateConfigDocs` renders each starter's `spring-configuration-metadata.json`; `./gradlew check` fails if the committed file drifts
Java API (Javadoc)	the Java source	`./gradlew aggregateJavadoc`
Architecture, guides	maintained by hand	written Markdown

Changing a property? Edit its Javadoc and run ./gradlew generateConfigDocs — never hand-edit the table. See Keeping docs in sync.