Loom73 Backend¶

The Loom73 backend is organized by responsibility.

Each core namespace owns one recurring application concern. Application controllers combine those components into concrete behavior without hiding the request flow.

Woodframe  application structure and shared services
Beam       database access
Heddle     authentication and authorization
Yarn       uploaded assets
Ledger     audit trail
Weave      application controllers and responses
Shuttle    command-line operations

This reference follows the namespaces rather than creating one page for every class. Each namespace page contains a class index and stable headings for individual class contracts.

Find documentation by task¶

I need to…	Read
Read configuration or define a module	Woodframe: Config
Create a controller or handle a request	Woodframe: Ctrl and MVC
Render a view	Woodframe: Template
Redirect with user feedback	Woodframe: Flash
Write an operational error	Woodframe: Logger
Send email	Woodframe: Mailman
Register application owner types	Woodframe: OwnerRegistry
Connect to the database	Beam: Connection
Create a model or execute SQL	Beam: Model
Interpret a database result	Beam: QueryResult
Authenticate a user	Heddle
Apply roles or abilities	Heddle: authorization
Validate and store an upload	Yarn
Deliver a stored file	Yarn: delivery
Record an auditable action	Ledger
Add an application controller	Weave
Expose a JSON resource	API
Add or run a CLI command	Shuttle
Understand the complete request flow	MVC
Deploy an instance	Deployment

Namespace map¶

Woodframe¶

Loom73\Woodframe\Config
Loom73\Woodframe\Ctrl
Loom73\Woodframe\Template
Loom73\Woodframe\Flash
Loom73\Woodframe\Logger
Loom73\Woodframe\Mailman
Loom73\Woodframe\OwnerRegistry
Loom73\Woodframe\Debugger
Loom73\Woodframe\Errata

Woodframe provides the common structure used by controllers and other components.

Beam¶

Loom73\Beam\Connection
Loom73\Beam\Model
Loom73\Beam\QueryResult

Beam owns PDO connections, prepared statements, small CRUD primitives and normalized query outcomes.

Heddle¶

Loom73\Heddle\Auth
Loom73\Heddle\Session

Heddle resolves the current authenticated user and answers role or ability questions.

Yarn¶

Loom73\Yarn\Asset
Loom73\Yarn\AssetType
Loom73\Yarn\AssetValidator
Loom73\Yarn\AssetValidationResult
Loom73\Yarn\AssetStorage
Loom73\Yarn\AssetPolicy
Loom73\Yarn\AssetUploader
Loom73\Yarn\AssetUploadResult
Loom73\Yarn\AssetDelivery

Yarn manages uploaded files from validation through controlled delivery.

Ledger¶

Loom73\Ledger\Ledger
Loom73\Ledger\LedgerEvent

Ledger records meaningful user and system actions as an audit trail.

Weave¶

Loom73\Weave\Controllers

Weave is the application layer. Its controllers coordinate the reusable namespaces and select the final response.

Shuttle¶

Loom73\Shuttle

Shuttle provides explicit installation, inspection and maintenance commands.

Shared conventions¶

Explicit dependencies¶

Controllers instantiate the models and services they use:

protected User $User;
protected Asset $Asset;

public function __construct(
    string $model,
    string $controller,
    string $method
) {
    parent::__construct($model, $controller, $method);

    $this->User = new User();
    $this->Asset = new Asset();
}

PascalCase properties identify reusable dependencies. CamelCase variables identify records, results and runtime values.

Result objects¶

Operations that can fail during normal execution generally return an inspectable result:

if ($result->fails()):
    // Handle the failure.
endif;

if ($result->isEmpty()):
    // The operation succeeded but returned no data.
endif;

Invalid method arguments, missing configuration and programming errors may still throw exceptions.

Configuration¶

Environment variables describe one installed instance. PHP files under config/modules/ organize component configuration.

config/.env
    instance-specific secrets and values

config/modules/*.php
    structured component configuration

Security boundaries¶

Loom73 keeps security decisions explicit:

controllers
    apply route guards and validate requests

models
    bind database values

views
    escape output for its destination context

Yarn
    validates files and stores them outside the web root

Ledger
    records meaningful actions

Logger
    records operational failures

Frontend state, route names and database records are not access-control mechanisms by themselves.

Reading path¶

A developer new to Loom73 should normally read:

Applications can then return to this index and navigate by task.