CLAUDE.md@examples/gradle-multimodule · git:20260925.82b44e7 · 2026-09-25 · sha256 b65e121adde1ff29

CLAUDE.md@examples/gradle-multimodule git:20260925.82b44e7A

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

<!-- VIBETAGS-START -->
<!-- VIBETAGS-MODULE: annotations-showcase -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
  <locked_files>
    <file path="com.example.payment.PaymentProcessor">
      <reason>Tied to legacy database schema v2.3. Changes will break production payment processing. Contact the payments team before modifying.</reason>
    </file>
    <file path="com.example.security.SecurityConfig">
      <reason>CRITICAL: Security configuration managed by DevOps team. Any changes require security review and approval ticket SEC-XXXX</reason>
    </file>
    <file path="com.example.security.SecurityConfig.getEncryptionAlgorithm()">
      <reason>Encryption algorithm tied to compliance requirements (PCI-DSS)</reason>
    </file>
    <file path="com.example.security.SecurityConfig.getKeyRotationHours()">
      <reason>Key rotation period mandated by company policy</reason>
    </file>
    <file path="com.example.security.SecurityConfig.getMaxLoginAttempts()">
      <reason>Max login attempts set by security team to prevent brute force</reason>
    </file>
    <file path="com.example.security.SecurityConfig.validateToken(java.lang.String)">
      <reason>Token validation must match auth server exactly. Changes will break all client authentication</reason>
    </file>
    <file path="com.example.service.OrderService.calculateTax(java.lang.String,double)">
      <reason>Tax calculation uses Avalara API integration. Credentials and endpoint configuration managed by finance team.</reason>
    </file>
    <file path="com.example.service.OrderService.processPayment(java.lang.String,double)">
      <reason>Payment processing uses Stripe API v2024.10. Changes require PCI compliance review.</reason>
    </file>
    <file path="com.example.service.OrderService.validateOrder(java.util.Map&lt;java.lang.String,java.lang.Object&gt;)">
      <reason>Order validation implements 47 business rules. Last changed in Q2 2024 after 3-month testing cycle. DO NOT MODIFY without running full test suite.</reason>
    </file>
  </locked_files>

  <audit_requirements>
    <file path="com.example.database.DatabaseConnector">
      <vulnerability_check>SQL Injection</vulnerability_check>
      <vulnerability_check>Thread Safety issues</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>
  <ignored_elements>
    <file path="com.example.internal.GeneratedMetadata">
      <reason>Auto-generated at build time. Manual edits are overwritten on every build.</reason>
    </file>
  </ignored_elements>

<rule>Never reference or suggest changes to any element listed in <ignored_elements>. Treat these as if they do not exist.</rule>
  <pii_guardrails>
    <element path="com.example.database.DatabaseConnector.password">
      <reason>Database credential - never log or include in error messages</reason>
    </element>
    <element path="com.example.database.DatabaseConnector.username">
      <reason>Database credential - never log or include in error messages</reason>
    </element>
    <element path="com.example.service.InventoryService.customerId">
      <reason>Customer identifiers linked to purchase history — PII under GDPR</reason>
    </element>
    <element path="com.example.service.NotificationService.sendEmail(java.lang.String,java.lang.String,java.lang.String)">
      <reason>Email address is PII under GDPR - never log the recipient address</reason>
    </element>
    <element path="com.example.service.NotificationService.sendSMS(java.lang.String,java.lang.String)">
      <reason>Phone number is PII - never log the destination number</reason>
    </element>
    <element path="com.example.service.OrderService.generateOrderConfirmation(java.lang.String)">
      <reason>Output contains customer shipping address and contact details (PII)</reason>
    </element>
    <element path="com.example.strategy.impl.CreditCardStrategy.cardNumber">
      <reason>PCI-DSS cardholder data - never log or expose in suggestions</reason>
    </element>
    <element path="com.example.strategy.impl.CreditCardStrategy.cvv">
      <reason>PCI-DSS security code - never log or expose in suggestions</reason>
    </element>
    <element path="com.example.strategy.impl.CreditCardStrategy.expiryDate">
      <reason>PCI-DSS cardholder data - never log or expose in suggestions</reason>
    </element>
  </pii_guardrails>

<rule>
  Never include runtime values of elements listed in <pii_guardrails> in logs, console output, external API calls, test fixtures, mock data, or code suggestions. Treat their values as strictly confidential.
