Ground rules

Ground Rules for AI and Automated Agents

These rules apply to every AI, agent, script, and automated tool working in this workspace.

1. Know the two workspace areas

• Workspace root: /home/soulwax/workspace/engines/unity/minecraft
• Unity project and Git repository: /home/soulwax/workspace/engines/unity/minecraft/Minecraft-HD
• Relative Unity project path: ./Minecraft-HD

Path names are case-sensitive. The correct directory name is Minecraft-HD, not MINECRAFT-HD.

The Minecraft-HD directory is both the Unity project root and the Git repository root. It is the source of truth for the game. All production code, game assets, Unity metadata, packages, project settings, tests, and documentation required to build, run, maintain, or release the game belong there.

Before running a project or Git command, an agent must confirm that it is targeting ./Minecraft-HD. The workspace root itself is not the game repository.

2. Keep authoritative documents in Docs

The user has moved the former parent-directory documents into the repository. The authoritative locations are Docs/MASTERPLAN.md and Docs/GROUND_RULES.md. CLAUDE.md remains at the repository root by explicit user choice. Maintain those locations; do not recreate competing parent-directory copies. This supersedes the former prohibition on storing these documents in the repository.

Production documentation, maintained plans and project guidance belong in Docs/, except the root CLAUDE.md entry point. Transient scratch files, tool-call logs and chat transcripts are not maintained documentation and must not be added as incidental source changes. None of these documents belongs under Unity’s Assets/ directory.

3. Protect the repository boundary

• Make project and documentation changes inside Minecraft-HD; the parent directory is not the project.
• Do not initialize another Git repository in the workspace root or inside a subdirectory of Minecraft-HD.
• Do not move the existing .git directory.
• Maintain one authoritative copy of each document at its declared location; do not use symlinks or broad Git commands to pull unrelated parent-directory material into the repository.
• Treat Unity-generated directories such as Library, Temp, Logs, Obj, Build, Builds, and UserSettings as non-source content and keep them ignored.

4. Use only the global Git identity

When a commit, signature, tag, or push is explicitly requested:

• Use the user’s existing globally configured Git identity and signing configuration.
• Do not set or override user.name, user.email, signing keys, or signing behavior in the repository’s local Git configuration.
• Do not pass temporary identity overrides on the command line or through environment variables.
• Create signed commits and signed tags whenever the requested operation supports signing and the global configuration provides it.
• Push using the repository’s configured remote and the global user’s credentials.
• If the global identity or required signing configuration is missing or fails, stop and report the problem. Do not invent an identity, disable signing, or silently create an unsigned replacement.

These Git rules do not grant permission to commit, tag, or push. They define the identity and signing requirements when the user has authorized those actions.

5. Resolve conflicts in favor of these boundaries

If an older document directs maintained plans or project guidance to the parent directory, update it to the layout above. Explicit user instructions take precedence over the historical workspace arrangement. Keep temporary artifacts out of maintained source changes.