TwinDocs
Build your Twin

Review and publish changes

Use the Twin workspace to check proposed business meaning, make a decision, and confirm what becomes usable.

The Twin can discover useful patterns, but a person decides what becomes shared business knowledge.

Organisation administrators use the Twin area to see what is known, review proposed changes, and follow each change towards publication.

Before you review

Make sure you can answer three questions:

  • What business outcome is this change meant to support?
  • Which source information should support it?
  • Who understands the meaning well enough to make the decision?

If you are not the right reviewer, leave the proposal open and ask the relevant business owner to review it.

1. Start from Overview

Open Admin → Twin, then choose Overview.

Overview shows the Twin's current state, what most needs attention, and the latest source refresh. Use it to decide whether you should review a proposed change, inspect source coverage, or explore published knowledge.

Choose How the Twin works when you need a reminder of the journey from source evidence to evaluated agent use.

2. Check the supporting sources

Open Source coverage before approving a change that depends on new or recently updated information.

Check that the intended sources are represented and that their latest refresh is suitable for the decision. A configured connection is not enough on its own; the Twin needs usable, traceable evidence from it.

Coverage is not approval

Source coverage tells you what the Twin can currently see. It does not decide whether a proposed definition, relationship, or process is correct.

3. Review the proposed change

Open Review changes, then choose a proposal.

The review panel separates the decision into clear questions:

  • What will change? Read the proposed meaning in business terms.
  • Why was it proposed? Check that the reason matches the intended outcome.
  • What evidence is available? Confirm that the proposal is grounded in the right sources.
  • What is the decision? Approve it, request changes, or reject it.

Use Start review when you want to show that someone is actively considering the proposal. Add a useful note when requesting changes or rejecting it so the next person knows what needs attention.

Only approve a proposal when its meaning, sources, exclusions, and expected use are clear.

4. Understand what happens after approval

Approval records a human decision. It does not automatically make the change available to every person or AI tool.

An approved proposal can be applied and published as a stable, versioned piece of Twin knowledge after its required checks pass. The exact published version must then pass the activation checks for its intended deployment before it becomes the active version.

Publication, activation, access, and evaluation remain separate decisions:

  1. Publish records a stable approved version.
  2. Activate selects the exact version that the configured deployment may use after its required checks pass.
  3. Access decides which people and connected tools may use it.
  4. Evaluate records whether it answers the intended business questions reliably.

Depending on your organisation's setup, the implementation team may carry out the publication and activation steps after your business review.

5. Inspect the governed business view

Open What it knows to inspect governed datasets, business relationships, and processes.

Check the name, description, state, and last refresh. Detailed identifiers are available for support, but the business meaning should be understandable without them.

This view helps you understand the Twin's constructed business context. It is not an authoritative release-readiness screen. A visible dataset or relationship may still need publication, activation, evaluation, or external access approval before a particular AI tool can use it.

6. Test before wider use

Ask a small set of questions with known answers:

  • one question the new knowledge should answer;
  • one edge case or exclusion it should handle; and
  • one question it should clearly decline because the evidence does not support it.

Review the answer, the exact version, the evidence references provided by the interface, and any supporting links. Where source freshness is shown, confirm it is suitable for the question. Make the knowledge more widely available only when the result meets the standard your business owner expects.

Do not approve on presentation alone

A well-written proposal can still use the wrong definition or source. Approve the business meaning and evidence, not the fluency of its wording.

On this page