asshole

Preventing unauthorized changes to core configs requires enforcing a documentation adherence protocol that forces AI agents to read project docs before modifying systems like Firebase config, Auth, or Electron IPC.

A documentation policy for core system code review is a formal decision flow that mandates reading project documentation before applying changes, ensuring modifications align with documented patterns and hierarchy.

When modifying Firebase or Auth configs with conflicting documentation, use a conflict resolution hierarchy that guides how to handle differing sources and prompts for user confirmation when documentation is missing or unclear.

Yes, you can use a guided prompt protocol for deployment and styling safety to provide structured prompts during uncertainty, ensuring changes are doc-aligned before touching core configurations.

You should escalate to a user during core config risk management when project documentation is missing, unclear, or insufficient to confirm alignment with project conventions for systems like Electron IPC.