Skip to main content

Core concepts

Tiden is organized from company scope down to the quality artifacts inside a product.

Organization​

An organization owns members, billing, security policy, and one or more workspaces. Organization owners and admins manage members, invite links, workspace access, two-factor requirements, and billing.

Workspace​

A workspace is a collaboration boundary inside an organization. It contains products and workspace-level credentials such as LLM provider keys used by agents. Workspace members can have direct workspace roles or scoped access from their organization role.

Product​

A product is the main quality container. It owns:

  • Requirements.
  • Tests.
  • Components.
  • Branches.
  • Environments.
  • Releases.
  • Quality gate verdicts.
  • Error tracking issues and DSN keys.
  • Agent configurations and runs.

Each product has a short code such as PAY or AUTH. Tiden uses that code in display IDs such as PAY-12.

Main and branches​

main is the canonical branch for the product repository. Non-main branches are isolated workspaces for reviewing changes to requirements, tests, and components.

Branches use copy-on-write behavior:

  • Creating a branch does not duplicate the product repository.
  • Creating a new item on a branch keeps it branch-local.
  • Editing a main item from a branch creates a branch copy.
  • Deleting a main item from a branch records a branch deletion marker.
  • Merging applies reviewed changes back to main in one transaction.

Generated branches can be created by the CLI intent capture workflow or by agents. Review them the same way as human-created branches.

Requirements, tests, and components​

Requirements describe product behavior. They are hierarchical, typed, statused, prioritized, assignable, source-backed, and branch-aware.

Tests live in a test repository made of suites and cases. Test cases can have steps, tags, priority, type, layer, links to requirements, and branch-aware changes.

Components are product areas such as "Billing" or "Auth". They group requirements and tests and drive traceability and quality gate breakdowns.

Environments and releases​

An environment is a named target such as staging, production, or a preview environment. A release is a version record for a product, optionally associated with an environment.

Release creation is API/CLI friendly and idempotent by version plus environment. Unknown environments can be auto-created when a release references their slug.

Issues and telemetry​

Tiden has embedded error tracking. A product DSN lets runtime SDKs send error events to Tiden. Events are grouped into issues, linked to releases and environments when that context is present, and symbolicated with uploaded source maps for browser JavaScript.

DSN keys are separate from user API tokens. A DSN key can send events only to the ingest endpoint for its product.

Quality gate and traceability​

The quality gate computes a go/no-go verdict from requirements, tests, executions, component risk, and production issues. It can evaluate:

  • Current main.
  • A release.
  • A branch merge projection.

Traceability shows which requirements are covered by which test cases, grouped by component.

Agents​

Agents are product-level automations configured with inputs, credentials, and optional schedules or triggers. Agent runs can produce generated branches, artifacts, and event streams that your team can review.