Skip to content

WildEditorInChief (WEIC)

WildEditorInChief (WEIC) is the governed authoring and API platform within the Oryvin architecture.

WEIC is the second-generation evolution of EditorInChief (EIC). EIC was a local Node.js system. WEIC is being built as a multi-user platform centered on WildFly, Java, and PostgreSQL.

This is not only a platform transition. It is also a practical example of Oryvin being used to update itself under human oversight.

Core concepts

WEIC is built around:

  • stable document identity
  • revision-first content storage
  • canonical HTML document representation
  • reusable content fragments
  • explicit review and publication workflows
  • traceable governance of knowledge changes

Documents are not overwritten in place. Content changes occur through revision creation.

Operational model

WEIC now follows a practical release discipline aligned with the rest of the platform:

  1. build and assign a baseline
  2. deploy
  3. verify runtime identity through /health
  4. commit and push only after verification succeeds

This release order matters because it keeps source, deployment, and diagnostics aligned.

Health contract

WEIC exposes /api/health using the platform health model:

{
  "status": "ok",
  "service": "weic-api",
  "baseline": "...",
  "buildUtc": "...",
  "sourceRevision": "...",
  "version": "...",
  "utc": "..."
}