Paths/Copilot Engineer/Team Adoption / Ground Rules
Write the Ground Rules
The assistant writes faster than anyone reads. Write the rules the team runs on so the speed does not become the risk.
Validator
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/adoption exists○
- File ~/adoption/guidelines.md exists○
- The rules state that a human reviews everything○
- The rules cover the tests and the secrets○
02Walkthrough
4 steps- 01
Create the adoption directory
The rules live together, where everyone can find them.
mkdir -p ~/adoption - 02
Write the review and the test rules
Everything the assistant produces is reviewed by a person, and the change comes with a test that fails without it.
echo '# Team guidelines for AI assisted work\n\n## The rules\n\n- a human reviews every change before it merges\n- every change comes with a test that fails without it\n- the person who merges it owns it, exactly as before' > ~/adoption/guidelines.md - 03
Write the secret rule
One rule, no exceptions, and no discussion needed when it is violated.
echo '\n## Secrets\n\nNo secret value is ever pasted into a prompt or into a file the assistant reads. If it would show up in the context, it does not go in.' >> ~/adoption/guidelines.md - 04
Verify and submit
cat the guidelines, then submit for validation.
cat ~/adoption/guidelines.md
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list