<!-- VIBETAGS-START -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
  <locked_files>
  </locked_files>
  <contextual_instructions>
  </contextual_instructions>

  <audit_requirements>
    <file path="com.example.multimodule.cli.MultiModuleCli">
      <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>
  <contract_signatures>
    <element path="com.example.multimodule.cli.MultiModuleCli.run(java.lang.String[])">
      <reason>Public CLI surface; flags are documented downstream</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>
  <test_driven_requirements>
    <element path="com.example.multimodule.cli.MultiModuleCli">
      <coverage_goal>100</coverage_goal>
      <frameworks>JUNIT_5</frameworks>
      <test_location>src/test/java/com/example/multimodule/cli</test_location>
    </element>
  </test_driven_requirements>

<rule>For any element listed in <test_driven_requirements>, you MUST provide both the implementation change AND the corresponding test code update in a single response. Changes without tests are incomplete and must not be proposed. Every name under <applies-to> in a <test_driven_default> block inherits that block's coverage goal, frameworks, and test-location convention (with {path} standing for the element's package path).</rule>
  <idempotent_elements>
    <element path="com.example.multimodule.cli.MultiModuleCli.outputPath(java.lang.String,java.lang.String)">
      <idempotent>true</idempotent>
      <reason>Derives output path from inputs only</reason>
    </element>
  </idempotent_elements>

<rule>Operations listed in <idempotent_elements> must remain idempotent. Never introduce side effects that cause repeated invocations to produce different results.</rule>
  <pure_functions>
    <file path="com.example.multimodule.cli.MultiModuleCli.outputPath(java.lang.String,java.lang.String)">
      <policy>Pure function: no side effects, deterministic.</policy>
    </file>
  </pure_functions>

<rule>Methods in <pure_functions> must remain mathematically pure. Side effects, mutations of class/static state, or blocking operations are strictly forbidden.</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.
  - @AIThreadSafe: note=Every type in this package is safe to publish across threads without synchronization.; strategy=IMMUTABLE
<!-- VIBETAGS-END -->
