Pyle

Supporting Platform Capabilities ​

Supporting Platform Capabilities is the domain that makes the rest of Pyle operable: it controls who can access the system, how records sync or move in and out, how search is indexed and queried, and how operators review system or business history.

This first pass treats the domain as four connected layers:

  • identity and access governance
  • integration and data exchange
  • search and discovery infrastructure
  • activity and collaboration history

Status ​

  • [x] Domain overview written
  • [x] Subdomains reviewed
  • [x] Technical node pages linked
  • [x] End-user concept pages linked
  • [x] Task guides linked

Responsibility ​

This domain is responsible for:

  • defining user, role, and permission behavior for admin and storefront access
  • supporting staff-management and permission-assignment workflows
  • exposing ERP bridge sync plumbing and request-log review surfaces
  • running Excel-based imports and exports with queued processing and result tracking
  • indexing searchable models and powering storefront fast search
  • surfacing activity history, parsed audit timelines, and adjacent comment records on operational pages

Subdomains ​

  • Identity And Access Governance
    • User
    • roles
    • permissions
    • staff classification
    • storefront permission pages
  • Integration And Data Exchange
    • ERP Bridge
    • Excel Import / Export
    • sync services
    • request logs
  • Search And Discovery Infrastructure
    • Fast Search
    • model-level Scout searchability
    • storefront query, filter, and sort flows
  • Activity And Collaboration History
    • Activity Log
    • parsed timelines
    • comments
    • sale activities

Classification Decisions ​

Standalone technical pages ​

Standalone end-user pages ​

Standalone task guides ​

Folded into parent pages for now ​

  • Role
    • folded into User / Role / Permissions because the packaged admin UX manages roles as part of the broader staff and permission system rather than as a separate first-pass concept page
  • Permission
    • folded into User / Role / Permissions because permission assignment is coupled tightly to user and role flows
  • Comment
    • folded into Activity Log because comments are an adjacent collaboration record shown on operational pages rather than a standalone history workspace
  • SaleActivity
    • folded into Activity Log because it is part of the broader per-record timeline story
  • RequestLog
    • folded into ERP Bridge because it is the concrete review surface for ERP sync traffic rather than a broader business concept
  • low-level model search() usage
    • folded into Fast Search because the first-pass documentation goal is the packaged search capability, not a page for every searchable trait usage

Explicitly deferred for a later pass ​

  • webhooks
  • maintenance
  • data feeds
  • filesystem disks
  • notifications
  • feature flags

These are real platform capabilities, but they would expand this batch beyond the first-pass scope already tracked in the to-do plan.

Evidence Highlights ​

Framework ownership ​

  • packages/framework/src/Models/User.php
  • packages/framework/src/Models/ExcelImport.php
  • packages/framework/src/Models/ExcelExport.php
  • packages/framework/src/Models/ExcelImportLog.php
  • packages/framework/src/Models/Comment.php
  • packages/framework/src/Actions/Excel
  • packages/framework/src/Policies/Actions/ExcelImport
  • packages/framework/src/Policies/Actions/ExcelExport
  • packages/framework/src/Actions/FastSearch/SearchProducts.php
  • packages/framework/src/Services/ErpBridge

Admin and operations surfaces ​

  • packages/admin/routes/web.php
  • packages/admin/src/Livewire/Admin/Staff
  • packages/admin/src/Livewire/Admin/Tools/Excel
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge
  • packages/admin/src/Livewire/Admin/ActivityLog
  • packages/admin/src/Livewire/Admin/Comments
  • packages/framework/routes/admin.php

Storefront and user-facing surfaces ​

  • packages/storefront/src/Livewire/Storefront/Search
  • packages/storefront/src/Livewire/Storefront/FastSearch
  • packages/storefront/src/Livewire/Storefront/Navigation/SearchForm.php
  • packages/storefront/src/Livewire/Storefront/MyAccount/Permissions

Core behavior and automation ​

  • packages/framework/src/Actions/User/AssignRoles.php
  • packages/framework/src/Actions/User/AssignPermissions.php
  • packages/framework/src/Actions/Excel/ImportCreate.php
  • packages/framework/src/Actions/Excel/ExportCreate.php
  • packages/framework/src/Actions/Excel/ExcelImporter.php
  • packages/framework/src/Actions/Excel/ExcelExporter.php
  • packages/framework/src/Actions/Excel/ExportDownload.php
  • packages/framework/src/Actions/Excel/SetImportStatus.php
  • packages/framework/src/Actions/Excel/SetExportStatus.php
  • packages/framework/src/Actions/ActivityLog/ActivityLogParser.php
  • packages/framework/src/Listeners/SyncSearchable.php
  • packages/framework/src/Actions/Searchable/SyncModelToSearchable.php
  • User / Role / Permissions is intentionally one technical page because the packaged admin UX treats those records as one governance system.
  • ERP Bridge crosses package boundaries: the shared framework owns the sync actions and services, while the request-log review surface depends on the separate erp-bridge package.
  • Excel Import / Export is a packaged operator tool with concrete admin UI, queued jobs, status records, and email completion notifications.
  • Fast Search is not the same thing as every generic search() call in the repo. This page focuses on the storefront fast-search capability and the indexing infrastructure it depends on.
  • Activity Log is mostly experienced as a per-record timeline dialog or section, not as one monolithic admin index page.

Priority Technical Pages ​

Priority End-User Pages ​

Priority Task Guides ​