</rule>
  <core_elements>
    <element path="com.example.security.SecurityConfig">
      <sensitivity>Critical</sensitivity>
      <note>This is a security manager. Any single-line change can compromise the entire project.</note>
    </element>
    <element path="com.example.service.InventoryService.releaseReservation(java.lang.String)">
      <sensitivity>High</sensitivity>
      <note>Must be called as the exact inverse of reserveStock. Pair changes to both methods together.</note>
    </element>
    <element path="com.example.service.InventoryService.reserveStock(java.lang.String,int,java.lang.String)">
      <sensitivity>Critical</sensitivity>
      <note>Reservation logic handles concurrent requests via optimistic locking. Took 18 months to get right under high load — do not refactor without running the full concurrency test suite.</note>
    </element>
  </core_elements>

<rule>Elements listed in <core_elements> are well-tested core components. Make changes with extreme caution and verify comprehensive test coverage before proposing modifications.</rule>
  <security_elements>
    <element path="com.example.security.SecurityConfig">
      <aspect>authentication</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. An elements entry lists names under a shared prefix: in="a.b" listing C, D means a.b.C and a.b.D. 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>
    <elements in="com.example">NotificationService</elements>
    <elements in="com.example.compliance">GdprService</elements>
    <elements in="com.example.concurrent">SessionCache</elements>
    <elements in="com.example.config">AsyncTestConfig, ParallelTestSettings</elements>
    <elements in="com.example.database">UserEntity</elements>
    <elements in="com.example.legacy">LegacyBridgeService, OldPaymentApi</elements>
    <elements in="com.example.metrics">OrderMetrics</elements>
    <elements in="com.example.payment">PaymentDetails, PaymentProcessor</elements>
    <elements in="com.example.security">SecurityConfig</elements>
    <elements in="com.example.service">EvidenceBasedShowcase, InventoryService, LayeredDomainService, NewAnnotationsShowcase, NotificationService, OrderService, PricingService, PublicPaymentController, TransactionalPaymentService</elements>
    <elements in="com.example.service.NewAnnotationsShowcase">DraftKafkaIntegrationSpike, ImmutableProductPrice, SandboxTestHelper, TaxCalculatorStrategy</elements>
    <elements in="com.example.strategy">PaymentStrategy</elements>
    <elements in="com.example.strategy.impl">CreditCardStrategy</elements>
    <elements in="com.example.utils">I18nMessageHelper, StrictUtility, StringParser</elements>
  </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-MODULE-END: annotations-showcase -->
<!-- VIBETAGS-MODULE: app -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>

  <audit_requirements>
    <file path="com.example.gmm.app.App">
      <vulnerability_check>Path Traversal</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>
  <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. An elements entry lists names under a shared prefix: in="a.b" listing C, D means a.b.C and a.b.D. 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.app.App" rules=".claude/rules/reactor-spine.md"/>
  </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>

## Inherited Guardrails (dependencies)

These come from packages this project depends on. They constrain how the dependency may be used; they are not editable from here.

- `com.example.gmm.core` (from se.deversity.vibetags.example:gradle-multimodule-core:1.0)
  - @AISecure: 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.

## Inherited Context (dependencies)

Conventions the dependency's authors documented. Follow them unless this project's own rules above say otherwise.

- `com.example.gmm.core` (from se.deversity.vibetags.example:gradle-multimodule-core:1.0)
  - @AIContext: avoids=Adding mutable state, framework annotations, or a dependency on any sibling module.; focus=Immutable IR data model shared across every module of the reactor.
  - @AIThreadSafe: note=Every type in this package is safe to publish across threads without synchronization.; strategy=IMMUTABLE
<!-- VIBETAGS-MODULE-END: app -->
<!-- VIBETAGS-MODULE: core -->
<!-- # 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. An elements entry lists names under a shared prefix: in="a.b" listing C, D means a.b.C and a.b.D. 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" rules=".claude/rules/reactor-spine.md"/>
  </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-MODULE-END: core -->
<!-- VIBETAGS-MODULE: platform -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>

  <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>
  <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. An elements entry lists names under a shared prefix: in="a.b" listing C, D means a.b.C and a.b.D. 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>
    <elements in="com.example.gmm.platform">FeatureGate, Telemetry</elements>
  </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>
<!-- VIBETAGS-MODULE-END: platform -->
<!-- VIBETAGS-END -->