The problem
Hiring doctrine usually lives as oral tradition. Each interviewer interprets the bar differently, notes are inconsistent, and calibration decays over time. The company has a philosophy but not an operating system.
What I built
RishiOS encodes the operating logic directly into an MCP server. Six modes:
- Score candidates on a shared framework
- Generate job descriptions aligned to the rubric
- Build executive briefs from raw context
- Structure loose interview notes into consistent formats
- Generate calibration references
- Learn from override patterns without losing the base doctrine
Built in TypeScript with the MCP SDK and Zod for runtime validation. Every decision is auditable — the system tracks what changed and why.
Trade-off
The doctrine is opinionated. That is the point. A team that disagrees with the framework should not use this system — it enforces a specific view of what good hiring looks like. The alternative is no system at all, which means drift.