Skip to main content

Product guide overview

This section documents the active customer-facing product areas in Tiden.

AreaWhat it is for
Organizations and workspacesMembers, roles, workspace access, billing, security policy
ProductsProduct quality repository and readiness
RequirementsHierarchical product requirements with sources and history
TestsSuites, cases, test metadata, steps, and requirement links
ComponentsProduct areas used for grouping and risk
BranchesCopy-on-write review flow for requirements, tests, and components
Environments and releasesTargets and version records for delivery context
Quality gatesRelease, branch, and main readiness verdicts
AgentsAutomated product changes and generated branch review
Error trackingRuntime issues, DSNs, telemetry SDKs, and source maps
Settings and securityProfile, API tokens, MFA, credentials, and product settings
  1. Keep main clean and use branches for proposed changes.
  2. Link tests to requirements as soon as the expected behavior is known.
  3. Use components consistently so traceability and risk views stay useful.
  4. Create releases from CI with the same release name your telemetry SDKs use.
  5. Connect error tracking before production rollout.
  6. Use quality gates as a review signal before shipping.
  7. Review generated branches before merging agent output.