Git Exclusion Policy for Genesis Workspace
Summary
This policy defines the exclusion of large, transient JSON artifacts generated during bootstrapping or data ingestion processes from the project’s version control. It specifically mandates the ignoring of files within the genesis-workspace/ directory to maintain repository hygiene.
Details
During the development and initialization phases of the Sokrates project—specifically during “genesis” tasks involving data processing or initial environment setup—the system generates various JSON files within the genesis-workspace/ directory. These files often contain large datasets, intermediate processing states, or raw outputs that are not required for the core logic of the application and would unnecessarily bloat the Git repository if tracked.
To enforce a clean working tree and prevent the accidental commitment of these artifacts, the project configuration includes specific rules in the .gitignore file. A key decision was made to explicitly add the pattern genesis-workspace/*.json to the ignore list.
The implementation of this law followed a diagnostic check of the repository’s untracked files, where it was observed that the only remaining noise in the git status output originated from these JSON files. By formalizing their exclusion, the development environment ensures that only source code, configuration files, and essential assets are tracked, while large-scale data artifacts remain local to the developer’s environment or the specific deployment instance.
This exclusion is part of a broader effort to maintain a “clean tree” state, ensuring that sokrates-ctl and other diagnostic tools can accurately report the state of the repository without interference from transient data files.