# Acme Shop

Order and payment service behind the Acme web shop and its mobile apps.

- Java 21. Sources live under `src/main/java/com/acme/shop`.
- Packages: `api` (checkout endpoints for web and mobile), `order` (pricing), `customer`
  (registration), `payment` (card acquirer client).
- Keep changes small and focused; match the style of the surrounding code.

<!-- VIBETAGS-START -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
  <locked_files>
    <file path="com.acme.shop.payment.PaymentGateway">
      <reason>The acquirer&#39;s nightly settlement file is matched against these exact method signatures and integer minor units (contract ACQ-2291); any change here breaks reconciliation, so route changes through the payments team.</reason>
    </file>
  </locked_files>
  <contextual_instructions>
  </contextual_instructions>
  <pii_guardrails>
    <element path="com.acme.shop.customer.Customer.email">
      <reason>Personal data under GDPR Art. 4: must never reach logs, metrics, traces or error messages. Identify a customer by id instead.</reason>
    </element>
    <element path="com.acme.shop.customer.Customer.taxId">
      <reason>National tax identifier: must never reach logs, metrics, traces or error messages. Identify a customer by id instead.</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>
  <contract_signatures>
    <element path="com.acme.shop.api.OrderApi.placeOrder(java.lang.String,java.util.List&lt;java.lang.String&gt;)">
      <reason>Mobile apps call this exact signature over the RPC bridge, and app releases stay installed for six months, so a changed signature breaks apps already in the field. Add an overload instead.</reason>
    </element>
  </contract_signatures>

<rule>You may refactor the internal logic of elements listed in <contract_signatures>, but you MUST NOT change their public signatures: method names, parameter types, parameter order, return types, or checked exceptions.</rule>
</project_guardrails>

<rule>Never propose edits to files listed in <locked_files>.</rule>
<!-- VIBETAGS-END -->
