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

Twindem FAQ

What happens when the reviewing agent finds an issue?

Review findings are structured records with severity, title, body, file path, line range, status, resolution note, and links to the related run and work item. Findings can move from open to fixed, resolved, or dismissed.

Review findings are structured records, not loose chat messages. A finding can have a severity such as blocker, critical, high, medium, low, or info. It can include a title, body, file path, line range, status, resolution note, and links to the related run and work item.

Findings can move through states such as open, fixed, resolved, or dismissed, so the team can see whether the review loop actually closed.

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