<!-- VIBETAGS-START -->
<!-- # 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>
  <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. 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.alltiers.shipping.CarrierAdapter" rules=".claude/rules/carrier-rates.md"/>
    <element path="com.example.alltiers.shipping.LabelPrinter" rules=".claude/rules/label-printing.md"/>
    <element path="com.example.alltiers.shipping.RateCalculator" rules=".claude/rules/carrier-rates.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-END -->
