tovio.Sign inSee it work

From an assigned task
to a reviewed change.

See how TOVIO fits into the work you already do. Follow one checkout fix through agent authority, review context, conflict resolution, and a team that still uses Git.

TOVIO is prelaunch. These examples describe supported product behavior; they are not a live service or an invitation to public early access. Check availability

Give the task
a boundary.

A maintainer asks an agent to raise checkout’s timeout. The task needs access to checkout, a finite lifetime, and a review before it reaches main.

  1. Authorize the agent

    Register its identity and grant the required paths and operations, with an expiry. Protected reads also require the relevant keys and clearance. A request written in a prompt is not an access boundary.

  2. Work in its lane

    The agent edits within its granted scope. TOVIO checks TOVIO-mediated operations; the agent’s host filesystem, shell, and network need their own isolation.

  3. Inspect before accepting

    Review the diff, agent provenance, applicable checks, and any captured context. Recording a commit does not by itself accept it onto a protected destination.

The delegation to define

Path scope
src/checkout/**
Operations
The minimum reads and writes needed for this task
Lifetime
A finite grant, revoked when no longer needed
Landing
Subject to main’s configured review and policy gates

Illustrative grant brief, not a token or CLI output.

Outcome: bounded authority, attributable work.

The capability controls what the agent may do through TOVIO. Signed provenance identifies agent-authorized work; it does not establish that the code is correct.

Follow the agent guide

Review the change.
Keep the request in view.

The diff shows a timeout changing from 30 to 60. A captured transcript supplies another useful detail: the original request said to leave retries alone.

  1. Choose the session source

    Check the repository’s capture policy and select the transcript explicitly when sessions overlap. Automatic discovery is a heuristic.

  2. Inspect code and context

    Read the recorded request and available tool activity alongside the diff. An observed transcript is unattested and self-reported; its association is not proof that the session produced the code.

  3. Check the affected interface

    For supported languages, use semantic diff and impact analysis to inspect interface changes and recorded dependents. Run the relevant tests separately.

Checkout timeoutIllustrative review · not captured output
Recorded request

“Raise the checkout timeout to 60 seconds. Leave the retry count alone.”

src/checkout/retry.ts
- const TIMEOUT = 30;
+ const TIMEOUT = 60;
  const RETRIES = 3;
Review question

The timeout changed. Did the implementation also preserve retries?

Observed transcript · unattested, self-reported
Capture, association, and privacy Read the underlying flow
Review tools · illustrative command sequence
tovio log --session chg:9fk2m1
tovio semantic diff
tovio semantic impact

The Change ID is illustrative. Semantic relationships are extracted syntactically and may be incomplete. Neither a transcript nor semantic analysis proves execution or correctness.

Two valid intentions.
One explicit decision.

Another change raises the same timeout to 90. TOVIO preserves the common base and both sides as a conflict object so a reviewer can decide deliberately.

  1. Inspect the disagreement

    Look at the base and both versions. A stored conflict keeps the disagreement visible while supported independent work continues.

  2. Choose or hand-merge

    Keep a side or record a combined result. Matching conflicts can reuse a recorded resolution through supported paths; a different conflict needs a new decision.

  3. Satisfy the landing gates

    Unresolved conflicts in the source tip, target tip, or merge base block landing. Resolving the VCS disagreement still leaves build and test verification to do.

Common base: TIMEOUT = 30

Our changeTIMEOUT = 60
Their changeTIMEOUT = 90

Both alternatives remain available. In this example the reviewer deliberately keeps our side.

Example · explicit resolution
tovio resolve src/checkout/retry.ts --ours
Outcome: a recorded resolution.

The decision is inspectable and may be reused when a supported operation encounters the same conflict.

Explore the change and conflict model

Adopt at
your team’s pace.

A pilot does not require the whole team to change tools. Choose the compatibility path that matches your goal, then test its translation boundaries.

Evaluate a separate copy

Import local Git history into a fresh TOVIO repository, materialize the working tree, and compare representative branches, tags, and assets.

Import guide

Keep the existing remote

Use the namespaced bidirectional bridge for ongoing exchange. Reconcile explicitly; do not assume every native permission or review concept round-trips into Git.

Bridge workflow

Keep compatible Git tools

A configured Forge can expose Git smart HTTP. Check which operations and native capabilities are available through that interface.

Client boundary

Protected files export as ciphertext. Git compatibility does not turn Git’s access model into TOVIO’s cryptographic permission model.

Choose one real task.
Evaluate it end to end.

Define what success looks like for your repository, the controls you require, and the evidence you need before adoption.

Plan an evaluationTalk through your workflow