CLAUDE.md@examples/kotlin · diff
git:20260905.1b67819 to git:20260914.04fac21
6 added, 0 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 -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<locked_files>
+ <file path="com.example.kotlin.AccountLedger.reconcile$se_deversity_vibetags_example_vibetags_example_kotlin(java.lang.String)">
+ <reason>LEDGER-INTERNAL-KEPT: reconciliation batches are replayed by the audit job.</reason>
+ </file>
+ <file path="com.example.kotlin.AccountLedger.settle(java.lang.Object)">
+ <reason>LEDGER-RESULT-KEPT: settlement outcome mapping is part of the payout contract.</reason>
+ </file>
<file path="com.example.kotlin.PaymentService.chargeKey(java.lang.String,int)">
<reason>Charge idempotency key derivation is contract-tested against the gateway. Changing it re-charges in-flight payments.</reason>
</file>
</locked_files>
<contextual_instructions>
<file path="com.example.kotlin.PaymentService">
<focus>Coordinates payment authorization and capture against the gateway</focus>
<avoids>Retry logic — the gateway client already retries; a second layer double-charges</avoids>
</file>
</contextual_instructions>
<pii_guardrails>
<element path="com.example.kotlin.CustomerVault">
<reason>Holds customer PII — never log, expose, or include field values 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.kotlin.CustomerVault.findCustomer(java.lang.String)">
<sensitivity>critical</sensitivity>
<note>Primary lookup path for every checkout; covered by the vault contract 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>
</project_guardrails>
<rule>Never propose edits to files listed in <locked_files>.</rule>
## 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.multimodule.core` (from se.deversity.vibetags.example: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 id 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.multimodule.core` (from se.deversity.vibetags.example: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.
<!-- VIBETAGS-END -->