Core PHP
Core PHP is the modular Laravel foundation behind LTHN. It covers multi-tenancy, service registration, admin surfaces, API delivery, and the agent runtime contract.
7+
First-party packages
Event-driven
Module boot model
Workspace scoped
Tenant boundary
Livewire + Flux
UI baseline
What ships with it
Modular monolith, not a loose bundle
Boot providers, lifecycle events, and domain-specific websites keep features isolated without fragmenting the application.
Tenant safety by default
Workspace-scoped models and request context prevent data bleed between customers, projects, and agent workspaces.
Operational packages ship together
Admin, API, MCP, commerce, content, service definitions, and agent orchestration are designed to compose cleanly.
Patterns are part of the contract
Actions, service definitions, activity logging, and lazy-loading events are documented and expected across the codebase.
Surface area
Framework core
core/php
Service providers, front-end bootstrapping, tenancy, configuration, helpers, and search primitives.
Agent runtime
lthn/agent
Plans, phases, sessions, workspace state, API key auth, and MCP tool registration for agent work.
Public API
lthn/api
Subdomain API delivery, auth scopes, human-readable guides, and generated OpenAPI explorers.
MCP layer
lthn/mcp
Registry, portal, request logs, quotas, and tool analytics for AI clients and operators.
Package baseline
The package contract lives on the docs site, with dedicated sections for the framework, API package, MCP package, and the agent runtime.
{
"require": {
"core/php": "*",
"lthn/agent": "dev-main",
"lthn/api": "dev-main",
"lthn/mcp": "*"
}
}
Read the contract
Core PHP docs
Read the framework guides for actions, modules, tenancy, service contracts, testing, and performance.
OpenAgent package contract
Architecture, API keys, MCP tools, and security for the server-side agent package.
OpenPlatform RFC
Reference the platform-level design standard that this application implements.
OpenStart from the package contract, then wire the website modules.
That keeps the public pages, MCP portal, and API surface aligned with the same underlying conventions.