Results and sources

A result you can't check is a result you have to trust, and trusting an AI on a number you're about to put in front of your board is a bad trade. Gini's output is built to be checked quickly.

Source chips

Facts come with the thing they came from attached: a ticket number, a thread link, a row, a commit. Click it and you're looking at the source.

The habit worth building: on anything you'll repeat to someone else, click one chip. Not all of them. One. It takes ten seconds and it tells you whether the shape of the answer is right.

If a claim has no chip, it's Gini's own reasoning over things that do. That's legitimate ("these two clusters are probably the same root cause" isn't a fact you can cite), but it's the part to read closely.

Files

Longer output arrives as a file in the thread: a spreadsheet, a document, a CSV. Gini writes into the format the work belongs in rather than pasting 200 rows into Slack.

Files persist in Slack under your workspace's normal retention. Ask Gini to put a file somewhere durable (Drive, Notion) and it will, with your access to that tool.

Changes in your tools

When a job changed something, the result links to what changed: the Linear issue, the HubSpot record, the PR. Follow the link and you're looking at the actual object, not Gini's description of it.

This is the difference between "I've updated the CRM" and "I've updated the CRM: here are the three records." Gini does the second.

The steps behind it

Every run keeps a record: what Gini did, in what order, which tools it called, what came back, where it waited for you.

Open it from app.ginicomputer.com → the run. Worth doing when a result surprises you. The answer is usually visible in the steps, and it's usually that Gini read a narrower or wider slice of data than you assumed.

Run records are kept for 90 days by default.

Reading a result honestly

Three things to look at before you act on one:

The scope. Gini says what it looked at: "read 214 tickets from July". If that's not the window you meant, the conclusion is about the wrong month.

The unsourced claims. Where the chips stop is where the interpretation starts.

What it says it didn't do. Gini flags what it skipped and why: a tool it couldn't reach, records it couldn't parse, a permission it didn't have. That sentence is easy to skim past and it's often the most important one on the screen.