How we work inside the Temple

The Centaur Model

SLOT is the key that opens the Temple — joining the Shadstone ninjas. That key lives on the jobs site: jobs.shadstone.com/slot. The map of rooms inside is training.shadstone.com/temple. This page is how you work after the door opens.

Ninja is who you are (training.shadstone.com/ninja). Centaur is how you work: a human and AI together, stronger than either alone. The chess version is simple — an average player plus an average computer can beat the strongest machine. We run that as an operating model, not a slogan.

A hooded Shadstone centaur holding a lantern in the Temple courtyard

The loop

  1. Work arrives from a client app (design, email, SEO, ecommerce, and others) intotasks.regardingwork.com.
  2. The engine uses a project template and sends a first pass to AI.
  3. A ninja who knows that task reviews, iterates, and owns quality. Taste stays human.
  4. Missing context comes from onboarding (onboard.regardingwork.com), not from guessing.
  5. If the named ninja is at capacity, the task can route tojobs.regardingwork.com, then QC atqc.regardingwork.com before it returns to the flow.

AI takes the first pass for speed. The ninja takes the last pass for judgment. That pairing is the Centaur.

Centaur model workflow diagram: client apps feed the task engine, with onboarding, QC, and contractor routing

What this is not

  • Not “replace the ninja with a bot.” The human half is the point.
  • Not a jobs listing. Open roles stay on jobs.shadstone.com.
  • Not the Handbook. That book lives in the inner sanctum — ninjas only, after you join. This page is the public model, not the SOP library.

Where to go next