CLAUDE.md@examples/gradle-multimodule/platform · git:20260821.18c0b37 · 2026-08-21 · sha256 2e507c13d6728a91
CLAUDE.md@examples/gradle-multimodule/platform git:20260821.18c0b37A
Immutable. This exact content never changes and is served at /api/v1/blob/2e507c13d6728a91.
<!-- VIBETAGS-START -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<locked_files>
</locked_files>
<contextual_instructions>
</contextual_instructions>
<audit_requirements>
<file path="com.example.gmm.platform.Telemetry">
<vulnerability_check>PII in metric labels</vulnerability_check>
</file>
</audit_requirements>
<rule>
If you are asked to modify any file listed in <audit_requirements>, you must first silently analyze your proposed code for the listed <vulnerability_check> items. If your code introduces these vulnerabilities, you must rewrite it before displaying it to the user.
</rule>
<observability_instrumentation>
<element path="com.example.gmm.platform.Telemetry">
<metric>reactor.render.count</metric>
<metric>reactor.render.duration</metric>
<note>Metric names are a published contract; renaming one breaks every dashboard reading it</note>
</element>
</observability_instrumentation>
<rule>Elements listed in <observability_instrumentation> publish metrics, traces, or log statements that downstream dashboards and alerts depend on. Never remove or rename instrumentation without flagging the corresponding dashboard update.</rule>
<feature_flag_elements>
<element path="com.example.gmm.platform.FeatureGate">
<flag>reactor.parallel-render</flag>
<default_value>false</default_value>
</element>
</feature_flag_elements>
<rule>Elements listed in <feature_flag_elements> are gated by a feature flag. Always preserve the flag check — never assume the flag is always active.</rule>
</project_guardrails>
<rule>Never propose edits to files listed in <locked_files>.</rule>
<!-- VIBETAGS-END -->