How pages get written

Gini writes a page when something durable happens in a channel it's in. Not every message: most chat is not knowledge.

What makes it write

The test it applies is roughly: would someone need to know this in three months, and would they struggle to find it?

That catches:

• A decision, and the reasoning behind it
• A process someone explained in a thread because a newer colleague asked
• An ownership change: who's on what now
• A definition your team uses that an outsider wouldn't know
• A conclusion from a job Gini did that outlives the job

It doesn't catch banter, scheduling, "shipped it", or anything that's true for an afternoon.

What makes it revise

A page changes when the channel says it should. Someone reverses a decision, an owner changes, a process gets simplified: Gini updates the page and records what changed and when.

The revision history is on the page. This matters more than it looks: "we decided X, then in June we changed to Y because Z" is the actual shape of most institutional knowledge, and a wiki that only shows the current state loses the half that explains it.

Steering it directly

You don't have to wait for Gini to notice.

Write this down.

@Gini write this down: anything touching billing goes to Priya first, then legal. Not the other way round.

Fix a page.

@Gini the on-call page is wrong. We moved to weekly rotations in June, not fortnightly.

Keep something out.

@Gini don't write anything from this channel down.

@Gini forget what I said about the acquisition.

All of these work in the channel, and all of them take effect immediately.

Editing pages yourself

Open app.ginicomputer.com → Wiki. Every page can be edited or deleted by anyone on your team.

Your edits stick. Gini won't quietly overwrite a page a person has corrected: if the channel later contradicts your edit, it flags the conflict rather than deciding for you.

What Gini won't put in a page

• Anything from a channel it hasn't been invited to
• Anything you told it to forget
• Message content that isn't knowledge: the raw chat isn't stored, only what was learnt from it
• Credentials, keys, or tokens, wherever it saw them

Data handling covers what's stored and for how long.

Keeping it useful

Two habits do most of the work.

Read it once a month. Ten minutes. You'll find one page that's wrong in a way that would have cost someone an afternoon.

Correct in the channel, not the page. Fixing the page fixes the page. Saying it in the channel fixes the page and teaches Gini the correction, so the next related page is right too.