CLAUDE.md@examples/all-tiers · git:20260820.1cddfe2 · 2026-08-20 · sha256 75950d0fc53ecb9c
CLAUDE.md@examples/all-tiers git:20260820.1cddfe2A
Immutable. This exact content never changes and is served at /api/v1/blob/75950d0fc53ecb9c.
<!-- VIBETAGS-START -->
<!-- VIBETAGS-MODULE: billing -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<locked_files>
<file path="com.example.alltiers.billing.InvoiceController.invoiceNumber(long)">
<reason>The invoice number format is on partner contracts; changing it breaks reconciliation</reason>
</file>
</locked_files>
<audit_requirements>
<file path="com.example.alltiers.billing.InvoiceController">
<vulnerability_check>SQL Injection</vulnerability_check>
<vulnerability_check>Broken Access Control</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>
<pii_guardrails>
<element path="com.example.alltiers.billing.InvoiceController.billingEmail">
<reason>Billing email identifies a natural person; never log it or echo it back</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.alltiers.billing.LedgerEntry">
<sensitivity>critical</sensitivity>
<note>Every monetary total in the system is derived from these rows</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>
Guardrails for module `billing` are maintained in that module's own files, in the scoped rules under `billing/.claude/rules/` (loaded automatically when you open a matching source file) and `billing/CLAUDE.md`. Consult those for this module's full guardrails.
<!-- VIBETAGS-MODULE-END: billing -->
<!-- VIBETAGS-MODULE: shipping -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<ignored_elements>
<file path="com.example.alltiers.shipping.LabelPrinter.carrierSessionToken">
<reason>Cached carrier handshake token; meaningless outside one process</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>
<security_elements>
<element path="com.example.alltiers.shipping.LabelPrinter">
<aspect>Carrier credentials and label signing</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>
</project_guardrails>
Guardrails for module `shipping` are maintained in that module's own files, in the scoped rules under `shipping/.claude/rules/` (loaded automatically when you open a matching source file) and `shipping/CLAUDE.md`. Consult those for this module's full guardrails.
<!-- VIBETAGS-MODULE-END: shipping -->
<!-- VIBETAGS-END -->