CLAUDE.md@examples/gradle-multimodule/core · git:20260911.a884ca8 · 2026-09-11 · sha256 85543b1a1e52389b

CLAUDE.md@examples/gradle-multimodule/core git:20260911.a884ca8A

Immutable. This exact content never changes and is served at /api/v1/blob/85543b1a1e52389b.

<!-- VIBETAGS-START -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
  <locked_files>
    <file path="com.example.gmm.core.IrNode">
      <reason>Core IR node shape is depended on by every downstream module</reason>
    </file>
  </locked_files>
  <security_elements>
    <element path="com.example.gmm.core">
      <aspect>Node identity is a security boundary: never build an IrNode from unvalidated external input, and never expose its raw name in a URL or log line.</aspect>
    </element>
  </security_elements>

<rule>Elements listed in <security_elements> are security-critical. Never weaken their security properties. Every proposed change must be explicitly reviewed for security impact.</rule>
  <scoped_rules>
    <note>Detailed per-element guardrails for the elements below live in scoped rule files that load automatically when the matching source file is opened. Unless an entry carries an explicit path, its file is .claude/rules/{path, every non-alphanumeric character replaced by &#39;-&#39;}.md. Consult the file before modifying an element.</note>
    <element path="com.example.gmm.core"/>
    <element path="com.example.gmm.core.IrNode"/>
  </scoped_rules>

<rule>When you work on any element listed in <scoped_rules>, open its referenced rule file and apply the guardrails there. The rule files are the authoritative source for those elements.</rule>
</project_guardrails>

<rule>Never propose edits to files listed in <locked_files>.</rule>
<!-- VIBETAGS-END -->