Display mode and language¶

ThothII can run with its own application header (full) or inside an integrated portal (embedded). Display mode and authentication are separate choices.

Installation	Display	Authentication
Standalone local instance	full	Local ThothII account
Standalone server	full	Local accounts or configured OIDC provider
Integrated portal	embedded	Identity verified by the portal's trusted server proxy

Standalone setup¶

Follow the complete Italian or English installation procedure. It explicitly selects --shell-mode full --shell-default-locale en and separates configuration, credentials, initial migrations and startup. Do not skip those steps by running setup alone.

The authored installation descriptor contains:

shell:
  mode: full
  defaultLocale: en

Use it for an Italian initial interface. Existing browser language preferences can override that initial value. Full mode remembers language and theme in the browser.

For an existing installation, preserve the current descriptor and edit only the intended settings; do not rerun setup to overwrite it. With a current host tht binary:

tht --installation /absolute/path/thothii-installation.yaml installation generate
tht --installation /absolute/path/thothii-installation.yaml start
tht --installation /absolute/path/thothii-installation.yaml status
tht --installation /absolute/path/thothii-installation.yaml doctor --json

Generation updates derived configuration; it does not start services. start applies the installation's normal lifecycle and is not guaranteed to touch only the frontend. Follow the deployment's maintenance procedure and retain its network, authentication and model settings. Do not edit generated files or remove persistent volumes.

Authentication and embedded deployments¶

Full mode does not configure login by itself. See local authentication or OIDC, with Authentik as a provider option.

Embedded mode requires a compatible portal integration, not just a descriptor toggle. The portal owns login/logout and supplies a server-verified identity. A presentation adapter does not authenticate users. The core must not be reachable by a route that bypasses the trusted proxy. Do not add a second OIDC login to an already authenticated upstream deployment.

Portal implementation details belong to the developer integration reference in the repository, not to the standalone installation procedure.

Three different languages¶

• Interface language controls labels, forms and application messages.
• Session interaction language is captured when a session is created. Resuming it retains that language even if the interface language changes later.
• Workspace language concerns domain content and retrieval; switching the interface does not translate Evidence, SQL, identifiers or database values.

In embedded mode the interface follows the portal's language and theme. A portal language change may reload the page. Saved session artifacts remain available, but resuming work is explicit; a reload does not by itself request a new model generation.