diff --git a/AGENTS.md b/AGENTS.md
deleted file mode 100644
index ffba798..0000000
--- a/AGENTS.md
+++ /dev/null
@@ -1,622 +0,0 @@
-# Repository Guidelines
-
-## Project Structure & Module Organization
-The application follows Laravel 12's streamlined tree. Server code lives in `app/`, with Livewire & Volt components under `app/Livewire` and HTTP actions under `app/Http`. Volt views and shared blades live in `resources/views`, UI assets in `resources/js` and `resources/css`. Routes are split across `routes/web.php`, `routes/api.php`, and CLI automation in `routes/console.php`. Database migrations, factories, and seeders live within `database/`. Automated tests are grouped by layer in `tests/Feature` and `tests/Unit`.
-
-## Build, Test, and Development Commands
-Use `composer run dev` for the full local stack (PHP server, queue listener, Pail, and Vite). Frontend-only work can rely on `npm run dev`, while `npm run build` compiles production assets. `composer test` clears config cache then runs the Pest suite. Run targeted tests via `php artisan test tests/Feature/FooTest.php`. When onboarding, execute `composer run setup` to install dependencies, provision `.env`, migrate, and build assets.
-
-## Coding Style & Naming Conventions
-PHP code targets 8.4+ and follows Laravel Pint defaults; run `vendor/bin/pint --dirty` before committing. Use descriptive camelCase for variables and methods, and PascalCase for classes, Livewire components, and enums. Volt components should keep their Blade/PHP in a single `.blade.php` file and align with existing Flux UI usage. Tailwind v4 powers styling—reference the utility-first classes already present in `resources/css/app.css`.
-
-## Testing Guidelines
-Write tests with Pest v4, mirroring the structure under `tests/Feature` for HTTP and Livewire flows and `tests/Unit` for pure logic. Prefer model factories and Volt testing helpers (`Volt::test`) to cover component behavior. Name tests after user-facing behavior and exercise validation errors alongside success paths. Always run the nearest relevant `php artisan test` command before pushing.
-
-## Commit & Pull Request Guidelines
-Commits are short, present-tense summaries (for example, `add billing address migration`). Bundle related changes together and include schema updates with their factories and tests. Pull requests should describe the change, list validation steps (commands run, screenshots for UI), and link to any tracked issue. Flag follow-up work clearly so reviewers can plan next steps.
-
-===
-
-
-=== foundation rules ===
-
-# Laravel Boost Guidelines
-
-The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to enhance the user's satisfaction building Laravel applications.
-
-## Foundational Context
-This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions.
-
-- php - 8.4.14
-- laravel/fortify (FORTIFY) - v1
-- laravel/framework (LARAVEL) - v12
-- laravel/prompts (PROMPTS) - v0
-- livewire/flux (FLUXUI_FREE) - v2
-- livewire/livewire (LIVEWIRE) - v3
-- livewire/volt (VOLT) - v1
-- laravel/mcp (MCP) - v0
-- laravel/pint (PINT) - v1
-- laravel/sail (SAIL) - v1
-- pestphp/pest (PEST) - v4
-- phpunit/phpunit (PHPUNIT) - v12
-- tailwindcss (TAILWINDCSS) - v4
-
-## Conventions
-- You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, naming.
-- Use descriptive names for variables and methods. For example, `isRegisteredForDiscounts`, not `discount()`.
-- Check for existing components to reuse before writing a new one.
-
-## Verification Scripts
-- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.
-
-## Application Structure & Architecture
-- Stick to existing directory structure - don't create new base folders without approval.
-- Do not change the application's dependencies without approval.
-
-## Frontend Bundling
-- If the user doesn't see a frontend change reflected in the UI, it could mean they need to run `npm run build`, `npm run dev`, or `composer run dev`. Ask them.
-
-## Replies
-- Be concise in your explanations - focus on what's important rather than explaining obvious details.
-
-## Documentation Files
-- You must only create documentation files if explicitly requested by the user.
-
-
-=== boost rules ===
-
-## Laravel Boost
-- Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them.
-
-## Artisan
-- Use the `list-artisan-commands` tool when you need to call an Artisan command to double check the available parameters.
-
-## URLs
-- Whenever you share a project URL with the user you should use the `get-absolute-url` tool to ensure you're using the correct scheme, domain / IP, and port.
-
-## Tinker / Debugging
-- You should use the `tinker` tool when you need to execute PHP to debug code or query Eloquent models directly.
-- Use the `database-query` tool when you only need to read from the database.
-
-## Reading Browser Logs With the `browser-logs` Tool
-- You can read browser logs, errors, and exceptions using the `browser-logs` tool from Boost.
-- Only recent browser logs will be useful - ignore old logs.
-
-## Searching Documentation (Critically Important)
-- Boost comes with a powerful `search-docs` tool you should use before any other approaches. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation specific for the user's circumstance. You should pass an array of packages to filter on if you know you need docs for particular packages.
-- The 'search-docs' tool is perfect for all Laravel related packages, including Laravel, Inertia, Livewire, Filament, Tailwind, Pest, Nova, Nightwatch, etc.
-- You must use this tool to search for Laravel-ecosystem documentation before falling back to other approaches.
-- Search the documentation before making code changes to ensure we are taking the correct approach.
-- Use multiple, broad, simple, topic based queries to start. For example: `['rate limiting', 'routing rate limiting', 'routing']`.
-- Do not add package names to queries - package information is already shared. For example, use `test resource table`, not `filament 4 test resource table`.
-
-### Available Search Syntax
-- You can and should pass multiple queries at once. The most relevant results will be returned first.
-
-1. Simple Word Searches with auto-stemming - query=authentication - finds 'authenticate' and 'auth'
-2. Multiple Words (AND Logic) - query=rate limit - finds knowledge containing both "rate" AND "limit"
-3. Quoted Phrases (Exact Position) - query="infinite scroll" - Words must be adjacent and in that order
-4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit"
-5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms
-
-
-=== php rules ===
-
-## PHP
-
-- Always use curly braces for control structures, even if it has one line.
-
-### Constructors
-- Use PHP 8 constructor property promotion in `__construct()`.
- - public function __construct(public GitHub $github) { }
-- Do not allow empty `__construct()` methods with zero parameters.
-
-### Type Declarations
-- Always use explicit return type declarations for methods and functions.
-- Use appropriate PHP type hints for method parameters.
-
-
-protected function isAccessible(User $user, ?string $path = null): bool
-{
- ...
-}
-
-
-## Comments
-- Prefer PHPDoc blocks over comments. Never use comments within the code itself unless there is something _very_ complex going on.
-
-## PHPDoc Blocks
-- Add useful array shape type definitions for arrays when appropriate.
-
-## Enums
-- Typically, keys in an Enum should be TitleCase. For example: `FavoritePerson`, `BestLake`, `Monthly`.
-
-
-=== laravel/core rules ===
-
-## Do Things the Laravel Way
-
-- Use `php artisan make:` commands to create new files (i.e. migrations, controllers, models, etc.). You can list available Artisan commands using the `list-artisan-commands` tool.
-- If you're creating a generic PHP class, use `artisan make:class`.
-- Pass `--no-interaction` to all Artisan commands to ensure they work without user input. You should also pass the correct `--options` to ensure correct behavior.
-
-### Database
-- Always use proper Eloquent relationship methods with return type hints. Prefer relationship methods over raw queries or manual joins.
-- Use Eloquent models and relationships before suggesting raw database queries
-- Avoid `DB::`; prefer `Model::query()`. Generate code that leverages Laravel's ORM capabilities rather than bypassing them.
-- Generate code that prevents N+1 query problems by using eager loading.
-- Use Laravel's query builder for very complex database operations.
-
-### Model Creation
-- When creating new models, create useful factories and seeders for them too. Ask the user if they need any other things, using `list-artisan-commands` to check the available options to `php artisan make:model`.
-
-### APIs & Eloquent Resources
-- For APIs, default to using Eloquent API Resources and API versioning unless existing API routes do not, then you should follow existing application convention.
-
-### Controllers & Validation
-- Always create Form Request classes for validation rather than inline validation in controllers. Include both validation rules and custom error messages.
-- Check sibling Form Requests to see if the application uses array or string based validation rules.
-
-### Queues
-- Use queued jobs for time-consuming operations with the `ShouldQueue` interface.
-
-### Authentication & Authorization
-- Use Laravel's built-in authentication and authorization features (gates, policies, Sanctum, etc.).
-
-### URL Generation
-- When generating links to other pages, prefer named routes and the `route()` function.
-
-### Configuration
-- Use environment variables only in configuration files - never use the `env()` function directly outside of config files. Always use `config('app.name')`, not `env('APP_NAME')`.
-
-### Testing
-- When creating models for tests, use the factories for the models. Check if the factory has custom states that can be used before manually setting up the model.
-- Faker: Use methods such as `$this->faker->word()` or `fake()->randomDigit()`. Follow existing conventions whether to use `$this->faker` or `fake()`.
-- When creating tests, make use of `php artisan make:test [options] ` to create a feature test, and pass `--unit` to create a unit test. Most tests should be feature tests.
-
-### Vite Error
-- If you receive an "Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest" error, you can run `npm run build` or ask the user to run `npm run dev` or `composer run dev`.
-
-
-=== laravel/v12 rules ===
-
-## Laravel 12
-
-- Use the `search-docs` tool to get version specific documentation.
-- Since Laravel 11, Laravel has a new streamlined file structure which this project uses.
-
-### Laravel 12 Structure
-- No middleware files in `app/Http/Middleware/`.
-- `bootstrap/app.php` is the file to register middleware, exceptions, and routing files.
-- `bootstrap/providers.php` contains application specific service providers.
-- **No app\Console\Kernel.php** - use `bootstrap/app.php` or `routes/console.php` for console configuration.
-- **Commands auto-register** - files in `app/Console/Commands/` are automatically available and do not require manual registration.
-
-### Database
-- When modifying a column, the migration must include all of the attributes that were previously defined on the column. Otherwise, they will be dropped and lost.
-- Laravel 11 allows limiting eagerly loaded records natively, without external packages: `$query->latest()->limit(10);`.
-
-### Models
-- Casts can and likely should be set in a `casts()` method on a model rather than the `$casts` property. Follow existing conventions from other models.
-
-
-=== fluxui-free/core rules ===
-
-## Flux UI Free
-
-- This project is using the free edition of Flux UI. It has full access to the free components and variants, but does not have access to the Pro components.
-- Flux UI is a component library for Livewire. Flux is a robust, hand-crafted, UI component library for your Livewire applications. It's built using Tailwind CSS and provides a set of components that are easy to use and customize.
-- You should use Flux UI components when available.
-- Fallback to standard Blade components if Flux is unavailable.
-- If available, use Laravel Boost's `search-docs` tool to get the exact documentation and code snippets available for this project.
-- Flux UI components look like this:
-
-
-
-
-
-
-### Available Components
-This is correct as of Boost installation, but there may be additional components within the codebase.
-
-
-avatar, badge, brand, breadcrumbs, button, callout, checkbox, dropdown, field, heading, icon, input, modal, navbar, profile, radio, select, separator, switch, text, textarea, tooltip
-
-
-
-=== livewire/core rules ===
-
-## Livewire Core
-- Use the `search-docs` tool to find exact version specific documentation for how to write Livewire & Livewire tests.
-- Use the `php artisan make:livewire [Posts\\CreatePost]` artisan command to create new components
-- State should live on the server, with the UI reflecting it.
-- All Livewire requests hit the Laravel backend, they're like regular HTTP requests. Always validate form data, and run authorization checks in Livewire actions.
-
-## Livewire Best Practices
-- Livewire components require a single root element.
-- Use `wire:loading` and `wire:dirty` for delightful loading states.
-- Add `wire:key` in loops:
-
- ```blade
- @foreach ($items as $item)
-
- {{ $item->name }}
-
- @endforeach
- ```
-
-- Prefer lifecycle hooks like `mount()`, `updatedFoo()` for initialization and reactive side effects:
-
-
- public function mount(User $user) { $this->user = $user; }
- public function updatedSearch() { $this->resetPage(); }
-
-
-
-## Testing Livewire
-
-
- Livewire::test(Counter::class)
- ->assertSet('count', 0)
- ->call('increment')
- ->assertSet('count', 1)
- ->assertSee(1)
- ->assertStatus(200);
-
-
-
-
- $this->get('/posts/create')
- ->assertSeeLivewire(CreatePost::class);
-
-
-
-=== livewire/v3 rules ===
-
-## Livewire 3
-
-### Key Changes From Livewire 2
-- These things changed in Livewire 2, but may not have been updated in this application. Verify this application's setup to ensure you conform with application conventions.
- - Use `wire:model.live` for real-time updates, `wire:model` is now deferred by default.
- - Components now use the `App\Livewire` namespace (not `App\Http\Livewire`).
- - Use `$this->dispatch()` to dispatch events (not `emit` or `dispatchBrowserEvent`).
- - Use the `components.layouts.app` view as the typical layout path (not `layouts.app`).
-
-### New Directives
-- `wire:show`, `wire:transition`, `wire:cloak`, `wire:offline`, `wire:target` are available for use. Use the documentation to find usage examples.
-
-### Alpine
-- Alpine is now included with Livewire, don't manually include Alpine.js.
-- Plugins included with Alpine: persist, intersect, collapse, and focus.
-
-### Lifecycle Hooks
-- You can listen for `livewire:init` to hook into Livewire initialization, and `fail.status === 419` for the page expiring:
-
-
-document.addEventListener('livewire:init', function () {
- Livewire.hook('request', ({ fail }) => {
- if (fail && fail.status === 419) {
- alert('Your session expired');
- }
- });
-
- Livewire.hook('message.failed', (message, component) => {
- console.error(message);
- });
-});
-
-
-
-=== volt/core rules ===
-
-## Livewire Volt
-
-- This project uses Livewire Volt for interactivity within its pages. New pages requiring interactivity must also use Livewire Volt. There is documentation available for it.
-- Make new Volt components using `php artisan make:volt [name] [--test] [--pest]`
-- Volt is a **class-based** and **functional** API for Livewire that supports single-file components, allowing a component's PHP logic and Blade templates to co-exist in the same file
-- Livewire Volt allows PHP logic and Blade templates in one file. Components use the `@livewire("volt-anonymous-fragment-eyJuYW1lIjoidm9sdC1hbm9ueW1vdXMtZnJhZ21lbnQtYmQ5YWJiNTE3YWMyMTgwOTA1ZmUxMzAxODk0MGJiZmIiLCJwYXRoIjoic3RvcmFnZVwvZnJhbWV3b3JrXC92aWV3c1wvMTUxYWRjZWRjMzBhMzllOWIxNzQ0ZDRiMWRjY2FjYWIuYmxhZGUucGhwIn0=", Livewire\Volt\Precompilers\ExtractFragments::componentArguments([...get_defined_vars(), ...array (
-)]))
-
-
-
-### Volt Class Based Component Example
-To get started, define an anonymous class that extends Livewire\Volt\Component. Within the class, you may utilize all of the features of Livewire using traditional Livewire syntax:
-
-
-
-use Livewire\Volt\Component;
-
-new class extends Component {
- public $count = 0;
-
- public function increment()
- {
- $this->count++;
- }
-} ?>
-
-
-
{{ $count }}
-
-
-
-
-
-### Testing Volt & Volt Components
-- Use the existing directory for tests if it already exists. Otherwise, fallback to `tests/Feature/Volt`.
-
-
-use Livewire\Volt\Volt;
-
-test('counter increments', function () {
- Volt::test('counter')
- ->assertSee('Count: 0')
- ->call('increment')
- ->assertSee('Count: 1');
-});
-
-
-
-
-declare(strict_types=1);
-
-use App\Models\{User, Product};
-use Livewire\Volt\Volt;
-
-test('product form creates product', function () {
- $user = User::factory()->create();
-
- Volt::test('pages.products.create')
- ->actingAs($user)
- ->set('form.name', 'Test Product')
- ->set('form.description', 'Test Description')
- ->set('form.price', 99.99)
- ->call('create')
- ->assertHasNoErrors();
-
- expect(Product::where('name', 'Test Product')->exists())->toBeTrue();
-});
-
-
-
-### Common Patterns
-
-
-
- null, 'search' => '']);
-
-$products = computed(fn() => Product::when($this->search,
- fn($q) => $q->where('name', 'like', "%{$this->search}%")
-)->get());
-
-$edit = fn(Product $product) => $this->editing = $product->id;
-$delete = fn(Product $product) => $product->delete();
-
-?>
-
-
-
-
-
-
-
-
-
-
- Save
- Saving...
-
-
-
-
-=== pint/core rules ===
-
-## Laravel Pint Code Formatter
-
-- You must run `vendor/bin/pint --dirty` before finalizing changes to ensure your code matches the project's expected style.
-- Do not run `vendor/bin/pint --test`, simply run `vendor/bin/pint` to fix any formatting issues.
-
-
-=== pest/core rules ===
-
-## Pest
-
-### Testing
-- If you need to verify a feature is working, write or update a Unit / Feature test.
-
-### Pest Tests
-- All tests must be written using Pest. Use `php artisan make:test --pest `.
-- You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files - these are core to the application.
-- Tests should test all of the happy paths, failure paths, and weird paths.
-- Tests live in the `tests/Feature` and `tests/Unit` directories.
-- Pest tests look and behave like this:
-
-it('is true', function () {
- expect(true)->toBeTrue();
-});
-
-
-### Running Tests
-- Run the minimal number of tests using an appropriate filter before finalizing code edits.
-- To run all tests: `php artisan test`.
-- To run all tests in a file: `php artisan test tests/Feature/ExampleTest.php`.
-- To filter on a particular test name: `php artisan test --filter=testName` (recommended after making a change to a related file).
-- When the tests relating to your changes are passing, ask the user if they would like to run the entire test suite to ensure everything is still passing.
-
-### Pest Assertions
-- When asserting status codes on a response, use the specific method like `assertForbidden` and `assertNotFound` instead of using `assertStatus(403)` or similar, e.g.:
-
-it('returns all', function () {
- $response = $this->postJson('/api/docs', []);
-
- $response->assertSuccessful();
-});
-
-
-### Mocking
-- Mocking can be very helpful when appropriate.
-- When mocking, you can use the `Pest\Laravel\mock` Pest function, but always import it via `use function Pest\Laravel\mock;` before using it. Alternatively, you can use `$this->mock()` if existing tests do.
-- You can also create partial mocks using the same import or self method.
-
-### Datasets
-- Use datasets in Pest to simplify tests which have a lot of duplicated data. This is often the case when testing validation rules, so consider going with this solution when writing tests for validation rules.
-
-
-it('has emails', function (string $email) {
- expect($email)->not->toBeEmpty();
-})->with([
- 'james' => 'james@laravel.com',
- 'taylor' => 'taylor@laravel.com',
-]);
-
-
-
-=== pest/v4 rules ===
-
-## Pest 4
-
-- Pest v4 is a huge upgrade to Pest and offers: browser testing, smoke testing, visual regression testing, test sharding, and faster type coverage.
-- Browser testing is incredibly powerful and useful for this project.
-- Browser tests should live in `tests/Browser/`.
-- Use the `search-docs` tool for detailed guidance on utilizing these features.
-
-### Browser Testing
-- You can use Laravel features like `Event::fake()`, `assertAuthenticated()`, and model factories within Pest v4 browser tests, as well as `RefreshDatabase` (when needed) to ensure a clean state for each test.
-- Interact with the page (click, type, scroll, select, submit, drag-and-drop, touch gestures, etc.) when appropriate to complete the test.
-- If requested, test on multiple browsers (Chrome, Firefox, Safari).
-- If requested, test on different devices and viewports (like iPhone 14 Pro, tablets, or custom breakpoints).
-- Switch color schemes (light/dark mode) when appropriate.
-- Take screenshots or pause tests for debugging when appropriate.
-
-### Example Tests
-
-
-it('may reset the password', function () {
- Notification::fake();
-
- $this->actingAs(User::factory()->create());
-
- $page = visit('/sign-in'); // Visit on a real browser...
-
- $page->assertSee('Sign In')
- ->assertNoJavascriptErrors() // or ->assertNoConsoleLogs()
- ->click('Forgot Password?')
- ->fill('email', 'nuno@laravel.com')
- ->click('Send Reset Link')
- ->assertSee('We have emailed your password reset link!')
-
- Notification::assertSent(ResetPassword::class);
-});
-
-
-
-$pages = visit(['/', '/about', '/contact']);
-
-$pages->assertNoJavascriptErrors()->assertNoConsoleLogs();
-
-
-
-=== tailwindcss/core rules ===
-
-## Tailwind Core
-
-- Use Tailwind CSS classes to style HTML, check and use existing tailwind conventions within the project before writing your own.
-- Offer to extract repeated patterns into components that match the project's conventions (i.e. Blade, JSX, Vue, etc..)
-- Think through class placement, order, priority, and defaults - remove redundant classes, add classes to parent or child carefully to limit repetition, group elements logically
-- You can use the `search-docs` tool to get exact examples from the official documentation when needed.
-
-### Spacing
-- When listing items, use gap utilities for spacing, don't use margins.
-
-
-
-
Superior
-
Michigan
-
Erie
-
-
-
-
-### Dark Mode
-- If existing pages and components support dark mode, new pages and components must support dark mode in a similar way, typically using `dark:`.
-
-
-=== tailwindcss/v4 rules ===
-
-## Tailwind 4
-
-- Always use Tailwind CSS v4 - do not use the deprecated utilities.
-- `corePlugins` is not supported in Tailwind v4.
-- In Tailwind v4, you import Tailwind using a regular CSS `@import` statement, not using the `@tailwind` directives used in v3:
-
-
- - @tailwind base;
- - @tailwind components;
- - @tailwind utilities;
- + @import "tailwindcss";
-
-
-
-### Replaced Utilities
-- Tailwind v4 removed deprecated utilities. Do not use the deprecated option - use the replacement.
-- Opacity values are still numeric.
-
-| Deprecated | Replacement |
-|------------+--------------|
-| bg-opacity-* | bg-black/* |
-| text-opacity-* | text-black/* |
-| border-opacity-* | border-black/* |
-| divide-opacity-* | divide-black/* |
-| ring-opacity-* | ring-black/* |
-| placeholder-opacity-* | placeholder-black/* |
-| flex-shrink-* | shrink-* |
-| flex-grow-* | grow-* |
-| overflow-ellipsis | text-ellipsis |
-| decoration-slice | box-decoration-slice |
-| decoration-clone | box-decoration-clone |
-
-
-=== tests rules ===
-
-## Test Enforcement
-
-- Every change must be programmatically tested. Write a new test or update an existing test, then run the affected tests to make sure they pass.
-- Run the minimum number of tests needed to ensure code quality and speed. Use `php artisan test` with a specific filename or filter.
-
-
-=== laravel/fortify rules ===
-
-## Laravel Fortify
-
-Fortify is a headless authentication backend that provides authentication routes and controllers for Laravel applications.
-
-**Before implementing any authentication features, use the `search-docs` tool to get the latest docs for that specific feature.**
-
-### Configuration & Setup
-- Check `config/fortify.php` to see what's enabled. Use `search-docs` for detailed information on specific features.
-- Enable features by adding them to the `'features' => []` array: `Features::registration()`, `Features::resetPasswords()`, etc.
-- To see the all Fortify registered routes, use the `list-routes` tool with the `only_vendor: true` and `action: "Fortify"` parameters.
-- Fortify includes view routes by default (login, register). Set `'views' => false` in the configuration file to disable them if you're handling views yourself.
-
-### Customization
-- Views can be customized in `FortifyServiceProvider`'s `boot()` method using `Fortify::loginView()`, `Fortify::registerView()`, etc.
-- Customize authentication logic with `Fortify::authenticateUsing()` for custom user retrieval / validation.
-- Actions in `app/Actions/Fortify/` handle business logic (user creation, password reset, etc.). They're fully customizable, so you can modify them to change feature behavior.
-
-## Available Features
-- `Features::registration()` for user registration.
-- `Features::emailVerification()` to verify new user emails.
-- `Features::twoFactorAuthentication()` for 2FA with QR codes and recovery codes.
- - Add options: `['confirmPassword' => true, 'confirm' => true]` to require password confirmation and OTP confirmation before enabling 2FA.
-- `Features::updateProfileInformation()` to let users update their profile.
-- `Features::updatePasswords()` to let users change their passwords.
-- `Features::resetPasswords()` for password reset via email.
-
diff --git a/app/Console/Commands/SyncBackendDataPoolCommand.php b/app/Console/Commands/SyncBackendDataPoolCommand.php
index 8383db4..e5750cf 100644
--- a/app/Console/Commands/SyncBackendDataPoolCommand.php
+++ b/app/Console/Commands/SyncBackendDataPoolCommand.php
@@ -94,7 +94,7 @@ class SyncBackendDataPoolCommand extends Command
*/
private function showStats(): int
{
- $job = new SyncBackendDataPool();
+ $job = new SyncBackendDataPool;
$stats = $job->getStats();
info('Backend Data Pool Statistics');
@@ -117,7 +117,7 @@ class SyncBackendDataPoolCommand extends Command
*/
private function showStatsBefore(): void
{
- $job = new SyncBackendDataPool();
+ $job = new SyncBackendDataPool;
$stats = $job->getStats();
$this->newLine();
@@ -138,7 +138,7 @@ class SyncBackendDataPoolCommand extends Command
*/
private function showStatsAfter(): void
{
- $job = new SyncBackendDataPool();
+ $job = new SyncBackendDataPool;
$stats = $job->getStats();
$this->newLine();
diff --git a/app/Console/Commands/TransformDataPoolCommand.php b/app/Console/Commands/TransformDataPoolCommand.php
index 3da2908..c9be9c7 100644
--- a/app/Console/Commands/TransformDataPoolCommand.php
+++ b/app/Console/Commands/TransformDataPoolCommand.php
@@ -82,7 +82,7 @@ class TransformDataPoolCommand extends Command
*/
private function showStats(): int
{
- $job = new TransformDataPoolToProduction();
+ $job = new TransformDataPoolToProduction;
$stats = $job->getStats();
info('Data Pool Transformation Statistics');
@@ -105,7 +105,7 @@ class TransformDataPoolCommand extends Command
*/
private function showStatsBefore(): void
{
- $job = new TransformDataPoolToProduction();
+ $job = new TransformDataPoolToProduction;
$stats = $job->getStats();
$this->newLine();
@@ -126,7 +126,7 @@ class TransformDataPoolCommand extends Command
*/
private function showStatsAfter(): void
{
- $job = new TransformDataPoolToProduction();
+ $job = new TransformDataPoolToProduction;
$stats = $job->getStats();
$this->newLine();
diff --git a/app/Jobs/SyncBackendDataPool.php b/app/Jobs/SyncBackendDataPool.php
index bc25857..021d44b 100644
--- a/app/Jobs/SyncBackendDataPool.php
+++ b/app/Jobs/SyncBackendDataPool.php
@@ -29,8 +29,7 @@ class SyncBackendDataPool implements ShouldQueue
public function __construct(
public bool $fullSync = true,
public ?int $batchSize = 1000,
- ) {
- }
+ ) {}
/**
* Execute the job.
diff --git a/app/Models/Backend/Transaction.php b/app/Models/Backend/Transaction.php
index fffd473..84d609f 100644
--- a/app/Models/Backend/Transaction.php
+++ b/app/Models/Backend/Transaction.php
@@ -127,7 +127,7 @@ class Transaction extends Model
{
$risk = $this->getRiskAssessment();
- if (!$risk) {
+ if (! $risk) {
return true; // Keine Risk-Assessment → Review
}
diff --git a/app/Models/Transaction.php b/app/Models/Transaction.php
index b24a890..03a40c2 100644
--- a/app/Models/Transaction.php
+++ b/app/Models/Transaction.php
@@ -69,7 +69,7 @@ class Transaction extends Model
}
} catch (\Exception $e) {
// If schema query fails (e.g., during migrations), just use standard casts
- \Illuminate\Support\Facades\Log::warning('Failed to load JSONB column casts: ' . $e->getMessage());
+ \Illuminate\Support\Facades\Log::warning('Failed to load JSONB column casts: '.$e->getMessage());
}
// Cache for subsequent calls
diff --git a/config/database.php b/config/database.php
index 4639e0d..2226040 100644
--- a/config/database.php
+++ b/config/database.php
@@ -175,7 +175,7 @@ return [
'options' => [
'cluster' => env('REDIS_CLUSTER', 'redis'),
- 'prefix' => env('REDIS_PREFIX', Str::slug(env('APP_NAME', 'laravel'), '_') . '_database_'),
+ 'prefix' => env('REDIS_PREFIX', Str::slug(env('APP_NAME', 'laravel'), '_').'_database_'),
'persistent' => env('REDIS_PERSISTENT', false),
],
diff --git a/database/migrations/2025_11_16_000000_remove_external_data_columns_from_transactions_table.php b/database/migrations/2025_11_16_000000_remove_external_data_columns_from_transactions_table.php
index 2c931c7..efda201 100644
--- a/database/migrations/2025_11_16_000000_remove_external_data_columns_from_transactions_table.php
+++ b/database/migrations/2025_11_16_000000_remove_external_data_columns_from_transactions_table.php
@@ -12,37 +12,64 @@ return new class extends Migration
*/
public function up(): void
{
- // Use raw SQL with CASCADE to drop columns and dependent views
- DB::statement('ALTER TABLE transactions
- DROP COLUMN IF EXISTS registry_company_number CASCADE,
- DROP COLUMN IF EXISTS registry_source CASCADE,
- DROP COLUMN IF EXISTS registry_match_score CASCADE,
- DROP COLUMN IF EXISTS registry_data CASCADE,
- DROP COLUMN IF EXISTS registry_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS genesis_context CASCADE,
- DROP COLUMN IF EXISTS genesis_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS govdata_data CASCADE,
- DROP COLUMN IF EXISTS govdata_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS bundesanzeiger_data CASCADE,
- DROP COLUMN IF EXISTS bundesanzeiger_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS insolvency_data CASCADE,
- DROP COLUMN IF EXISTS insolvency_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS rss_alerts CASCADE,
- DROP COLUMN IF EXISTS rss_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS sanctions_data CASCADE,
- DROP COLUMN IF EXISTS sanctions_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS pep_data CASCADE,
- DROP COLUMN IF EXISTS pep_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS gleif_lei CASCADE,
- DROP COLUMN IF EXISTS gleif_data CASCADE,
- DROP COLUMN IF EXISTS gleif_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS eu_sanctions_data CASCADE,
- DROP COLUMN IF EXISTS eu_sanctions_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS handelsregister_data CASCADE,
- DROP COLUMN IF EXISTS handelsregister_last_refreshed_at CASCADE,
- DROP COLUMN IF EXISTS handelsregister_status CASCADE,
- DROP COLUMN IF EXISTS handelsregister_entity_id CASCADE
- ');
+ // Check if we're using PostgreSQL (production) or SQLite (testing)
+ $driver = Schema::getConnection()->getDriverName();
+
+ if ($driver === 'pgsql') {
+ // PostgreSQL: Use raw SQL with CASCADE to drop columns and dependent views
+ DB::statement('ALTER TABLE transactions
+ DROP COLUMN IF EXISTS registry_company_number CASCADE,
+ DROP COLUMN IF EXISTS registry_source CASCADE,
+ DROP COLUMN IF EXISTS registry_match_score CASCADE,
+ DROP COLUMN IF EXISTS registry_data CASCADE,
+ DROP COLUMN IF EXISTS registry_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS genesis_context CASCADE,
+ DROP COLUMN IF EXISTS genesis_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS govdata_data CASCADE,
+ DROP COLUMN IF EXISTS govdata_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS bundesanzeiger_data CASCADE,
+ DROP COLUMN IF EXISTS bundesanzeiger_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS insolvency_data CASCADE,
+ DROP COLUMN IF EXISTS insolvency_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS rss_alerts CASCADE,
+ DROP COLUMN IF EXISTS rss_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS sanctions_data CASCADE,
+ DROP COLUMN IF EXISTS sanctions_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS pep_data CASCADE,
+ DROP COLUMN IF EXISTS pep_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS gleif_lei CASCADE,
+ DROP COLUMN IF EXISTS gleif_data CASCADE,
+ DROP COLUMN IF EXISTS gleif_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS eu_sanctions_data CASCADE,
+ DROP COLUMN IF EXISTS eu_sanctions_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS handelsregister_data CASCADE,
+ DROP COLUMN IF EXISTS handelsregister_last_refreshed_at CASCADE,
+ DROP COLUMN IF EXISTS handelsregister_status CASCADE,
+ DROP COLUMN IF EXISTS handelsregister_entity_id CASCADE
+ ');
+ } else {
+ // SQLite: Use Schema Builder to drop columns (if they exist)
+ Schema::table('transactions', function (Blueprint $table) {
+ $columns = [
+ 'registry_company_number', 'registry_source', 'registry_match_score',
+ 'registry_data', 'registry_last_refreshed_at', 'genesis_context',
+ 'genesis_last_refreshed_at', 'govdata_data', 'govdata_last_refreshed_at',
+ 'bundesanzeiger_data', 'bundesanzeiger_last_refreshed_at', 'insolvency_data',
+ 'insolvency_last_refreshed_at', 'rss_alerts', 'rss_last_refreshed_at',
+ 'sanctions_data', 'sanctions_last_refreshed_at', 'pep_data',
+ 'pep_last_refreshed_at', 'gleif_lei', 'gleif_data',
+ 'gleif_last_refreshed_at', 'eu_sanctions_data', 'eu_sanctions_last_refreshed_at',
+ 'handelsregister_data', 'handelsregister_last_refreshed_at',
+ 'handelsregister_status', 'handelsregister_entity_id',
+ ];
+
+ foreach ($columns as $column) {
+ if (Schema::hasColumn('transactions', $column)) {
+ $table->dropColumn($column);
+ }
+ }
+ });
+ }
}
/**
diff --git a/misc/migrate-tables-to-archive.sql b/database/queries/migrate-tables-to-archive.sql
similarity index 100%
rename from misc/migrate-tables-to-archive.sql
rename to database/queries/migrate-tables-to-archive.sql
diff --git a/misc/playground.sql b/database/queries/playground.sql
similarity index 100%
rename from misc/playground.sql
rename to database/queries/playground.sql
diff --git a/misc/playground2.sql b/database/queries/playground2.sql
similarity index 100%
rename from misc/playground2.sql
rename to database/queries/playground2.sql
diff --git a/test_backend_query.sql b/database/queries/test-backend-query.sql
similarity index 100%
rename from test_backend_query.sql
rename to database/queries/test-backend-query.sql
diff --git a/misc/database_table_schemes/backend_transaction_outputs_output_key_.csv b/database/schemas/backend_transaction_outputs_output_key_.csv
similarity index 100%
rename from misc/database_table_schemes/backend_transaction_outputs_output_key_.csv
rename to database/schemas/backend_transaction_outputs_output_key_.csv
diff --git a/misc/database_table_schemes/backend_transaction_outputs_output_keys.csv b/database/schemas/backend_transaction_outputs_output_keys.csv
similarity index 100%
rename from misc/database_table_schemes/backend_transaction_outputs_output_keys.csv
rename to database/schemas/backend_transaction_outputs_output_keys.csv
diff --git a/misc/database_table_schemes/backend_transaction_outputs_scheme.csv b/database/schemas/backend_transaction_outputs_scheme.csv
similarity index 100%
rename from misc/database_table_schemes/backend_transaction_outputs_scheme.csv
rename to database/schemas/backend_transaction_outputs_scheme.csv
diff --git a/misc/database_table_schemes/backend_transactions_scheme.csv b/database/schemas/backend_transactions_scheme.csv
similarity index 100%
rename from misc/database_table_schemes/backend_transactions_scheme.csv
rename to database/schemas/backend_transactions_scheme.csv
diff --git a/misc/database_table_schemes/doppeltes Encoding in content_json.csv b/database/schemas/doppeltes Encoding in content_json.csv
similarity index 100%
rename from misc/database_table_schemes/doppeltes Encoding in content_json.csv
rename to database/schemas/doppeltes Encoding in content_json.csv
diff --git a/misc/database_table_schemes/DB Migration Frontend-Backend.key b/database/schemas/migration-diagrams/DB Migration Frontend-Backend.key
similarity index 100%
rename from misc/database_table_schemes/DB Migration Frontend-Backend.key
rename to database/schemas/migration-diagrams/DB Migration Frontend-Backend.key
diff --git a/misc/database_table_schemes/DB Migration Frontend-Backend.pdf b/database/schemas/migration-diagrams/DB Migration Frontend-Backend.pdf
similarity index 100%
rename from misc/database_table_schemes/DB Migration Frontend-Backend.pdf
rename to database/schemas/migration-diagrams/DB Migration Frontend-Backend.pdf
diff --git a/misc/database_table_schemes/SQL Zuordnung nach Seiten - Public Schema.xlsx b/database/schemas/migration-diagrams/SQL Zuordnung nach Seiten - Public Schema.xlsx
similarity index 100%
rename from misc/database_table_schemes/SQL Zuordnung nach Seiten - Public Schema.xlsx
rename to database/schemas/migration-diagrams/SQL Zuordnung nach Seiten - Public Schema.xlsx
diff --git a/misc/database_table_schemes/Zuordnung SQL nach Seitenaufruf - public Schema.numbers b/database/schemas/migration-diagrams/Zuordnung SQL nach Seitenaufruf - public Schema.numbers
similarity index 100%
rename from misc/database_table_schemes/Zuordnung SQL nach Seitenaufruf - public Schema.numbers
rename to database/schemas/migration-diagrams/Zuordnung SQL nach Seitenaufruf - public Schema.numbers
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue1 - Transaktion.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue1 - Transaktion.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue1 - Transaktion.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue1 - Transaktion.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue2 - Stammdaten.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue2 - Stammdaten.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue2 - Stammdaten.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue2 - Stammdaten.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue3 - Unternehmensstatus.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue3 - Unternehmensstatus.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue3 - Unternehmensstatus.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue3 - Unternehmensstatus.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue4 - Branchen.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue4 - Branchen.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue4 - Branchen.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue4 - Branchen.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue5 - Länder.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue5 - Länder.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue5 - Länder.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue5 - Länder.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue6 - Strukturen und Verpflechtungen.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue6 - Strukturen und Verpflechtungen.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue6 - Strukturen und Verpflechtungen.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue6 - Strukturen und Verpflechtungen.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue7 - Natürliche Personen.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue7 - Natürliche Personen.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue7 - Natürliche Personen.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue7 - Natürliche Personen.csv
diff --git a/misc/transactions_output_structured/transactions_details_output - Menue8 - Zusätzliche Informationen.csv b/database/schemas/output_keys_mapping/transactions_details_output - Menue8 - Zusätzliche Informationen.csv
similarity index 100%
rename from misc/transactions_output_structured/transactions_details_output - Menue8 - Zusätzliche Informationen.csv
rename to database/schemas/output_keys_mapping/transactions_details_output - Menue8 - Zusätzliche Informationen.csv
diff --git a/misc/database_table_schemes/public_companies_scheme.csv b/database/schemas/public_companies_scheme.csv
similarity index 100%
rename from misc/database_table_schemes/public_companies_scheme.csv
rename to database/schemas/public_companies_scheme.csv
diff --git a/misc/database_table_schemes/public_transactions_scheme.csv b/database/schemas/public_transactions_scheme.csv
similarity index 100%
rename from misc/database_table_schemes/public_transactions_scheme.csv
rename to database/schemas/public_transactions_scheme.csv
diff --git a/SCHEDULING_SETUP.md b/docs/scheduling-setup.md
similarity index 100%
rename from SCHEDULING_SETUP.md
rename to docs/scheduling-setup.md
diff --git a/STUFE_2_TRANSFORMATION_PLAN.md b/docs/stufe-2-transformation-plan.md
similarity index 88%
rename from STUFE_2_TRANSFORMATION_PLAN.md
rename to docs/stufe-2-transformation-plan.md
index 1a641cb..d26ed1a 100644
--- a/STUFE_2_TRANSFORMATION_PLAN.md
+++ b/docs/stufe-2-transformation-plan.md
@@ -363,30 +363,30 @@ Total Score: 22.5 → "low"
## 📋 Implementierungs-Schritte
-### Phase 1: Vorbereitung
+### Phase 1: Vorbereitung ✅ ABGESCHLOSSEN
1. ✅ Data Pool ist befüllt
-2. ⬜ KYC Risk Calculator Service erstellen
-3. ⬜ Data Extraction Helpers erstellen
-4. ⬜ Mapping-Logik definieren
+2. ✅ KYC Risk Calculator Service erstellen
+3. ✅ Data Extraction Helpers erstellen
+4. ✅ Mapping-Logik definieren
-### Phase 2: Job Implementation
-1. ⬜ TransformDataPoolToProduction Job erstellen
-2. ⬜ Company Creation Logic implementieren
-3. ⬜ Transaction Creation Logic implementieren
-4. ⬜ Error Handling & Logging
+### Phase 2: Job Implementation ✅ ABGESCHLOSSEN
+1. ✅ TransformDataPoolToProduction Job erstellen
+2. ✅ Company Creation Logic implementieren
+3. ✅ Transaction Creation Logic implementieren
+4. ✅ Error Handling & Logging
### Phase 3: Testing
1. ⬜ Unit Tests für Risk Calculator
2. ⬜ Feature Tests für Transformation Job
3. ⬜ Datenintegritäts-Checks
-### Phase 4: Scheduling
-1. ⬜ Schedule konfigurieren
-2. ⬜ Queue Setup (optional)
+### Phase 4: Scheduling ✅ ABGESCHLOSSEN
+1. ✅ Schedule konfigurieren (läuft alle 6h um :30)
+2. ✅ Queue Setup (optional)
3. ⬜ Monitoring einrichten
### Phase 5: Deployment
-1. ⬜ Produktions-Test mit echten Daten
+1. ✅ Produktions-Test mit echten Daten
2. ⬜ Performance-Optimierung
3. ⬜ Dokumentation finalisieren
@@ -424,5 +424,24 @@ Nach erfolgreicher Implementation von Stufe 2:
---
-*Erstellt am: 2025-11-16*
-*Status: PLANUNG - Wartet auf Entscheidungen zu offenen Fragen*
+## 🎉 Status Update
+
+**Erstellt am:** 2025-11-16
+**Aktualisiert am:** 2025-11-21
+**Status:** ✅ **PRODUKTIV** - Stufe 2 ist implementiert und läuft automatisch!
+
+### Was funktioniert:
+
+✅ **TransformDataPoolToProduction Job** - Vollständig implementiert
+✅ **Automatisches Scheduling** - Läuft alle 6 Stunden um :30 (0:30, 6:30, 12:30, 18:30)
+✅ **Company & Transaction Creation** - Automatische Erstellung und Updates
+✅ **Risk Score Mapping** - Verwendet Backend risk_score direkt
+✅ **Artisan Command** - `php artisan backend:transform-data-pool` verfügbar
+
+### Offene TODOs:
+
+⬜ Unit Tests für Transformation Job (Phase 3)
+⬜ Feature Tests für Transformation Job (Phase 3)
+⬜ Monitoring einrichten (Phase 4)
+⬜ Performance-Optimierung (Phase 5)
+⬜ KycRiskCalculator Service integrieren (optional, aktuell nicht genutzt)
diff --git a/SYNC_MIGRATION_INSTRUCTIONS.md b/docs/sync-migration-instructions.md
similarity index 100%
rename from SYNC_MIGRATION_INSTRUCTIONS.md
rename to docs/sync-migration-instructions.md
diff --git a/misc/ETL_PIPELINE_MIGRATION_PLAN.md b/misc/ETL_PIPELINE_MIGRATION_PLAN.md
deleted file mode 100644
index 90f9df9..0000000
--- a/misc/ETL_PIPELINE_MIGRATION_PLAN.md
+++ /dev/null
@@ -1,1414 +0,0 @@
-# ETL-Pipeline Migration: CSV → KI Workflow → Frontend
-
-## System-Architektur (Klargestellt)
-
-### Aktueller Zustand (Nicht optimal)
-```
-┌─────────────────────────────────────────────────────┐
-│ Laravel Frontend │
-│ │
-│ CSV Upload → Manual Processing │
-│ ↓ │
-│ public.companies (11 Felder) │
-│ ↓ │
-│ public.transactions (49 Felder, komplex) │
-│ - Core-Felder (14) │
-│ - Enrichment-Felder (35) │
-│ │
-└─────────────────────────────────────────────────────┘
-```
-
-**Probleme**:
-- ❌ Companies und Transactions vermischt
-- ❌ Enrichment-Logik direkt in Laravel
-- ❌ Keine klare Trennung: Raw Data vs Processed Data
-- ❌ Skalierbarkeit begrenzt
-
----
-
-### Ziel-Zustand (Backend-Pipeline)
-```
-┌──────────────────────────────────────────────────────────────┐
-│ CSV Upload │
-│ ↓ │
-│ backend.transactions (14 Felder) │
-│ - corporate_entity │
-│ - corporate_counterparty │
-│ - tx_date, tx_amount, tx_currency │
-│ - raw_payload (Original-CSV) │
-│ - status: 'pending' │
-└─────────────────────────┬────────────────────────────────────┘
- │
- ↓
-┌──────────────────────────────────────────────────────────────┐
-│ KI Workflow (Python/MCP) │
-│ │
-│ Für jede Transaction: │
-│ 1. Analyse: Risk Assessment │
-│ 2. Enrichment: External APIs │
-│ 3. Output: Strukturierte Ergebnisse │
-│ │
-│ Nutzt: backend.prompt_templates │
-│ backend.prompt_runs │
-└─────────────────────────┬────────────────────────────────────┘
- │
- ↓
-┌──────────────────────────────────────────────────────────────┐
-│ backend.transaction_outputs (5 Felder) │
-│ │
-│ - transaction_id (FK → backend.transactions.id) │
-│ - prompt_id (FK → backend.prompt_templates.id) │
-│ - output_key (z.B. 'risk_assessment', 'sanctions_check') │
-│ - content (JSON mit Ergebnissen) │
-│ - run_id (Batch-Tracking) │
-│ │
-│ Beispiel-Outputs: │
-│ • 'risk_assessment' → {score: 85, level: 'high'} │
-│ • 'sanctions_check' → {found: true, matches: [...]} │
-│ • 'pep_check' → {is_pep: false} │
-│ • 'company_info' → {name, sector, country} │
-└─────────────────────────┬────────────────────────────────────┘
- │
- ↓
-┌──────────────────────────────────────────────────────────────┐
-│ Laravel Frontend │
-│ │
-│ Liest von: │
-│ - backend.transactions (Raw Data) │
-│ - backend.transaction_outputs (Processed Results) │
-│ │
-│ Zeigt an: │
-│ - Transaction Details │
-│ - Risk Score & Assessment │
-│ - Enrichment Results (Sanctions, PEP, etc.) │
-│ - Review Queue │
-└──────────────────────────────────────────────────────────────┘
-```
-
----
-
-## Mapping: Alt → Neu
-
-### 1. Companies Table → ENTFÄLLT
-
-**Warum?**
-- Companies sind **keine separate Entität** mehr
-- Firmeninformationen kommen aus:
- 1. `backend.transactions.corporate_entity` (Name aus CSV)
- 2. `backend.transaction_outputs` mit `output_key='company_info'` (KI-Enrichment)
-
-**Migration**:
-```sql
--- Bestehende Companies werden zu Transaction Outputs
-INSERT INTO backend.transaction_outputs (
- transaction_id,
- prompt_id,
- output_key,
- content
-)
-SELECT
- bt.id as transaction_id,
- 1 as prompt_id, -- Default prompt für Company Info
- 'company_info' as output_key,
- jsonb_build_object(
- 'name', c.name,
- 'legal_name', c.legal_name,
- 'ticker', c.ticker,
- 'sector', c.sector,
- 'country', c.country,
- 'headquarters', c.headquarters,
- 'kyc_risk_level', c.kyc_risk_level,
- 'summary', c.summary
- ) as content
-FROM public.companies c
-JOIN public.transactions t ON t.company_id = c.id
-JOIN backend.transactions bt ON bt.corporate_entity = c.name;
-```
-
-### 2. Transactions Table → transaction_outputs
-
-**public.transactions (49 Felder)**:
-```
-Core-Felder (14):
-- company_id, reference, amount, currency
-- counterparty, executed_at, status
-- risk_score, requires_review
-→ Gespeichert in backend.transactions
-
-Enrichment-Felder (35):
-- registry_data, sanctions_data, pep_data, ...
-→ Jedes wird zu einem Output in transaction_outputs
-```
-
-**Mapping-Strategie**:
-
-| public.transactions Feld | Ziel | output_key |
-|--------------------------|------|------------|
-| amount, currency, counterparty | backend.transactions | - |
-| risk_score, requires_review | transaction_outputs | 'risk_assessment' |
-| registry_data | transaction_outputs | 'registry' |
-| sanctions_data | transaction_outputs | 'sanctions' |
-| pep_data | transaction_outputs | 'pep' |
-| gleif_data | transaction_outputs | 'gleif' |
-| ... | ... | ... |
-
----
-
-## Phase 1: Backend Models & Relationships (Tag 1-2)
-
-### 1.1 Database Config
-
-**config/database.php**:
-```php
-'backend' => [
- 'driver' => 'pgsql',
- 'host' => env('DB_HOST', '127.0.0.1'),
- 'port' => env('DB_PORT', '5432'),
- 'database' => env('DB_DATABASE', 'forge'),
- 'username' => env('DB_USERNAME', 'forge'),
- 'password' => env('DB_PASSWORD', ''),
- 'charset' => 'utf8',
- 'prefix' => '',
- 'search_path' => 'backend',
- 'sslmode' => 'prefer',
-],
-```
-
-### 1.2 Backend\Transaction Model
-
-**app/Models/Backend/Transaction.php**:
-```php
- 'decimal:2',
- // tx_date ist noch text - später zu timestamp migrieren
- ];
-
- /**
- * KI-generierte Outputs für diese Transaktion
- */
- public function outputs(): HasMany
- {
- return $this->hasMany(TransactionOutput::class, 'transaction_id');
- }
-
- /**
- * Hole spezifischen Output-Typ
- */
- public function getOutput(string $key): ?array
- {
- return $this->outputs()
- ->where('output_key', $key)
- ->first()
- ?->content;
- }
-
- /**
- * Hole alle Outputs als Key-Value Array
- */
- public function getOutputsArray(): array
- {
- return $this->outputs()
- ->get()
- ->pluck('content', 'output_key')
- ->toArray();
- }
-
- /**
- * Company Info aus Outputs
- */
- public function getCompanyInfo(): ?array
- {
- return $this->getOutput('company_info');
- }
-
- /**
- * Risk Assessment aus Outputs
- */
- public function getRiskAssessment(): ?array
- {
- return $this->getOutput('risk_assessment');
- }
-
- /**
- * Helper: Hat diese Transaction einen bestimmten Output?
- */
- public function hasOutput(string $key): bool
- {
- return $this->outputs()->where('output_key', $key)->exists();
- }
-
- /**
- * Ist KI-Verarbeitung abgeschlossen?
- */
- public function isProcessed(): bool
- {
- return $this->status === self::STATUS_COMPLETED;
- }
-
- /**
- * Benötigt Review?
- */
- public function requiresReview(): bool
- {
- $risk = $this->getRiskAssessment();
-
- if (!$risk) {
- return true; // Keine Risk-Assessment → Review
- }
-
- return ($risk['score'] ?? 0) >= 70 || ($risk['requires_review'] ?? false);
- }
-}
-```
-
-### 1.3 Backend\TransactionOutput Model
-
-**app/Models/Backend/TransactionOutput.php**:
-```php
- 'array', // Automatisch JSON encode/decode
- ];
-
- /**
- * Transaction zu der dieser Output gehört
- */
- public function transaction(): BelongsTo
- {
- return $this->belongsTo(Transaction::class, 'transaction_id');
- }
-
- /**
- * Prompt Template das diesen Output erzeugt hat
- */
- public function promptTemplate(): BelongsTo
- {
- return $this->belongsTo(PromptTemplate::class, 'prompt_id');
- }
-
- /**
- * Output-Key Konstanten für Type Safety
- */
- public const KEY_COMPANY_INFO = 'company_info';
- public const KEY_RISK_ASSESSMENT = 'risk_assessment';
- public const KEY_SANCTIONS = 'sanctions';
- public const KEY_PEP = 'pep';
- public const KEY_REGISTRY = 'registry';
- public const KEY_GLEIF = 'gleif';
- public const KEY_INSOLVENCY = 'insolvency';
- public const KEY_BUNDESANZEIGER = 'bundesanzeiger';
- public const KEY_RSS = 'rss';
- public const KEY_EU_SANCTIONS = 'eu_sanctions';
- public const KEY_HANDELSREGISTER = 'handelsregister';
-
- /**
- * Alle verfügbaren Output-Keys
- */
- public static function availableKeys(): array
- {
- return [
- self::KEY_COMPANY_INFO,
- self::KEY_RISK_ASSESSMENT,
- self::KEY_SANCTIONS,
- self::KEY_PEP,
- self::KEY_REGISTRY,
- self::KEY_GLEIF,
- self::KEY_INSOLVENCY,
- self::KEY_BUNDESANZEIGER,
- self::KEY_RSS,
- self::KEY_EU_SANCTIONS,
- self::KEY_HANDELSREGISTER,
- ];
- }
-}
-```
-
-### 1.4 Backend\PromptTemplate Model (optional)
-
-**app/Models/Backend/PromptTemplate.php**:
-```php
-hasMany(TransactionOutput::class, 'prompt_id');
- }
-}
-```
-
----
-
-## Phase 2: CSV Upload Service (Tag 3-4)
-
-### 2.1 CSV Upload Controller
-
-**app/Http/Controllers/TransactionUploadController.php**:
-```php
-validate([
- 'csv_file' => 'required|file|mimes:csv,txt|max:10240', // 10MB
- ]);
-
- try {
- $result = $this->uploadService->process($validated['csv_file']);
-
- return redirect()
- ->route('transactions.index')
- ->with('success', "Imported {$result['count']} transactions. Processing started.");
- } catch (\Exception $e) {
- return back()
- ->withErrors(['csv_file' => $e->getMessage()])
- ->withInput();
- }
- }
-}
-```
-
-### 2.2 Upload Service
-
-**app/Services/TransactionUploadService.php**:
-```php
-storeFile($file);
-
- // 2. Parse CSV
- $rows = $this->parseCsv($file);
-
- // 3. Validiere Daten
- $this->validate($rows);
-
- // 4. Importiere zu backend.transactions
- $transactions = $this->import($rows, $fileName);
-
- // 5. Starte KI-Verarbeitung (async)
- $this->queueAiProcessing($transactions);
-
- return [
- 'count' => count($transactions),
- 'file' => $fileName,
- ];
- }
-
- /**
- * Speichere Original-CSV für Audit
- */
- private function storeFile(UploadedFile $file): string
- {
- return Storage::disk('local')->putFileAs(
- 'uploads/transactions',
- $file,
- date('Y-m-d_His') . '_' . $file->getClientOriginalName()
- );
- }
-
- /**
- * Parse CSV-Datei
- */
- private function parseCsv(UploadedFile $file): array
- {
- $handle = fopen($file->getRealPath(), 'r');
- $headers = fgetcsv($handle); // Erste Zeile = Header
-
- $rows = [];
- while (($data = fgetcsv($handle)) !== false) {
- $rows[] = array_combine($headers, $data);
- }
-
- fclose($handle);
-
- return $rows;
- }
-
- /**
- * Validiere CSV-Daten
- */
- private function validate(array $rows): void
- {
- if (empty($rows)) {
- throw new \InvalidArgumentException('CSV file is empty');
- }
-
- $requiredColumns = [
- 'corporate_entity',
- 'corporate_counterparty',
- 'tx_date',
- 'tx_amount',
- ];
-
- $headers = array_keys($rows[0]);
- $missing = array_diff($requiredColumns, $headers);
-
- if (!empty($missing)) {
- throw new \InvalidArgumentException(
- 'Missing required columns: ' . implode(', ', $missing)
- );
- }
- }
-
- /**
- * Importiere Transaktionen
- */
- private function import(array $rows, string $fileName): array
- {
- $transactions = [];
-
- DB::connection('backend')->transaction(function () use ($rows, $fileName, &$transactions) {
- foreach ($rows as $row) {
- $transactions[] = Transaction::create([
- 'corporate_entity' => $row['corporate_entity'],
- 'corporate_counterparty' => $row['corporate_counterparty'],
- 'tx_date' => $row['tx_date'],
- 'tx_amount' => (float) $row['tx_amount'],
- 'tx_currency' => $row['tx_currency'] ?? 'EUR',
- 'tx_purpose' => $row['tx_purpose'] ?? null,
- 'tx_country_outgoing' => $row['tx_country_outgoing'] ?? null,
- 'tx_country_incoming' => $row['tx_country_incoming'] ?? null,
- 'source_file' => $fileName,
- 'raw_payload' => json_encode($row),
- 'status' => Transaction::STATUS_PENDING,
- ]);
- }
- });
-
- return $transactions;
- }
-
- /**
- * Starte KI-Verarbeitung für alle Transaktionen
- */
- private function queueAiProcessing(array $transactions): void
- {
- foreach ($transactions as $transaction) {
- ProcessTransactionWithAI::dispatch($transaction);
- }
- }
-}
-```
-
----
-
-## Phase 3: KI Workflow Integration (Tag 5-7)
-
-### 3.1 AI Processing Job
-
-**app/Jobs/ProcessTransactionWithAI.php**:
-```php
-transaction->update(['status' => Transaction::STATUS_PROCESSING]);
-
- try {
- // 1. Company Info Enrichment
- $companyInfo = $aiService->enrichCompanyInfo($this->transaction);
- $this->storeOutput('company_info', $companyInfo);
-
- // 2. Risk Assessment
- $riskAssessment = $aiService->assessRisk($this->transaction);
- $this->storeOutput('risk_assessment', $riskAssessment);
-
- // 3. Sanctions Check
- $sanctionsCheck = $aiService->checkSanctions($this->transaction);
- $this->storeOutput('sanctions', $sanctionsCheck);
-
- // 4. PEP Check
- $pepCheck = $aiService->checkPep($this->transaction);
- $this->storeOutput('pep', $pepCheck);
-
- // 5. Weitere Checks (conditional)
- if ($riskAssessment['score'] >= 50) {
- $registryData = $aiService->checkRegistry($this->transaction);
- $this->storeOutput('registry', $registryData);
- }
-
- // Fertig
- $this->transaction->update(['status' => Transaction::STATUS_COMPLETED]);
-
- } catch (\Exception $e) {
- $this->transaction->update([
- 'status' => Transaction::STATUS_FAILED,
- ]);
-
- // Store Error Output
- $this->storeOutput('error', [
- 'message' => $e->getMessage(),
- 'trace' => $e->getTraceAsString(),
- ]);
-
- throw $e;
- }
- }
-
- private function storeOutput(string $key, array $data): void
- {
- TransactionOutput::create([
- 'transaction_id' => $this->transaction->id,
- 'prompt_id' => 1, // TODO: Map zu echtem Prompt Template
- 'output_key' => $key,
- 'content' => $data,
- 'run_id' => null, // TODO: Track Batch-Runs
- ]);
- }
-}
-```
-
-### 3.2 AI Workflow Service (Stub)
-
-**app/Services/AiWorkflowService.php**:
-```php
- $transaction->corporate_entity,
- 'legal_name' => null,
- 'country' => $transaction->tx_country_outgoing,
- 'sector' => 'Unknown',
- 'kyc_risk_level' => 'medium',
- 'enriched_at' => now()->toIso8601String(),
- ];
- }
-
- /**
- * Risk Assessment
- */
- public function assessRisk(Transaction $transaction): array
- {
- // TODO: Echte Risk-Logik via KI
-
- $amount = (float) $transaction->tx_amount;
- $score = 0;
-
- // Einfache Heuristik
- if ($amount > 100000) {
- $score += 30;
- }
- if ($transaction->tx_country_incoming !== 'DE') {
- $score += 20;
- }
-
- return [
- 'score' => $score,
- 'level' => $score >= 70 ? 'high' : ($score >= 40 ? 'medium' : 'low'),
- 'requires_review' => $score >= 70,
- 'factors' => [
- 'high_amount' => $amount > 100000,
- 'foreign_country' => $transaction->tx_country_incoming !== 'DE',
- ],
- 'assessed_at' => now()->toIso8601String(),
- ];
- }
-
- /**
- * Sanctions Check
- */
- public function checkSanctions(Transaction $transaction): array
- {
- // TODO: API zu Sanktionslisten
-
- return [
- 'checked' => true,
- 'found' => false,
- 'matches' => [],
- 'sources' => ['EU', 'OFAC'],
- 'checked_at' => now()->toIso8601String(),
- ];
- }
-
- /**
- * PEP Check
- */
- public function checkPep(Transaction $transaction): array
- {
- // TODO: PEP Database Check
-
- return [
- 'is_pep' => false,
- 'confidence' => 0.0,
- 'matches' => [],
- 'checked_at' => now()->toIso8601String(),
- ];
- }
-
- /**
- * Registry Check
- */
- public function checkRegistry(Transaction $transaction): array
- {
- // TODO: Handelsregister API
-
- return [
- 'found' => false,
- 'company_number' => null,
- 'match_score' => 0.0,
- 'data' => null,
- 'checked_at' => now()->toIso8601String(),
- ];
- }
-}
-```
-
----
-
-## Phase 4: Frontend Anpassung (Tag 8-10)
-
-### 4.1 Transaction Repository
-
-**app/Repositories/TransactionRepository.php**:
-```php
-orderBy('created_at', 'desc')
- ->get();
- }
-
- /**
- * Transaktionen die Review benötigen
- */
- public function requiresReview(): Collection
- {
- return Transaction::with('outputs')
- ->where('status', Transaction::STATUS_COMPLETED)
- ->get()
- ->filter(fn($t) => $t->requiresReview());
- }
-
- /**
- * High-Risk Transaktionen
- */
- public function highRisk(int $threshold = 70): Collection
- {
- return $this->allWithOutputs()
- ->filter(function ($transaction) use ($threshold) {
- $risk = $transaction->getRiskAssessment();
- return ($risk['score'] ?? 0) >= $threshold;
- });
- }
-
- /**
- * Transaktionen nach Firma
- */
- public function byCompany(string $companyName): Collection
- {
- return Transaction::with('outputs')
- ->where('corporate_entity', $companyName)
- ->orderBy('tx_date', 'desc')
- ->get();
- }
-
- /**
- * Statistiken
- */
- public function stats(): array
- {
- $total = Transaction::count();
- $pending = Transaction::where('status', Transaction::STATUS_PENDING)->count();
- $processing = Transaction::where('status', Transaction::STATUS_PROCESSING)->count();
- $completed = Transaction::where('status', Transaction::STATUS_COMPLETED)->count();
- $failed = Transaction::where('status', Transaction::STATUS_FAILED)->count();
-
- return compact('total', 'pending', 'processing', 'completed', 'failed');
- }
-}
-```
-
-### 4.2 Transaction Controller
-
-**app/Http/Controllers/TransactionController.php**:
-```php
-transactions->allWithOutputs();
- $stats = $this->transactions->stats();
-
- return view('transactions.index', compact('transactions', 'stats'));
- }
-
- public function show(int $id)
- {
- $transaction = $this->transactions->find($id);
-
- if (!$transaction) {
- abort(404);
- }
-
- return view('transactions.show', compact('transaction'));
- }
-
- public function review()
- {
- $transactions = $this->transactions->requiresReview();
-
- return view('transactions.review', compact('transactions'));
- }
-}
-```
-
-### 4.3 Volt Component für Transaction List
-
-**resources/views/pages/transactions/index.blade.php**:
-```php
- $transactionRepo->allWithOutputs());
-$stats = computed(fn() => $transactionRepo->stats());
-
-?>
-
-