Reference
Pharos extension points are declared in app-owned files and executed by framework-owned runtime behavior. The tables below show the supported seams and bounded hooks that are intended for app authors.
| Seam: Behavior | File path: |
|---|---|
| app-local config: Precedence resolution over shared config. | app.conf |
| app manifest: App loading, profile selection, and artifact wiring. | pharos.app.yml |
| page surfaces: HTML rendering and response shaping. | templates/*.page.ymltemplates/*.body.html |
| routes: Route matching and dispatch. | data/contracts/routes.yml |
| forms: Input extraction and validation. | data/contracts/forms.ymldata/contracts/form-fields.yml |
| actions: Validation, policy gating, mutation execution, and response shaping. | data/contracts/actions.yml |
| workflows: Transition execution and effect recording. | data/contracts/workflows.yml |
| generated surfaces: Generated admin and generated API behavior. | data/contracts/generated-surfaces.yml |
| UI-library surfaces: Framework-owned UI example rendering. | data/contracts/ui-elements.ymldata/contracts/ui-examples.yml |
| integrations: Webhook, notification, email, local audit, and local file-record adapter behavior. | data/contracts/integrations.yml |
Database persistence
Apps declare logical entities and migrations, then use the configured adapter through the database interface. This contract covers reads, guarded mutations, schema changes, security state, and operator snapshots.