Working with Gini
When Gini gets it wrong
Stopping a run, correcting a wrong result, and making the correction stick for next time.
It will. It's a model doing real work against messy data, and some percentage of the time the answer is wrong, the approach is wrong, or it confidently misread what you asked for.
The design assumption isn't that Gini is always right. It's that you can catch it cheaply and that nothing expensive happens without you.
Stop a run
Say so in the thread: "stop", "cancel that", "no, wrong approach". Gini halts and confirms.
You can also stop it from app.ginicomputer.com, on the run itself.
Nothing that needed an approval has happened unless you clicked it. If a reversible change did land before you stopped it, Gini tells you exactly what and offers to undo it.
Correct a wrong result
Reply in the thread. Be specific about what's wrong, not just that it's wrong:
- "That's last quarter, I meant this one."
- "You counted trials as customers. Don't."
- "Priya doesn't own billing any more, Sam does."
Gini redoes the affected part rather than the whole job, and the correction applies to the rest of the run.
Make the correction stick
Here's the part people miss. A correction in a thread fixes that result. Telling Gini it's a standing fact fixes every result after it.
Revenue always means net of refunds. Don't ask me again.
We call the enterprise tier "Scale" internally. Anything about "enterprise" means that.
Never post to
#general. Ask me where instead.
Gini keeps these. Check what it's holding at app.ginicomputer.com → Wiki, and edit or delete any of it. See What Gini remembers.
If the correction is about how to do a job rather than a fact (always check the CRM before drafting, always cc the account owner), that's a skill.
When a run fails
Gini posts what it tried and where it stopped. It does not silently retry a sensitive action.
Most failures are one of four things:
| What you see | Usually |
|---|---|
| "I couldn't reach HubSpot" | The connection expired. Fix it |
| "I don't have access to that" | Your own account can't see it either |
| Stopped partway with no error | Out of credits. Check the balance |
| A wrong answer, confidently | Wrong scope. Open the run and read what it looked at |
If something did go out
A failed run that had already sent an email or made a change says so. If something reached a customer that shouldn't have, tell us at team@ginicomputer.com. The run record has exactly what happened and we can help you piece together the rest.
When it keeps getting the same thing wrong
That's a signal, and usually not about the model. Common causes, in the order they're worth checking:
It's missing context. It's working from a channel that doesn't contain the thing it needs. Point it at the right channel, or write the fact down for it.
It's reading a stale source. A wiki page that's out of date, a spreadsheet nobody maintains. Fix the source and the answer fixes itself.
Your ask is genuinely ambiguous. If two competent people would read your message differently, Gini has to pick one. Asking for work covers phrasing.
If none of those and it's still wrong, tell us with a link to the run. That's a bug on our side and we want it.