tenax labsGrounded intelligence, with receipts.
Tenax is the substrate: a write plane that captures sources verbatim, a lake that keeps them, an entity graph that resolves who is who, and a read plane that serves answers no model had to guess at. Products sit thin on top. Nothing is summarised without a citation you can follow.
A platform, not a product.
Each plane is a thing you operate, with exactly one door per boundary — one holder of lake credentials, one path for outbound mail, one threshold every external request crosses. A product that wants a second path does not get one; that constraint is what makes the trust guarantees checkable rather than aspirational.
Capture
Fetches a source and commits the raw body verbatim, before anything interprets it.
The corpus
The lake behind a single door — the only holder of its credentials, and the platform's one linearization point.
The graph
Canonical entities and document-anchored edges, each carrying how it was resolved.
Serve
Envelope, cursor, and notice contract, metered per call. It degrades visibly or refuses — never silently.
Compose
Witnessed evidence in, grounded artifacts out. It holds no credentials and reaches the corpus only through the door.
The gate
Host resolution, rate limits, auth, audit, roles. One crossing, one record of it.
Three of the four filings name the same counterparty, and the fourth is silent on the question entirely.
Not supported by the sources: no filing states why the fourth omits it.
… the obligations described in Item 1.01 were assumed in full by the counterparty named therein.
A house, and its papers.
Tenax is the house; each product is an endorsed sub-brand with its own name and its own mood. The roster below states what is live and what is not — see /civic and /news.
Crier
Legislative and government sources, served as a browsable public surface and through the MCP product.
Herald
The news vertical. Its public web surface is served; its MCP surface is registered, discoverable, and deliberately not yet usable.