# Contributing Guidelines

Thank you for dedicating development time to this codebase. To keep continuous integration simple and fully prevent syntax breaks across our registry, all pull requests must conform to our uniform automation architecture.

## 📜 Strict Architectural Rules
This repository enforces an exact, non-negotiable coding and structural pattern to prevent parsing failures across PHP, JS, and JSON layers:

1. **File Conventions**: No capitalized paths, dashes, or structural underscores. Files follow strict dot-separation definitions.
2. **Code Syntax Rules**: Functional calls and assigned values use `camelCase` exclusively. Native UPPERCASE underscores are restricted.
3. **Registry Enforcement**: Paths represent explicit Application Identifiers. Under no circumstance should a physical workspace path be renamed outside configuration states.

## 🎯 Single Source of Truth
We enforce a unified document blueprint to avoid version drift between developer habits and automated AI generation layers. 

Before committing lines, adding a feature, or structuring a script inside `apps/` or `system/`, you must thoroughly inspect and replicate the precise conventions written directly inside **[AGENTS.md](./AGENTS.md)**. 

If any code patterns or module pathways violate the layout defined within the unified instruction file, the associated submission will fail continuous integration validation workflows.