Project status

PAM is public-facing software under active development. This page is intentionally conservative: “implemented” means code exists and the documented contract is exercised; it does not mean every workload or third-party package is production-safe.

Surface	Status	Supported today	Important gaps
Server runtime	Experimental	Linux x86_64/ARM64, PHP 8.4, HTTP 1.1/2/3, streams, async I/O	Broader platform and production adoption
Laravel host	Experimental, tested	Laravel 12 and 13; OTLP, process supervisor, local/remote releases, autoscaling, MCP	One concurrent request per worker; app/package global state remains your responsibility
PAM Native	Experimental	Android API 26–36; Swift/UIKit protocol peer and renderer	iOS host, packaging, device CI, accessibility, and measured parity
PAM Mobile UI	Experimental per component	61 catalog entries with individual Android parity evidence	Component maturity differs; iOS matrix is not yet part of the parity artifact
PAM Desktop	Stable API 1 on Linux x86-64	Servo host, native shell, plugins, signed updates, reproducible .tar.gz, optional .deb	Windows/macOS distribution and broader compositor/GPU certification
First-party Composer packages	Experimental	API, socket, PSR bridge, testing, core contracts	Stable 1.0 API guarantees

Server and Laravel

The runtime persists PHP, schedules native I/O through Tokio, supports isolated request Fibers for native PAM applications, supervises workers, exposes health and Prometheus endpoints, and includes operational diagnostics.

Laravel 12 and 13 are tested with Eloquent on SQLite, MySQL, and PostgreSQL; Redis; database queues; Artisan; scheduler discovery; Sanctum; Flysystem; Blade; Livewire; Inertia; Scout; Reverb; Telescope; and Pulse. Horizon and Socialite are exercised on Laravel 12 because their current stable Composer constraints do not accept Laravel 13.

The production package adds W3C-compatible OTLP traces, Nightwatch process integration, managed processes, local atomic releases, PAM Cloud and Forge operations, autoscaling, and a mutation-gated MCP server. The compatibility registry tracks 44 packages through public certification artifacts.

Laravel runs one request at a time per worker. Scale through supervised workers, and independently supervise queues, Horizon, and scheduler processes.

Native mobile

PAM Native renders real Android Views and has a Swift/UIKit renderer for iOS. PHP owns state and composition, Rust validates, reconciles, diffs, and lays out the tree, while Kotlin or Swift commits native mutations on the platform UI thread.

The iOS source includes protocol v1 decoding, runtime/batch ownership, UIKit node mapping, custom native views, storage/HTTP/system modules, advanced press/input/modal/image events, refresh, drawer, scroll, and end-reached behavior.

Do not confuse implementation with release support

iOS is now implemented at the renderer/runtime layer, but it is not a verified distribution target. A complete app host and packaging flow, simulator/device matrix, cross-platform golden tests, accessibility pass, and physical performance evidence remain open.

Mobile UI

The component catalog contains 61 entries. Each entry records a sequential integer category, maturity level, implementation kind, examples, and ten verification gates. Some components are native primitives, some are composed PHP components, and some exist for compatibility or authoring structure.

Use the parity record rather than the component name alone when deciding whether a component is ready for your application.

Desktop

PAM Desktop 1.1.2 supports local HTML/CSS/JavaScript rendered by Servo; typed commands and events; reusable multiple windows; deadlines and cancellation; crash recovery; hot reload; capability-gated filesystem, dialogs, clipboard, notifications, and drag-and-drop; menus, tray behavior, global shortcuts, background jobs, PHP and supervised Rust plugins; signed Ed25519 updates with rollback; and reproducible self-contained Linux distribution.

Public API 1, worker protocol 6, and Rust plugin protocol 1 are compatibility gated. Windows and macOS packaging remain experimental and unpublished; Linux graphics-stack variation still requires qualification on the target compositor, GPU driver, and oldest supported glibc baseline.

See the current release record for exact artifacts and verification evidence.

Ways to help

The highest-impact contribution areas are:

1. completing the iOS host, packaging, device CI, and parity verification;
2. component parity and accessibility verification;
3. Windows and macOS desktop packaging;
4. reproducible compatibility fixtures for real Composer packages;
5. documentation examples and technical review; and
6. benchmarks that follow the published protocol instead of marketing-only numbers.