git:20260821.ae7f616 to git:20260821.18c0b37
204 added, 2 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
<!-- 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<java.lang.String,java.lang.Object>)">
+ <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. Consult the referenced file before modifying an element.</note>
+ <element path="com.example.NotificationService" rules=".claude/rules/com-example-NotificationService.md"/>
+ <element path="com.example.compliance.GdprService" rules=".claude/rules/com-example-compliance-GdprService.md"/>
+ <element path="com.example.concurrent.SessionCache" rules=".claude/rules/com-example-concurrent-SessionCache.md"/>
+ <element path="com.example.config.AsyncTestConfig" rules=".claude/rules/com-example-config-AsyncTestConfig.md"/>
+ <element path="com.example.config.ParallelTestSettings" rules=".claude/rules/com-example-config-ParallelTestSettings.md"/>
+ <element path="com.example.database.DatabaseConnector" rules=".claude/rules/com-example-database-DatabaseConnector.md"/>
+ <element path="com.example.database.UserEntity" rules=".claude/rules/com-example-database-UserEntity.md"/>
+ <element path="com.example.internal.GeneratedMetadata" rules=".claude/rules/com-example-internal-GeneratedMetadata.md"/>
+ <element path="com.example.legacy.LegacyBridgeService" rules=".claude/rules/com-example-legacy-LegacyBridgeService.md"/>
+ <element path="com.example.legacy.OldPaymentApi" rules=".claude/rules/com-example-legacy-OldPaymentApi.md"/>
+ <element path="com.example.metrics.OrderMetrics" rules=".claude/rules/com-example-metrics-OrderMetrics.md"/>
+ <element path="com.example.payment.PaymentDetails" rules=".claude/rules/com-example-payment-PaymentDetails.md"/>
+ <element path="com.example.payment.PaymentProcessor" rules=".claude/rules/com-example-payment-PaymentProcessor.md"/>
+ <element path="com.example.security.SecurityConfig" rules=".claude/rules/com-example-security-SecurityConfig.md"/>
+ <element path="com.example.service.EvidenceBasedShowcase" rules=".claude/rules/com-example-service-EvidenceBasedShowcase.md"/>
+ <element path="com.example.service.InventoryService" rules=".claude/rules/com-example-service-InventoryService.md"/>
+ <element path="com.example.service.LayeredDomainService" rules=".claude/rules/com-example-service-LayeredDomainService.md"/>
+ <element path="com.example.service.NewAnnotationsShowcase" rules=".claude/rules/com-example-service-NewAnnotationsShowcase.md"/>
+ <element path="com.example.service.NewAnnotationsShowcase.DraftKafkaIntegrationSpike" rules=".claude/rules/com-example-service-NewAnnotationsShowcase-DraftKafkaIntegrationSpike.md"/>
+ <element path="com.example.service.NewAnnotationsShowcase.ImmutableProductPrice" rules=".claude/rules/com-example-service-NewAnnotationsShowcase-ImmutableProductPrice.md"/>
+ <element path="com.example.service.NewAnnotationsShowcase.SandboxTestHelper" rules=".claude/rules/com-example-service-NewAnnotationsShowcase-SandboxTestHelper.md"/>
+ <element path="com.example.service.NewAnnotationsShowcase.TaxCalculatorStrategy" rules=".claude/rules/com-example-service-NewAnnotationsShowcase-TaxCalculatorStrategy.md"/>
+ <element path="com.example.service.NotificationService" rules=".claude/rules/com-example-service-NotificationService.md"/>
+ <element path="com.example.service.OrderService" rules=".claude/rules/com-example-service-OrderService.md"/>
+ <element path="com.example.service.PricingService" rules=".claude/rules/com-example-service-PricingService.md"/>
+ <element path="com.example.service.PublicPaymentController" rules=".claude/rules/com-example-service-PublicPaymentController.md"/>
+ <element path="com.example.service.TransactionalPaymentService" rules=".claude/rules/com-example-service-TransactionalPaymentService.md"/>
+ <element path="com.example.strategy.PaymentStrategy" rules=".claude/rules/com-example-strategy-PaymentStrategy.md"/>
+ <element path="com.example.strategy.impl.CreditCardStrategy" rules=".claude/rules/com-example-strategy-impl-CreditCardStrategy.md"/>
+ <element path="com.example.utils.I18nMessageHelper" rules=".claude/rules/com-example-utils-I18nMessageHelper.md"/>
+ <element path="com.example.utils.StrictUtility" rules=".claude/rules/com-example-utils-StrictUtility.md"/>
+ <element path="com.example.utils.StringParser" rules=".claude/rules/com-example-utils-StringParser.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: 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. Consult the referenced file before modifying an element.</note>
- <element path="com.example.gmm.app.App" rules=".claude/rules/com-example-gmm-app-App.md"/>
+ <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. Consult the referenced file before modifying an element.</note>
- <element path="com.example.gmm.core.IrNode" rules=".claude/rules/com-example-gmm-core-IrNode.md"/>
+ <element path="com.example.gmm.core" rules=".claude/rules/reactor-spine.md"/>
+ <element path="com.example.gmm.core.IrNode" 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. Consult the referenced file before modifying an element.</note>
+ <element path="com.example.gmm.platform.FeatureGate" rules=".claude/rules/com-example-gmm-platform-FeatureGate.md"/>
+ <element path="com.example.gmm.platform.Telemetry" rules=".claude/rules/com-example-gmm-platform-Telemetry.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>
+ <!-- VIBETAGS-MODULE-END: platform -->
<!-- VIBETAGS-END -->