Server runtime, Laravel, native Android and iOS, desktop applications, packages, architecture, security, performance, production operations, and every public component contract—documented in one place.
Read the docs · Server runtime · Laravel · Native mobile · Desktop · Contributing
PAM is not one binary with a few side projects. It is a coherent PHP application platform spanning persistent servers, Laravel production operations, real native mobile interfaces, secure desktop applications, and a PAM-first package ecosystem that remains fully compatible with Composer.
Official capabilities are installed through the PAM CLI:
pam packages
pam add auth
pam add maps
pam add observability
pam doctorPAM performs package metadata lookup, dependency compatibility preflight,
updates the normal Composer manifest and lockfile, and refreshes native
integration where required. Package authors and advanced interoperability flows
can still use pam composer; application documentation should lead with
pam add <capability> whenever an official alias exists.
This repository explains that platform without hiding the hard parts. The documentation records public APIs, architectural ownership, lifecycle, protocol limits, security boundaries, performance evidence, compatibility status, release provenance, and known limitations. Ambition is welcome here; unsupported claims are not.
| Area | What it covers |
|---|---|
| Introduction | Why PAM exists and how the ecosystem fits together |
| Server runtime | Persistent PHP, Tokio, Fibers, HTTP, async I/O and production |
| Laravel | Long-lived Laravel, isolation, workers, observability and deployment |
| PAM Native | Android/iOS, components, lifecycle, global store, media and native APIs |
| PAM Desktop | Servo host, capabilities, plugins, security and distribution |
| Packages | First-party Composer APIs and interoperability |
npm install
npm run devRun the complete quality gate before publishing:
npm run validateValidation checks Astro content and types, builds the static site, verifies internal links, and runs the accessibility contract.
Every significant capability should include:
- a clear user outcome;
- a copyable example;
- the architecture or ownership boundary that matters;
- security and performance constraints;
- platform or version limitations;
- links from the correct navigation section; and
- executable evidence where the repository provides it.
See the documentation contribution guide for the complete publishing contract.