Tiden is an intent verification platform designed for engineering teams shipping agent-written code, keeping versioned specifications beside code.
What the product does and how it is positioned
Tiden reads repository codebases to catalog components and functional specifications, highlighting which behaviors remain unproven by tests.
The platform enforces working contracts during coding agent sessions, helping reduce completion until all declared promises pass automated verification.
Source-supported ways to use the product
Engineering teams using agents like Claude Code or Cursor can enforce test verification against specified intent before closing tasks.
Teams can maintain versioned specifications directly alongside code changes, receiving drafted updates automatically on every merge.
The documented workflow, where available
Connect GitHub to allow Tiden to analyze source files, extract specifications, and flag areas without test coverage.
Establish the working contract and specific behavioral promises that the coding agent must fulfill during the session.
Execute automated tests to prove each promise, keeping the coding session open until all requirements are met.
Inspect the branch review screen to verify which lines of code changed and which automated tests prove the updated specification.
Review release-level coverage verdicts across components and route production errors back to agents for resolution.
Tiden functions alongside agentic coding tools by separating code generation from intent confirmation. When autonomous agents generate feature code, passing unit tests alone may merely indicate that the code satisfies the agent's internal assumptions rather than the developer's original goals. Tiden addresses this discrepancy by converting requirements into explicit contracts composed of measurable promises.
As development branches proceed toward production, Tiden maintains parity between implementation and behavioral documentation. Every merge triggers drafted specification updates that track Git modifications against existing functional contracts, so that missing test coverage and regression risks are surfaced directly on release dashboards.
Checks to run with your own material and workflow
What was checked and when
Answers based on the source-checked product record
Tiden verifies that agent-written code fulfills requested specifications and maintains versioned behavioral contracts alongside codebase changes.
Tiden is documented to work beside coding agents including Claude Code, Cursor, GitHub Copilot, and Codex.
Tiden connects with GitHub, Jira, Linear, Notion, and Azure DevOps to incorporate project context and code history.
The active coding session remains blocked and cannot close until the remaining open promise is proven by a passing test.
Tiden drafts updates to the functional specification on every merge, including merges that bypassed the Tiden platform directly.
