This document describes public responsibilities, not Tessen's private production topology.
Primary Tessen product.
Company and system story.
Public developer website: API, Code, Connect, Project Zero, Node and documentation discovery.
Authenticated developer workspace: overview, credentials, usage and developer controls.
Independent public operational status for customer-facing Tessen systems.
The intended experience is one Tessen identity across developer surfaces. Sessions can remain host-scoped; sharing an identity does not require one broad cross-subdomain cookie.
sequenceDiagram
participant D as Developer Tool
participant I as Tessen Identity
participant G as Tessen Gateway
participant R as Eligible Intelligence
participant A as Accounting
D->>I: authenticate / present credential
I-->>D: developer authority
D->>G: request using tessen/project-zero
G->>G: entitlement + policy checks
G->>R: eligible routed request
R-->>G: response
G->>A: usage / cost metadata
G-->>D: response
A sustainable $0 preview still requires:
- authentication;
- entitlement checks;
- rate and concurrency controls;
- usage and underlying cost accounting;
- abuse controls;
- provider/route health;
- operational kill switches.
Node is a participation surface, not an implicit extension of a developer session. Participation and local execution remain explicit.