ArchForgeAn enterprise platform built for the AI era

Contract-first four-repo architecture · Spring Boot 4.1 + Java 25 · Humans and AI agents share the same source of truth

Get Started

Contract-first

GitHub

⚙️

Modern runtime

Spring Boot 4.1 + Java 25 virtual threads. Optional Native Image (~100ms start). OpenTelemetry out of the box.

🧩

Contract-first, four repos

The backend generates the OpenAPI contract and enums. Admin and Web are checked against it. Deleted paths stay deleted.

🤖

AI-native workflow

Every repo has AGENTS.md. Skills in ArchForge/.agents are progressive disclosure. CLI can install them and speak MCP.

Why four repositories?

ArchForge is four independent Git repositories, cloned side by side. There are no git submodules. The backend repo owns the contract (spec/openapi.yaml, generated from the code) and the AI context (repos.yaml, AGENTS.md, .agents/) — an agent reads it first. The former ArchForgeSpec repository was merged into it (ADR-0012).

Repository	Role	Local port
ArchForge	Backend. `archforge-server-admin` + `archforge-server-web`	`:8080` / `:8081`
ArchForgeAdmin	Admin UI (vue-pure-admin)	`:8848` → `:8080`
ArchForgeWeb	C-end (Next.js)	`:3000` → `:8081`
ArchForgeDocs	This VitePress site	`npm run docs:dev`

Start with contract-first, then AI workflow. CLI lives in the backend repo: ./archforge.

Run it locally

bash

# siblings, no submodules
git clone https://github.com/sofn/ArchForge.git
git clone https://github.com/sofn/ArchForgeAdmin.git
git clone https://github.com/sofn/ArchForgeWeb.git
git clone https://github.com/sofn/ArchForgeDocs.git

cd ArchForge
./archforge init --write
./archforge infra up
FILE_STORAGE_TYPE=local ./gradlew :archforge-server-admin:bootRun

Admin default login is admin / admin123 (captcha on in dev). There is no hosted public demo yet — run the stack locally or with Docker Compose.