REFERENCE

Security boundaries and canonical Tenzarch language.

Use consistent terminology across the website, product, documentation, and developer surfaces, and keep privileged credentials inside the correct trust boundary.

SECURITY

Protect wallet identity, developer credentials, and backend secrets.

Wallet secrets

Tenzarch should never require a private key or recovery phrase.

Developer API Keys

Store programmatic credentials server-side and scope them narrowly.

Backend secrets

Database connection strings and privileged service credentials belong only in backend environment configuration.

Frontend boundary

Do not place privileged secrets in browser-exposed environment variables.

TERMINOLOGY

Canonical execution language.

Tenzarch Execution Network

The coordination system connecting workload demand, execution state, orchestration, routing, distributed capacity, observability, and results.

AI Agent

A user-facing AI experience that submits workloads.

AI Execution

A reusable developer-facing execution capability.

Execution Job

The trackable record of an individual workload.

Workflow Run

The orchestration record coordinating execution lifecycle around a Job.

Execution Node

Distributed processing infrastructure eligible for assignment under network conditions.

Free Execution Node

The wallet-associated participation entry point.

Execution Credits

Usage accounting for workload execution.

Node Rewards

A separate program for qualifying node participation.

Node Points

The accounting unit used by the Node Rewards program.