App Library
Evidence gathered from the current module files before writing the user guide pages.
Research Sources Inspected
Source path
modules/Applications
Feature flags marked true
- Controllers
- Models
- Views
- Language
- Permissions
- Left Menu
- Default Menu
- Routes
- Migrations
- Api Endpoints
- Helpers
Evidence Summary
Manifest
module.json defines slug applications, version 1.0.0, category System, and the module capability flags used in this guide.
Runtime surface
4 controller file(s), 22 view file(s), and 10 route mapping(s) were found.
Data surface
11 model file(s), 12 declared table(s), and 13 migration file(s) were found.
Operations surface
9 permission key(s), 0 job(s), 1 seeder(s), and 2 test file(s) were found.
Detailed File Evidence
Controllers and methods
ApplicationsApplications_adminApplications_api- apps, app, versions, manifest, reviews, categories, tagsApplications_euapi- apps, app, versions, manifest, reviews, myDownloads, appDashboard, submitReview, recordDownload
Jobs and schedules
No scheduled module jobs were found.
Routes sampled
| Route | Target |
|---|---|
apps | Applications/index |
apps/catalog_data | Applications/catalog_data |
apps/my_downloads | Applications/my_downloads |
apps/download/(:num) | Applications/download/$1 |
apps/manage | Applications_admin/index |
apps/manage/(:any)/(:any) | Applications_admin/$1/$2 |
apps/manage/(:any) | Applications_admin/$1 |
apps/(:any)/manifest | Applications/manifest/$1 |
apps/(:any)/review | Applications/submit_review/$1 |
apps/(:any) | Applications/view/$1 |
README topics
- Layout
- Make it visible
- Demo seeder
- Tests
- Dual API
- Integration (Client) API - `GET /api/v1/applications/*` (READ-ONLY, scope `applications:read`)
- End-User API - `/v1/api/applications/*` (JWT bearer, gated `module_applications`)
- Wiring & OpenAPI
- Contracts
Operating Implications
- Permission coverage is part of the module contract, so every workflow should be tested with a role-limited user and an administrator.
- The module has migrations, so fresh installs and tenant databases need migration validation before go-live.
- The module has a public or portal-facing surface, so privacy review and logged-out testing are required.
- The module has API documentation or routes, so response examples and query filters should stay aligned with user-facing screens.
- Seeders exist for sample or starter data; operators should know whether seeded records are demo-only or operational defaults.
Known Risks from the Manifest
No explicit known_risks list was found in the module manifest. Keep normal module controls in place and validate permissions, data, and public surfaces during QA.