Latch
The identity substrate
StatusBuildBuilt
01What it does
Latch is the shared identity/session substrate, a provider-interface pattern plus a signed-cookie session contract every tool with a login surface ports into its own runtime, so which OAuth provider verifies a sign-in is a config line, never a per-tool rebuild.
Without it, every tool that grows a login surface solves session auth independently, each one a fresh chance to get the provider handshake or cookie codec wrong.
03Who it works with
A substrate member is called, never run. Everything below reads its declared contract at the moment it needs it, which is why it has no step of its own in any workflow.
- ConsoleOperates (reference port)Console's Google OAuth pilot is the first/reference consumer, calling the same establishSession() mint point
- ManifoldOperates (precedent)Same substrate shape, sibling graduation under Lathe
- ConcordGatesA tool hardcoding its own provider handshake or cookie codec instead of calling through Latch is captured as open drift
- WardOperates (sibling layer)Ward brokers machine credentials one layer beneath Latch's human-identity layer; neither reaches into the other
Others on the substrate plane