forked from fa/breadcrumb-the-shire
fs
0e86925464
Rename the top-level lib/ directory to core/ so the project root immediately communicates which code is core platform and which lives in modules/. PHP namespaces (MintyPHP\*) are unchanged — only the Composer PSR-4 path mapping moves from lib/ to core/. Module-internal lib/ directories (modules/*/lib/) are untouched. Updated across the full stack: - composer.json PSR-4 mapping - bootstrap entry points (web/index.php, bin/*, tests/bootstrap.php) - tooling configs (phpstan.neon, phpunit.xml, php-cs-fixer) - 26 architecture contract tests - enforcement-policy, guard-catalog, quality-gates - all documentation (CLAUDE.md, README, 25 docs/, .agents/skills/) - bin/qa-extended.sh search paths - .claude/settings.local.json permission paths Workflow: .agents/runs/CORE-LIB-RENAME-001/ (Analyst → Planner → Executor → Code Review (4 findings fixed) → Security Review → Acceptance Test → Finalizer) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
87 lines
3.0 KiB
Markdown
87 lines
3.0 KiB
Markdown
# Architektur und Request-Flow
|
|
|
|
Letzte Aktualisierung: 2026-03-06
|
|
|
|
## Ziel
|
|
|
|
Verstehen, wo Änderungen hingehören und wo nicht.
|
|
|
|
## Request-Flow
|
|
|
|
1. `web/index.php` lädt Bootstrap, registriert den `AppContainer` und setzt globale Service-Auflösung.
|
|
2. `RequestContext` initialisiert `request_id` und Basis-Metadaten; `X-Request-Id` wird gesetzt.
|
|
3. Guard/Sicherheitslayer laufen.
|
|
4. Action in `pages/**` nimmt Input an.
|
|
5. Action delegiert an Service.
|
|
6. Service nutzt Repository für Datenzugriff.
|
|
7. Response wird als HTML/JSON ausgegeben.
|
|
|
|
API-Ergänzung:
|
|
|
|
1. `ApiBootstrap::init()` startet API-Audit (`ApiAuditService`) und API-System-Audit (`ApiSystemAuditReporter`).
|
|
2. `ApiResponse::send()` finalisiert beide Reporter (inkl. `request_id`-Korrelation).
|
|
3. System-Protokolle schreiben nur selektive `api.request`-Events (kein Voll-Request-Logging).
|
|
|
|
## Schichtregeln
|
|
|
|
- `pages/**`: Input, Auth/AuthZ, Service-Aufruf, Response.
|
|
- `core/Service/**`: Business-Regeln und Orchestrierung.
|
|
- `core/Repository/**`: SQL, Filter, Mapping.
|
|
- `templates/**`: Rendering ohne Business-Logik.
|
|
- Request-Daten in Actions nur über `requestInput()` (keine Input-Superglobals).
|
|
- Validierungsfehler zentral über `FormErrors`; API-Fehler über `ApiResponse::validationFromFormErrors(...)`.
|
|
- Template-AuthZ konsumiert nur vorbereitete `$viewAuth`-Daten (kein `can('...')` im Template).
|
|
- Service-Auflösung in Actions/Helpern über `app(Foo::class)`.
|
|
- Fachliche Audit-Events laufen zentral über `SystemAuditService`.
|
|
- Persistierte Status/Outcome-Werte laufen über die zentrale Taxonomie-Schicht `core/Domain/Taxonomy/*` (Enums + DB-Checks).
|
|
- `pages/**/data().php` sind GET-only (`gridRequireGetRequest()`) und normalisieren `limit`/`offset`/`order`/`dir` über Grid-Helper.
|
|
|
|
## Einfaches ASCII-Beispiel
|
|
|
|
Beispiel: `GET /admin/users/data`
|
|
|
|
```text
|
|
Browser
|
|
-> web/index.php (Bootstrap + AppContainer)
|
|
-> pages/admin/users/data().php (Action)
|
|
-> Guard + AuthorizationService (Auth/AuthZ)
|
|
-> UserAccountService (Fachlogik)
|
|
-> UserListQueryRepository (SQL + Filter + Paging)
|
|
-> DB
|
|
<- { data, total } JSON
|
|
```
|
|
|
|
Factory/Gateway im selben Bild:
|
|
|
|
```text
|
|
AppContainer
|
|
-> UserServicesFactory
|
|
-> createUserAccountService() -> UserAccountService
|
|
|
|
Guard::requireAbilityOrForbidden(ops....)
|
|
-> app(AuthorizationService::class)
|
|
-> AccessPolicyFactory -> *AuthorizationPolicy
|
|
-> PermissionGateway -> PermissionService -> PermissionRepository -> DB
|
|
|
|
Front Controller (web/index.php)
|
|
-> app(UiAccessService::class)
|
|
-> UiCapabilityMap::LAYOUT -> $viewAuth['layout']
|
|
|
|
Action
|
|
-> app(UiAccessService::class)
|
|
-> UiCapabilityMap::* -> $viewAuth['page']
|
|
-> templates/** (nur Darstellung)
|
|
```
|
|
|
|
## Absolute No-Go's
|
|
|
|
- SQL in View-Dateien
|
|
- Business-Logik in Actions
|
|
- Tenant-Scope als UI-Only-Check
|
|
|
|
## Vertiefung
|
|
|
|
- Vollständiger Kompass: `/docs/explanation-architektur.md`
|
|
- Regeln für `core/**`: `/docs/reference-core-standards.md`
|
|
- RBAC-Rechte erweitern: `/docs/howto-rbac-permissions-playbook.md`
|