Lesson 5: Where things belong

In this lesson: where work is saved so that colleagues and agents find it later.

Chat is the working conversation. Agents treat it as a cache: what stays only in a chat is lost to everyone else. Each kind of result has its home:

What	Where it belongs
Shared knowledge: procedures, context, what you have learned	the Organization’s Knowledgebase
Plans, their status and who is responsible	the Organization’s Mission Control
An open problem or an uncertainty	a GitHub Issue in the repository it concerns
Software and documentation	a repository on GitHub, changed by a pull request
A finished file that belongs in no repository, such as a presentation	Files of the Environment
Personal matters	your Personal Environment, never a Work Environment

Every change to a repository goes as a pull request. If you can only read the repository, the agent writes the proposal as an issue there and mentions who can make the change. Your Organization may call its Modules differently; the agent finds them in the Organization’s own instructions and documents.

Your task

Pick one thing from your recent work that a new colleague would need to know: a term, a step of a procedure or a rule. Write it down in two or three sentences. Then send in Chat:

I want to save this for colleagues: [your two or three sentences].
Tell me where it belongs in our Organization (Knowledgebase, Mission
Control, an issue or Files) and why. Check whether something similar
already exists. Do not save anything yet.

Done means: you have one small, real piece of work and you know where it belongs. You will have it saved in lesson 7.