Operating system

An operating system for organizational learning.

Nineteen live analytical services compose into a coherent stack beneath your own UIs — normalization, enrichment, adaptive measurement, and decision tools wired for AI access. Built for analysts who refuse to confuse activity with intelligence — and want the org to learn faster without mistaking varnish for comprehension.

The idea

Faster learning beats prettier charts.

Organizations already run on operating systems underneath the logos you see — approvals, postings, paychecks. Yet the analytic layer too often behaved like bundled media — survey here, ERP there, spreadsheets in the middle — instead of coordinating how evidence tightens organizational priors weekly. Nobody sets out to crawl the Valley of the Shadow of Death pipeline where CSV handoffs silently mutate denominators until nobody trusts last month's cut. Shops land there anyhow because tooling sold the hamburger (another dashboard SKU) without the fries (canonical cohorts that survive ERP rewrites, reproducible lineage, honesty about sample floors).

The real product is not dashboards. The real product is faster organizational learning.

This toolbox is how that learning loops as software rather than folklore: typed boundaries between services, audited calls, methodological defaults that stop being heroic one-offs. Operational reporting answers "what happened last quarter?" Analytic operating capacity answers earlier "is this lever still sharper than sampling noise?, which item bank entries aged out quietly?, still worth delaying a reorganize-without-burning-the-research-queue?" Elevated realism for the discipline that already deserved it.

COMPOSITION — HTTP CONTRACTS, NOT SHARED INTERNALSperformance-validityGET /api/spokes/...performance-calibrationGET /api/spokes/...segmentation-studioGET /api/spokes/...core/import core/ ✗ forbiddenmanager-effectivenessMEI composite + archetypeMEICompositearchetyperecalibration-auditSpokes compose contracts over HTTP. The boundary is the API — never the codebase.
Typed boundaries in practice: manager-effectiveness composes three sibling spokes over HTTP contracts, never their internals.

Architecture in three layers

The kitchen → the recipes → service to the diner.

The synthetic vision memo names the footing layer "The Kitchen": raw inputs only become nourishment after prep you can cite. Layers below anchor to today's live spokes plus the explicitly declared runway.

Layer 1 — Data foundation

Reliable ingredients + portion discipline.

segmentation-studio earns IDs that outlive vendor column renames rather than restarting Excel archaeology after every HRIS patch. calculus emits objects where confidence method selection respects sample shape — analysts stop hand-wringing privately about misuse of normal intervals on sparse proportions. metrics-catalog keeps metric ontology legible beyond tribal spreadsheet macros. Boundary enforcement travels through data-anonymizer any time aggregates would violate -class floors while those joins fan out beyond engineering-only audiences.

Layer 2 — Insight & intelligence

Methods that deserve to speak.

Once ingredients normalize, differentiated intelligence arrives: reincarnation hardens adaptive inside production — pool choreography, Cronbach instrumentation, retiring items politely instead of politely lying in static surveys. preference-modeler exposes , , penny allocation workloads without renting a wholly separate boutique license for each HR study. Tighter scaffolding, fuller assembly, sharper primitives — deliberately unglamorous code where rigor earns budget — plus explicit so exploratory factor work stops rotting inside consultant Jupyter handoffs. Already live: forecasting marrying sketches with /-style prompts when delaying a reorganize-or-hold decision burns measurable runway.

Layer 3 — Delivery

Where learning meets actual Monday calendars.

The toolbox publishes reference surfaces — Insight Player pacing, MCP-accessible tooling surfaces — knowing durable value sits wherever your operators already live: approvals, executive mobile moments, investigator consoles for comp anomalies. Planned PAT-N9-era admin shells, persona-targeted dashboards, hardened ops tooling exist because evidence unopened is organizational amnesia. gateways matter here symmetrically with HTTP — audited, scoped access so AI coworkers inherit the contracts humans already trust instead of improvising hallucinated plumbing.

Architectural insight

Workforce intelligence is fundamentally graph-shaped and temporal.

Careers traverse matrices, rotational programs, mergers, reopened reqs with altered reporting lines — snapshots taken Thursday misalign with survey payloads captured Friday afternoon. Treating humanity as interchangeable rows surrenders narrative fidelity precisely where stakes climb. (who reported to whom, when policies toggled geography taxability, consecutive pulse waves on moving cohort kernels) predicates every honest downstream claim. Glamorous statistical envelopes or finely tuned psychometric models pasted atop rotten identity joins become precision theater instead of reproducible inference.

Modular , -grounded interoperability, MCP + HTTP parity let you weave those joins intentionally — swapping one methodological engine without ripping monolithic ontology assumptions away from unwilling finance partners.

Competitive posture

Why incumbent stacks don't spontaneously become this OS.

Each quadrant optimizes faithfully for its purchaser — CFO workflow integrity, Chief Listening Officer delight, analytics theater — leaving compositional methodology and AI-safe contracts as your integration tax. Toolbox posture: unify those missions as services engineers and agents orchestrate deliberately.

Representative laneStrengthStructural blind spot vs learning OS
(and ERP-class HR suites)Systems of record tuned for transactions — jobs, hires, approvals, payouts.Rarely accountable for methodological joins with survey worlds; analytics often stops at snapshots built for payroll legibility.
/ -style PA platformsDashboards atop vendor cubes — curated metrics, narratives, predictable navigation.Still squarely widget-first: your org's ontology is presumed, not programmable; methodological rigor is optional bolt-on commentary.
/ Culture Amp / Lattice-class survey suitesOutstanding at response capture and employee listening UX.Treat segmentation + HRIS lineage as exporting CSVs downstream; seldom ship adaptive diagnostics or honesty about low-N aggregates at the boundary.
/ — generic BIInfinite flexibility to draw shapes on glass.No contractual opinion on psychometrics, privacy floors, anonymity gates, longitudinal identity, causal designs — analysts rebuild civilization per dashboard.
People Analytics ToolboxMicroservice constellation + MCP/HTTP transports + explicit contracts unify ingestion, enrichment, adaptive measurement, and decision instrumentation without forcing a bundled UI religion. Consume one spoke. Or compose four. Trade studies move at service speed instead of eighteen-month roadmap theater.

None of those vendor rows are caricatures — they monetize narrower promises well. Toolbox thesis: methodological ownership returns to practitioners when algorithms + audit surfaces live on your plane of control.

Next motions

Decide whether layering OS-shaped services beats funding another integrations landfill. Read deeper methodology narratives, escalate procurement translation for executives unwilling to skim service diagrams, then book tangible minutes if you're ready.