What this is

People Analytics Toolbox is the service substrate for the People Analytics domain: one Next.js application that exposes 19 live, independently-versioned analytical microservices ("spokes") over two transports — HTTP for engineers and MCP for AI agents. Each spoke owns one capability, its own Postgres schema, a versioned contract, and an audit trail. Consumer apps (Performix, vela, peopleanalyst-site, and future products) vendor only the typed contracts; the algorithms live here.

One repo. One deploy. One Vercel project. One Supabase project. 19 live services.

It is producer infrastructure, not an end-user app: it turns people data into governed analytical results that downstream products surface and monetize.

Who it's for

• Engineers integrating an analytical capability over HTTP.
• AI agents calling capabilities over MCP under governed scopes.
• Product teams composing spokes into Products (AnyComp, Leadership Index, Analytics-Plan).

This is the product-docs surface

Curated, reader-facing documentation — distinct from the repo's internal design/handoff docs under docs/**. Built to the portfolio Documentation Standard (~/.claude/DOCUMENTATION-STANDARD.md).

Documentation tree

Overview ........................ this page
Concepts ........................ concepts.md      (spoke · contract · transport · tenant · instrument · product)
Getting Started ................. getting-started.md  (base URL · service key · first read · first write · MCP)
Architecture .................... architecture.md  (one app · 19 spokes · schema-per-spoke · transports · substrate)
Trust & Security ................ trust-and-security.md  (tenant isolation · service-key auth · min-N · audit)
APIs (REST) ..................... apis.md          (conventions + clusters)
  └─ reference-apis.generated.md ..................... full surface table (generated)
MCP Tools ....................... mcp-tools.md     (endpoint · scopes · tool catalog)
  └─ reference-mcp.generated.md ..................... full tool table (generated)

Products (composed surfaces)
  ├─ AnyComp — compensation Decision OS ................ products/anycomp.md
  ├─ JobFrame — canonical Job Family × Focus × Level ... products/jobframe.md  (flagship)
  ├─ Leadership Index ................................. products/leadership-index.md
  └─ Analytics-Plan Generator ........................ products/analytics-plan-generator.md

Source of truth

The always-current live service list is whatever has status: "live" in src/lib/contracts/registry.ts; capability metadata + realization gates live in docs/capability-manifest.json. The API and MCP references below are generated from those declarations — they do not drift, per the documentation standard.

See also

Concepts · Getting Started · Architecture