Skip to content

Project status

PAM 1.0 is a stable compatibility contract for the documented CLI, runtime, package, editor, and native-host interfaces. “Stable” does not mean that every third-party PHP package, device, or workload has been tested. The table below separates released evidence from application-owner responsibilities.

Surface PAM 1.0 contract Application-owner boundary
CLI and project lifecycle Interactive launcher/init; contextual dev, generation, package, quality, doctor, build, and release commands Project-specific scripts and credentials
Server runtime Linux x86_64/ARM64, PHP 8.5 Embed by default, HTTP 1.1/2/3, streams, async I/O, supervised workers Workload soak tests and extension safety
Laravel host Laravel 12 and 13 executable matrix; Artisan and request isolation Package globals and one active request per worker
PAM Native Android API 26–36, arm64-v8a/x86_64, PHP 8.4/8.5, signed APK/AAB tooling Keystore, Play Console, and physical-device QA
PAM Native iOS iOS 15 baseline; iOS 18 extension matrix; PHP 8.4/8.5; generated UIKit host; simulator runtime; archive/IPA tooling Apple team, certificates, profiles, App Store, and physical-device QA
Editor tooling .pam formatter/LSP plus managed VS Code, Neovim, and Helix setup Editor-specific custom configuration
First-party Composer packages Versioned API, socket, PSR bridge, testing, core contracts, and skeleton splits Third-party package compatibility
PAM Desktop Contextual CLI delegation and generated starter Follow the independent PAM Desktop platform matrix

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

Laravel 12 and 13 are tested with SQLite, MySQL, PostgreSQL, Redis, database queues, Artisan, Sanctum, Scout, Livewire, Inertia, Reverb, Telescope, and Pulse. Horizon and Socialite are exercised where their stable Composer constraints allow them. Laravel runs one request at a time per worker; scale through supervised workers.

PHP owns state and composition, Rust validates and reconciles the retained tree, and Kotlin or Swift commits bounded mutation batches on the platform UI thread. Android certification builds and runs real generated hosts. iOS certification generates projects from scratch, resolves plugins through Composer after a dry-run, compiles every app-extension target, installs the app, launches it, and confirms the embedded PHP process remains alive in a real simulator.

The iOS extension matrix covers Share Extension, Health, Media, Widgets, App Intents, and Live Activities at compatible deployment targets. Physical-device and store validation cannot be universal because signing identities, provisioning, entitlements, and devices belong to each application team.

Native protocol IDs and every coded status, type, state, kind, and variant use sequential integer enums beginning at 1. Existing identifiers are not reused inside a protocol version. Project and package commands expose deterministic non-interactive forms and stable JSON where automation needs it.

See the PAM 1.0 release record for exact artifacts and CI evidence.