Projects and repositories
A repository gives the council your code. A project gives the work a memory.
Repositories
Choose a folder from the repository chip in the sidebar. A conversation rooted there reads the branch and the diff into every request, so "review my changes" works without pasting anything. What the council may do in it is a property of the repository:
| Level | What it allows |
|---|---|
| read | Read the code and reason about it. Edits are refused, and it says so. |
| edit | Edit and create files without asking each time. No commands. |
| full | Everything, including the shell: the tests, the build, git. What a repository you add starts with. |
Lower it from the lock in the status bar, or:
A folder Valhalla does not know is read-only. Read what a member proposes before you widen it.
Snapshots and undo
Before every turn the conversation takes a snapshot of the working tree. Under every reply that changed something, a strip names the files and counts the lines, with Review to read the diff and Undo turn to put back exactly what that turn touched and nothing else. Undo can be redone.
Source control
Source control shows status, diffs, branches and history, and commits as you, with your git identity. It never forces and never waits on a prompt the window cannot answer. Each conversation can keep its own branch and directory, so two pieces of work do not collide.
Projects
A project is a shared brain for a piece of work: a brief everybody reads, a vault of its own knowledge, a crew of the members who belong at its table and and a mission. A project can be tied to one checkout, so every conversation in it starts there. Open a project on its hub to see where it stands.
Missions
A conversation has a goal. A project has a mission: what the whole piece of work is for, written as an ordered list of phases. Each phase has criteria that say when it is done, and the members who should carry it.
You do not have to write one from nothing. In any conversation inside the project, say what you are trying to build and ask the council to propose a mission. A member drafts the title, the phases, the criteria and the crew, and the draft shows up as a card. Nothing is saved until you press Set as the mission, and a later proposal can only add to what is there.
From then on every conversation in the project is sent the mission with each message, so a chat opened next week works from the plan the council saw today. When a criterion is met, a member ticks it and records the evidence. They cannot rename the mission, reorder it, delete from it or untick what you ticked. A phase with no movement for ten days is shown as stalled, and a member can offer to open a conversation for a phase with its crew and brief ready.
The mission is a file in the project's folder, so it can be committed and reviewed like the brief.