Why this exists
Built because our own standards kept scattering
Axceed runs over a dozen products out of one small team. Standards, decisions, and vendor terms were living in chat threads, half-finished docs, and whoever happened to remember the context that day. A version number would get hardcoded somewhere and quietly go stale the moment the standard moved on. A decision would get "fixed" by someone who didn't know it had already been made — and the fix would just as quietly vanish the next time someone touched the file.
So we gave the job to an agent, on purpose, from the architecture up — not a chat bolted onto a wiki afterward. It reads, it classifies, it drafts in your own words, and it never gets to skip the part where you see what it's about to write. Professor is that agent, and the discipline it enforces internally — a decision, once locked, is only ever superseded, never rewritten out from under you — is the same discipline your team gets from day one.
"We stopped finding out a standard had changed by tripping over the old version in production."— Engineering lead, Axceed