CoreWise Academy

How it’s built

The Process

01Guides start from real sources

Most start with a video the editor learned from. The transcript is fetched and broken into concepts, prerequisites, misconceptions, exercises, and quotable moments with timestamps. Every guide credits its sources on the page.

02Human in the loop

Nothing publishes directly. Every draft arrives as a pull request; the editor reviews, corrects, and merges. Merging is publishing: the site rebuilds and the guide goes live.

StageWhat happensWhat comes out
Ingest A source video or document is fetched and broken into concepts, misconceptions, exercises, and quotable moments Structured notes + source log
Draft The writing tool reads the whole curriculum, then writes an original guide (or extends an existing one) MDX draft on a branch
Review The draft arrives as a pull request; the editor reviews, corrects, and merges Published guide
Rebuild Merging rebuilds the static site, so publishing and merging are the same act Live page

03The style book is strict

The Academy keeps one written style book. A machine checks some of its rules on every build and blocks the deploy on any hit; the editor holds the rest in review.

RuleHeld by
No em dash anywhere on the siteBuild gate
Titles and headings stay under a length capBuild gate
Plain words, and fewer of themReview
Say plainly what a thing isReview
No jargon and no invented wordsReview
No walls of text; the content in the shape that fits itReview

These are a sample. The full book lives in skills and permanent memory rules.

04Learning science, applied

They apply the standard findings on the testing effect and active recall to a guide format.

05The loop behind every change

Major updates or changes run through the Harness Firmware loop:

Plate III · Loop Fig. 1
Figure: how every change to this site is made. Rules, skills, and checks feed a five-stage loop (recall, plan, execute, audit, integrate) run by one manager session; a stall watch steps in when work stalls; a candidate pull request passes the checks into an updated main, and the lessons go back into the rules. Every name is a link to the real file. INPUTS Rules CLAUDE.md rules always loaded;7 reference files on demand CLAUDE.md .claude/reference/ caveman · RTK · STK FEWER TOKENS Skills 31 skills, one folder each;repeated failures becomerules for the next session .claude/skills/ .agents/skills/ · Codex copy Checks CI, tests, audited evidence:every claim gets checked .github/workflows/ site/scripts/ · build gates verify-this Manager session one context holds the goal I Recall recall .claude/reference/ II Plan long-horizon · dare brainstorming · why enhance-prompt III Execute fable-mode wow-loop · showpiece IV Audit long-horizon · verify-this advocate · codex-review astra-review · arena wow-loop · impartial-review handoff-audit V Integrate record the result refine · writing recall save STALL WATCH 2 audit fails on one step: change the approach 3 rounds, no new verified progress: rewrite the plan long-horizon · codex-review when work stalls Candidate branch + PR, evidence attached merge · gh pr checks pass? merge repair and retry · babysit-ci Updated main squash-merge to main Vercel publishes the site lessons go to refine and recall save refine · recall save · deployment.md lessons go back into the rules, skills, and reference files

Scroll sideways for the whole figure

One session holds the goal and walks the ring: recall, plan, execute, audit, integrate. Checks gate the merge, and what merges goes back into the rules. ✦ = the session · solid = every round · dashed = only when needed

FAQ · The Process

How are the guides made?

Each guide starts from real sources: a lecture the editor learned from, official docs fetched at writing time, or the editor's own field notes. Notes from several sources are combined into one original piece, and a human editor reviews every draft as a pull request before it publishes.

How long are the guides?

Guides run 5 to 11 minutes each, and the whole catalogue is about 311 minutes of reading. A typical guide is made to fit inside one sitting.

Who checks what gets published?

100% of guides pass through the editor, Ryan D. Allen, before they go live. Nothing publishes directly: every draft is a pull request, review notes are resolved, and merging is publishing.