What Happened

Between late April and mid-May 2026, the app layer of Three Realms Academy left a dense trail of worklogs. `wiki-site` moved away from a local Wiki.js and seed-pipeline direction into a static Next.js knowledge site on Cloud Run. `dialogue-trainer` grew from a food-service dialogue MVP into a language practice surface named 言途.

Those records now live under `apps/worklogs/` in the Academy repository. They were moved outside deploy-triggered app folders for a practical reason: editing operational notes should not redeploy Cloud Run services. That decision also made something visible. The apps are growing, and the memory of their growth is becoming part of the system.

Readers can now enter the public surfaces directly: the official site, the Three Realms Academy Wiki, Dialogue Trainer, and this Three Realms Review.

Underneath the Product Surface

On the surface, this is a familiar app-building story: deployments, DNS, OAuth, Cloud Run, Next.js, build repairs, content migration, and interface changes.

The deeper layer is more interesting: the Three Realms Protocol is being translated from text into usable tools. Wiki Site turns protocol vocabulary into a searchable, linkable, multilingual public entrance. Dialogue Trainer turns language, boundaries, care, responsibility, and repair into an interactive field where a player can practice one sentence at a time.

More precisely, the Academy layer is growing its own organs: one side preserves semantic structure; the other lets people walk into it. Website work and game work are the visible forms; the deeper formation is a usable learning field.

The Layer We Are Pointing At

The layer we are pointing at is the moment when work becomes public surface.

The internal worklogs record construction: what happened on which day, which judgment was corrected, which error forced an architectural turn. The public URLs show the other side: the entrances that readers, players, search engines, and future users can reach. Together, they form the first growth history of these apps.

Dialogue Trainer makes this especially clear. On April 27, it was a text dialogue MVP centered on `阿發小吃：午餐尖峰`. Over the following weeks, it added Gemini judging, multi-turn dialogue, journey notebook, generated journey, Growth Card, NPC cards, David life board, Value Lens, actor / judge split, and NPC opening director. These names sound like engineering items, but they are all working on the same question: language is not answer selection. It is action that leaves relationship consequences.

Wiki Site changed more quietly. It moved from heavy CMS and seed infrastructure into a static Next.js knowledge site; from local tooling into `wiki.three-quarters.net`; from a small set of pages into a LEX index, multilingual content, SEO foundation, and a new LEX-003 collection. Its job is not to excite. Its job is to make the protocol findable, citable, and slowly understandable.

What We Are Reading

This article reads a transition: Three Realms Academy is moving from "we are building some apps" toward "the protocol has usable learning entrances."

The transition is still early. Its value is not the length of the feature list. Its value is that each feature is beginning to return to the same question: how can a human practice, revisit, and repair their way through complex relationships, language choices, and protocol concepts?

Here, the worklog is not secondary material. It is an internal timeline that lets future readers know the products did not arrive suddenly. They grew through naming, splitting, deleting, repairing, deploying, and calibrating.

What Remains Uncertain

  • The worklogs are first-party internal records. Readers can enter the public URLs, but they cannot inspect every internal worklog unless the Academy repository becomes public.
  • HTTP 200 means these entrances were reachable on May 17, 2026. It does not prove stable operations, user growth, search ranking, or educational effect.
  • Dialogue Trainer's ability to help users practice more mature language still needs more playtesting and feedback.
  • Wiki Site's public value depends on continued content expansion, search indexing, and whether it becomes an entrance for protocol readers.
  • The public shape of the apps will keep changing quickly. This article records a first growth history, not a final form.

Source Notes

  • The chronology in this article mainly comes from first-party worklogs under Three Realms Academy `apps/worklogs/`.
  • These worklogs are the internal factual floor, not third-party news sources.
  • Public surfaces readers can inspect include three-quarters.net, wiki.three-quarters.net, dialogue-trainer.three-quarters.net, and news.three-quarters.net.
  • The `Three-Realms-Academy` repository returned 404 on GitHub on May 17, 2026, so this article does not present it as a publicly inspectable source link.

Our Claim, Bounded

This article's claim is narrow: the first growth history of the Three Realms Academy apps is worth recording in the Review because it marks an early transition from protocol text to protocol tools.

The boundary is equally important: these apps are still under construction, and market or classroom validation remains ahead. The article says that a set of internal construction records has begun to correspond to public surfaces readers can enter, and that this correspondence gives the Academy layer a visible shape.

A protocol that remains only in text can be read. When it grows tools, it can also be practiced. The most important thing to watch in Dialogue Trainer and Wiki Site is there.