{
  "generated_by": "garpedia-page-model-exporter",
  "record": {
    "anchor_resolution_status": "not_applicable",
    "canonical_sections": [
      {
        "body": [
          {
            "text": "# Authentication Infrastructure and the Identity Custody Surface: WorkOS at the Center of the AI Access Chain"
          },
          {
            "text": "Counterpose | CP-58 | March 16, 2026"
          },
          {
            "text": "A publication of Vega Commons Project, Inc."
          },
          {
            "text": "---"
          },
          {
            "text": "WorkOS announced a $100 million Series C at a $2 billion valuation on March 2, 2026. The company provides enterprise authentication infrastructure (SSO, directory sync, role-based access control, multi-factor authentication, audit logs) as an API service consumed by application developers. Its customer list includes OpenAI, Anthropic, xAI, Cursor, Perplexity, Sierra, Baseten, Replit, Vercel, and others."
          },
          {
            "text": "The observation here is structural, not competitive. WorkOS solves whether an enterprise user was authenticated, whether an action was authorized under policy, and whether an audit log entry was created. It does not address who holds custody of those authentication records across the distributed chain, under what retention policy each node retains, for how long, or what happens when those records are the subject of legal process."
          },
          {
            "text": "## Authentication Records and Custody"
          },
          {
            "text": "A custody surface is the set of records an AI system and its supporting infrastructure generate during operation that can be discovered, subpoenaed, or compelled through legal process. An interaction record is the log of what a user asked, what the system responded, and any reasoning the system performed. The authentication layer sits below the interaction layer but creates its own class of discoverable records."
          },
          {
            "text": "When an enterprise user at a law firm authenticates to an AI platform via SSO, the authentication event creates records at the firm's identity provider, at WorkOS (which mediates the SSO flow and generates audit log entries), and at the AI platform (which receives the authenticated session). Each node retains independently under its own policy. No protocol-level mechanism propagates litigation hold, preservation, or deletion across that chain."
          },
          {
            "text": "This is a recognizable pattern. Other custody-relevant developments have identified the gap between procedural authorization controls and the retention governance of the records those controls create. At the payment layer, systems that solve whether a consumer authorized an agentic transaction do not address who retains the authorization record, for how long, or what happens when it is subpoenaed. WorkOS replicates this structural pattern at the identity layer."
          },
          {
            "text": "## Cross-Platform Identity Correlation"
          },
          {
            "text": "Because a single vendor mediates enterprise authentication for OpenAI, Anthropic, xAI, and other AI platforms simultaneously, the consolidation creates a cross-platform identity record surface. WorkOS holds authentication events that correlate enterprise users to AI platform sessions across providers. That correlation data (linking a specific employee to a specific AI session on a specific platform at a specific time) is discovery material of direct relevance in employment disputes, regulatory investigations, malpractice claims, and trade secret litigation."
          },
          {
            "text": "The correlation problem is distinct from the interaction record problem. Even if an AI platform minimizes its session retention, the authentication records at the mediation layer may persist independently and serve as an evidentiary link between the user and the session."
          },
          {
            "text": "## Directory Sync as Ongoing Custody Surface"
          },
          {
            "text": "SCIM directory sync creates a continuous record surface beyond the point-in-time authentication event. When an employee joins, changes roles, or departs an organization, directory sync propagates those changes from the enterprise's HR system through WorkOS to connected AI platforms. These lifecycle events create records at each node in the chain."
          },
          {
            "text": "In an employment dispute, the directory sync records establish when a departing employee's access to AI platforms was provisioned and when it was deprovisioned. If the employee used AI tools to generate work product, draft communications, or process client data between the events that triggered the dispute and the deprovisioning of access, the sync records are the evidentiary link."
          },
          {
            "text": "## Agentic Authentication at Scale"
          },
          {
            "text": "WorkOS's founder frames the agentic future explicitly: software running inside organizations will not be operated by people, but every action will still require authentication, authorization, and auditability. The company is building authentication infrastructure for agentic systems, not only for human users."
          },
          {
            "text": "Agent authentication generates a structurally different record surface than human authentication. A human user authenticates once per session and generates a bounded set of records. An agentic system may authenticate continuously, at high frequency, across multiple services, generating authentication records at each invocation. The volume of audit log entries, permission checks, and verification events scales with agent activity, not human session duration."
          },
          {
            "text": "WorkOS also lists Model Context Protocol capabilities among its product features. If WorkOS provides MCP server functionality for authentication, each MCP-mediated authentication event creates an additional record node in the custody chain. An agentic system authenticating through WorkOS via MCP generates records at the agent platform, at the MCP transport layer, at WorkOS, at the identity provider, and at any downstream service the authenticated agent accesses."
          },
          {
            "text": "## Open Question"
          },
          {
            "text": "Under existing legal frameworks, authentication metadata (who authenticated, when, to which platform, and what permissions were exercised) is producible through legal process and is unlikely to qualify for work product protection under any current doctrine. The procedural controls that enterprises adopt to strengthen access governance create additional retention surfaces. Enterprise SSO generates more records than direct authentication. Directory sync generates ongoing records of organizational membership changes. Role-based access control generates records of permission grants, modifications, and revocations. Audit logs are, by definition, retained records."
          },
          {
            "text": "The question WorkOS's position in the AI access chain surfaces is whether authentication infrastructure that solves the identity problem also needs to address the custody problem, or whether the market will continue to treat these as separate concerns until a court order demonstrates that they are not."
          },
          {
            "text": "---"
          },
          {
            "text": "## Sources"
          },
          {
            "text": "| Source | Date | Description | URL |\n|--------|------|-------------|-----|\n| WorkOS blog (workos.com/blog/series-c) | March 2, 2026 | Series C announcement, $2B valuation | https://workos.com/blog/series-c |\n| WorkOS product page | March 2026 | Product capabilities, customer list | https://workos.com |\n| Michael Grinich announcement | March 2, 2026 | Three-phase company trajectory, agentic framing |  |"
          },
          {
            "text": "---"
          },
          {
            "text": "## Amendment Log"
          },
          {
            "text": "*No amendments to date.*"
          },
          {
            "text": "---"
          },
          {
            "text": "The observations presented reflect analytical assessment of publicly available information and do not constitute legal, insurance, or investment advice. Counterpose maintains no formal relationship with any vendor, regulator, or standards body referenced in this publication."
          }
        ],
        "heading": "Signal body",
        "section_id": "CP-SIG-58:body"
      }
    ],
    "citation_spans": [],
    "corpus_lifecycle": "published",
    "cross_references": [],
    "current_edition": "CP-SIG-58-ED-1",
    "disputes": [],
    "editions": [
      {
        "edition_id": "CP-SIG-58-ED-1",
        "edition_number": 1,
        "released_at": "2026-03-16T00:00:00Z"
      }
    ],
    "entities": [],
    "exports": [],
    "intersections": [],
    "lineage": [],
    "page_id": "PAGE-CP-SIG-58",
    "profile": {
      "admission_boundary": "Captured Counterpose signal republished from the GARPedia admitted pool. The editorial body is projected verbatim and unverified: GARPedia records that the signal was admitted and renders it, but asserts no independent citation, source, or anchor verification over its claims.",
      "id": "counterpose_publication",
      "label": "Counterpose Publication"
    },
    "projections": [],
    "provenance": {
      "source_kind": "captured_counterpose_signal"
    },
    "publisher": {
      "label": "Counterpose",
      "posture": "Counterpose publication surface. GARPedia renders captured signals from the admitted pool; it does not edit, adjudicate, or originate Counterpose editorial.",
      "publisher_id": "counterpose",
      "slug": "counterpose"
    },
    "record_id": "CP-SIG-58",
    "rendered_at": "2026-03-16T00:00:00Z",
    "route_slug": "/records/CP-SIG-58",
    "slug": "cp-sig-58",
    "sources": [],
    "status": "active",
    "title": "Authentication Infrastructure and the Identity Custody Surface: WorkOS at the Center of the AI Access Chain"
  },
  "schema_family": "garpedia.rendered_record",
  "schema_version": 1
}