Twindem Team FAQ for controlled AI delivery --:-- UTC
Twindem

Twindem FAQ

What kind of evidence does Twindem keep?

Evidence can include test output, logs, diffs, screenshots, command output, links, files, audit receipts, and run receipts. Evidence can be tied to a story, a run, or a review finding.

Evidence can include test output, logs, diffs, screenshots, command output, links, files, audit receipts, and run receipts. Evidence can be connected to a work item, a specific agent run, or a review finding.

Evidence also has a health state: unverified, healthy, warning, or failed. That helps the team separate "the agent says it is done" from "there is supporting proof attached."

Related questions

If our developers already use Codex or Claude Code, why do we need Twindem?

AI coding tools help individual developers move faster. Twindem adds the company layer: board items, phases, second-agent review, evidence, usage, cost, and audit events attached to the work.

Open this answer
What does controlled AI delivery mean in practice?

Controlled AI delivery means AI work starts from a delivery item, moves through a defined workflow, and keeps the useful record attached: runs, summaries, findings, evidence, usage, cost, comments, handoffs, and board events.

Open this answer
Why is the second agent important?

The same agent that produces the work should not be the only reviewer of that work. Twindem separates implementation and review so a second agent can challenge the output, inspect risks, open findings, and drive a fix loop before human approval.

Open this answer
Can Twindem turn architecture work into development tasks?

Yes. Architecture work in Twindem is not just a document. It can produce concrete development task proposals, with rationale, scope, dependencies, and evidence expectations, so the team can approve what should become delivery work.

Open this answer