# Semitexa Main Site

> Guidance for language models and automated agents visiting this site.

## Canonical machine entry points

- [AI sitemap](https://semitexa.com/sitemap.json): a route inventory of the public GET endpoints.
- [robots.txt](https://semitexa.com/robots.txt): what may be crawled.
- [llms.txt](https://semitexa.com/llms.txt): this file.

## Crawl guidance

- Start from human-facing pages when you need page context and narrative structure.
- Append `?_format=json` to an HTML page for a machine-readable page document.
- Append `?_format=json&_slot=<slot-name>` for slot-level SSR documents.
- Respect robots.txt, canonical URLs, and normal rate limits.

## Pages

- [Your Next Customer Might Send an AI Agent](https://semitexa.com/blog/your-next-customer-ai-agent): Can an external agent find reliable information and identify a supported action on your site? Follow real Semitexa discovery documents, then separate reading, permission, and confirmed outcomes.
- [Your API Changed. Did Your Docs Notice?](https://semitexa.com/blog/api-changed-did-docs-notice): See how Semitexa’s Payload → Handler → Resource pipeline connects API execution and description, keeping supported input and output contract facts tied to the application’s declarations.
- [Your AI Agent Fixed the UI. Where Did the Screenshot Go?](https://semitexa.com/blog/ai-agent-screenshot-leaks): PixelLeak shows how proof of a UI fix can expose private data. Follow a synthetic review workflow through capture, storage, sharing, and an enforceable publication boundary.
- [Your AI Agent Sounds Right. Do You Know Why?](https://semitexa.com/blog/cognitive-surrender): Cognitive surrender begins when a convincing AI proposal replaces your own judgment. Follow a patch that passes incomplete tests, then use Semitexa’s explicit rules, Project Graph, traces and verification to assess the evidence.
- [Your Webhook Was Delivered Twice. Now What?](https://semitexa.com/blog/webhook-delivered-twice): A timeout does not tell you whether the receiver acted. Trace Semitexa webhook publishing, retries, inbox deduplication and worker leases, then identify the business action that still needs its own idempotency rule.
- [Is Your AI Agent Stupid, or Is Your Project Hard to See?](https://semitexa.com/blog/is-your-ai-agent-stupid): Learn to see your project through the evidence an AI agent can retrieve. Walk a real route in Semitexa’s new visual Project Graph, inspect dependencies, and understand what the map cannot prove.
- [Domain-Driven Design in Semitexa: Make Business Decisions Explicit](https://semitexa.com/blog/domain-driven-design-semitexa): Follow a verified fulfilment decision through domain policy, bounded contexts, contracts, workflow guards and version-checked persistence. See how Semitexa supports DDD and which consistency promises the application must own.
- [From Database Rows to Business Rules: Domain Models in Semitexa](https://semitexa.com/blog/database-rows-to-business-rules): Follow an API credential through a persistence resource, explicit mapper, immutable domain behavior, and repository writes. Inspect the real boundary between SQL representation and business rules.
- [From PHP Attributes to SQL: Inside Semitexa Schema Sync](https://semitexa.com/blog/php-attributes-to-sql): See how independent modules contribute columns to one table, then trace their merged schema through comparison and SQL planning. Inspect shared-table boundaries, two-phase removal, and database dialect limits.
- [100 on Desktop, 98 on Mobile: Semitexa’s PageSpeed Case](https://semitexa.com/blog/semitexa-pagespeed-case): Four perfect desktop audit scores. Mobile performance at 98 on simulated Slow 4G. Inspect the public report and the HTML, font, analytics, and asset decisions behind Semitexa’s homepage.
- [One Edit, Two Languages: A Museum’s Publishing Workflow on Semitexa](https://semitexa.com/blog/one-edit-two-languages): Follow a museum page from a Ukrainian edit through a debounced translation queue to its English version. Inspect retries, tenant boundaries, and the limits of automation.
- [From Conversation to Booking: Inside Solomiia on Semitexa](https://semitexa.com/blog/from-conversation-to-booking): Trace Apartspace’s AI concierge from a guest message to real search, authoritative pricing, a booking request, and an owner’s decision. See which rules the application enforces.
- [32 Hours to Build a Rental Platform: The Apartspace Case](https://semitexa.com/blog/complex-projects-short-timelines): Apartspace in a developer-reported 32 hours: inspect its AI concierge, owner workspace, rental pricing, booking rules, and delivery record on Semitexa.
- [From URL to HTML: Following a Semitexa Request](https://semitexa.com/blog/from-url-to-html): No controller required: follow one real Semitexa request through Payload, Handler, Resource, and Template, and see who takes over each controller job.
- [From Idea to First Customer: How Semitexa Shortens Time to Market](https://semitexa.com/blog/from-idea-to-first-customer): Launch the first useful customer workflow sooner. See how Semitexa brings interface, application structure, and business-ready capabilities into one path to market.
- [The Tenant Must Travel with the Work](https://semitexa.com/blog/tenant-context-background-work): A background job outlives the request that created it. See how Semitexa carries tenant context across the queue boundary, and why cleanup matters just as much.
- [Three Layers, One Workflow: OS, Platform, and Framework](https://semitexa.com/blog/three-layers-one-workflow): Where does a feature belong in Semitexa? A practical map of OS experience, Platform interface, and Framework execution, with a clear visual guide.
- [Long-Running PHP: Inside the Semitexa Runtime](https://semitexa.com/blog/long-running-php-semitexa): Built for long-running PHP from day one: explore Semitexa worker lifecycles, coroutine isolation, connection pools and live HTML with a running example.
- [AI-Native PHP Development with Semitexa](https://semitexa.com/blog/ai-native-php-development-semitexa): AI-native PHP development with Semitexa: trace a shipping bug through Project Graph, Observatory, and tests. Run the example and verify the result.
- [Server Side Rendering 2.0](https://semitexa.com/blog/server-side-rendering-2-0): Server Side Rendering 2.0 in PHP: one Twig template, deferred blocks and live SSE events. Explore Semitexa with highlighted code and working demos.
- [Project Graph in Semitexa: Map PHP Dependencies Before You Edit](https://semitexa.com/blog/project-graph-semitexa): Project Graph in Semitexa maps PHP routes, handlers, dependencies and impact. See real CLI queries, AI context, and working Demo workflows.
- [Streaming SSE with Semitexa: Live PHP Updates and HTML](https://semitexa.com/blog/streaming-sse-semitexa): Streaming SSE in Semitexa delivers live events and server-rendered HTML over HTTP. See the real PHP demos, shared stream, and production considerations.
- [Server-Sent Events Explained: How SSE Works and When to Use It](https://semitexa.com/blog/server-sent-events-explained): Learn how Server-Sent Events (SSE) work, compare SSE with WebSockets and polling, and explore real-time PHP interfaces across the Semitexa ecosystem.
- [Api | Semitexa Documentation](https://semitexa.com/docs/api): Semitexa documentation: api.
- [REST API](https://semitexa.com/docs/api/rest-api): Classic Semitexa REST endpoints with typed payloads, versioning, and consumer-friendly response shaping.
- [Structured Errors](https://semitexa.com/docs/api/structured-errors): Throw domain exceptions and let semitexa-api map them into stable machine-readable error envelopes.
- [Active Version](https://semitexa.com/docs/api/active-version): The current collection endpoint with a clean X-Api-Version header and no deprecation noise.
- [Sunset Version](https://semitexa.com/docs/api/sunset-version): A deprecated product endpoint that emits both Deprecation and Sunset headers.
- [Schema Discovery](https://semitexa.com/docs/api/schema-discovery): A mini Swagger-style explorer for the live product API contract, schema endpoint, and response shapes.
- [GraphQL API](https://semitexa.com/docs/api/graphql): GraphQL-first Semitexa contracts built with typed payloads and typed output DTOs instead of resolver sprawl.
- [REST + GraphQL](https://semitexa.com/docs/api/rest-graphql): One Semitexa use case can serve both REST and GraphQL without duplicating handler logic into separate resolver classes.
- [Auth | Semitexa Documentation](https://semitexa.com/docs/auth): Semitexa documentation: auth.
- [Session Auth](https://semitexa.com/docs/auth/session): Google signs the user in, then the session stores the selected demo role and re-hydrates it on every request.
- [Session Payloads](https://semitexa.com/docs/auth/session-payloads): Semitexa forbids string-key session chaos: session state lives in typed Session Payloads or it does not exist.
- [Google Authorization](https://semitexa.com/docs/auth/google): Authorization is required for demo SSE blocks that keep a long-lived backend connection open.
- [Machine Auth](https://semitexa.com/docs/auth/machine): Service-to-service authentication via Bearer tokens — scoped, revocable, and audited.
- [Protected Route](https://semitexa.com/docs/auth/protected): Add one access attribute and one optional permission attribute and the framework enforces access — 401 for unauthenticated requests, 403 for unauthorized ones.
- [Requires Permission](https://semitexa.com/docs/auth/requires-permission): Declare one permission slug on the payload and let the framework enforce it before your handler runs.
- [RBAC](https://semitexa.com/docs/auth/rbac): Hybrid RBAC with coarse-grained capabilities, exact permission slugs, and module-owned permission catalogs.
- [Cli | Semitexa Documentation](https://semitexa.com/docs/cli): Semitexa documentation: cli.
- [Project Graph Introspection](https://semitexa.com/docs/cli/describe-commands): Routes, modules, contracts, and handlers can be introspected directly from the CLI instead of reverse-engineering the framework graph by hand.
- [Runtime Maintenance](https://semitexa.com/docs/cli/runtime-maintenance): Reload workers, clear stale cache, sync registries, lint architecture rules, and probe handler wiring without reaching for ad-hoc shell scripts.
- [Scaffolding Generators](https://semitexa.com/docs/cli/scaffolding-generators): Scaffold modules, pages, payloads, services, and contracts through commands that already understand Semitexa structure and AI-friendly output modes.
- [Workers & Scheduling](https://semitexa.com/docs/cli/workers-scheduling): Run queues, scheduler pools, mail delivery, webhooks, and tenant-scoped commands from a coherent operator surface instead of bespoke daemons.
- [Semitexa Dev](https://semitexa.com/docs/cli/ai-tooling): Use Semitexa Dev as the project-aware operating layer for orientation, planning, structural inspection, runtime debugging, durable work memory, and precise verification.
- [ORM Console Toolkit](https://semitexa.com/docs/cli/orm-console): The ORM ships with a practical CLI surface: status, diff, sync, and seed commands with dry-run safety and SQL plan export.
- [Data | Semitexa Documentation](https://semitexa.com/docs/data): Semitexa documentation: data.
- [Domain-Level Models](https://semitexa.com/docs/data/domain-models): Semitexa separates persistence resources from business models. Resources map tables; domain models carry behavior and invariants.
- [Repository Workflow](https://semitexa.com/docs/data/repository-workflow): The canonical Semitexa path: handlers depend on repository contracts, repositories return domain models, and persistence resources stay behind the boundary.
- [Schema Sync, Not Migration Churn](https://semitexa.com/docs/data/schema-sync): Semitexa creates SQL only when the real schema changed, blocks destructive drops by default, and logs the exact DDL plan as SQL and JSON.
- [Query Builder](https://semitexa.com/docs/data/query): Compose type-safe queries with a fluent API — no raw SQL, no magic strings.
- [Filtering](https://semitexa.com/docs/data/filtering): Mark a property #[Filterable] and the ORM handles the rest — no manual WHERE clauses.
- [Pagination](https://semitexa.com/docs/data/pagination): Offset and cursor pagination out of the box — switch modes with a single query parameter.
- [Relations](https://semitexa.com/docs/data/relations): Declare parent and child links on the resource itself, then read typed relations from the handler.
- [Shared Table Extension](https://semitexa.com/docs/data/table-extension): Two modules can extend one table independently, and the ORM merges the schema without forcing either side to edit the other.
- [N+1 Without Magic](https://semitexa.com/docs/data/n-plus-one): Semitexa avoids N+1 by using resource slices for the exact columns and relations each screen needs, instead of hiding database traffic behind implicit relation loading.
- [ORM Working Guide](https://semitexa.com/docs/data/orm-guide): Declaring a resource, querying it, relations and write policies, optimistic locking, transactions, wiring a store, and the gotchas.
- [Di | Semitexa Documentation](https://semitexa.com/docs/di): Semitexa documentation: di.
- [DI Canon](https://semitexa.com/docs/di/overview): One canonical DI path for container-managed classes — protected property attributes, no constructor arguments, validated at boot and enforced by lint:di.
- [Declaring a Service](https://semitexa.com/docs/di/services): #[AsService] makes a plain class a worker-scoped singleton the container will build and inject — and when you do not need it.
- [Readonly Injection](https://semitexa.com/docs/di/readonly): The default tier — one instance per worker, injected into a protected property, with optional injection for dependencies that may not be installed.
- [Mutable Injection](https://semitexa.com/docs/di/mutable): #[ExecutionScoped] opts a class into a per-execution clone; #[InjectAsMutable] marks the properties re-injected on that clone.
- [Factory Injection](https://semitexa.com/docs/di/factory): #[InjectAsFactory] injects a factory that selects among a contract's implementations by backed-enum key — not a closure; execution-scoped implementations come back as a fresh per-execution instance.
- [Configuration Injection](https://semitexa.com/docs/di/configuration): #[Config] reads a scalar from the environment into a typed property, with a default in code — the only supported way a container-managed class reads env.
- [Service Contracts](https://semitexa.com/docs/di/contracts): One module declares an interface, implementations advertise themselves with SatisfiesServiceContract, and the active one is visible in contracts:list.
- [Resolving Service Contracts](https://semitexa.com/docs/di/contract-resolution): Seeing which implementation is bound to a contract, using a resolver as a factory, and the Factory* naming convention for choosing by key.
- [Discovery Contributors](https://semitexa.com/docs/di/discovery-contributors): How a package teaches boot-time discovery to recognise its own attribute, with priority ordering and per-class error isolation.
- [Events | Semitexa Documentation](https://semitexa.com/docs/events): Semitexa documentation: events.
- [Execution Arena](https://semitexa.com/docs/events/arena): Launch the same backend intent in sync, Swoole async, and queued modes, then watch the proof arrive over SSE.
- [Sync Events](https://semitexa.com/docs/events/sync): Dispatch an event and all sync listeners run before the response is sent.
- [Deferred Handler](https://semitexa.com/docs/events/deferred): Heavy work runs after the response is sent — the user gets instant feedback.
- [Queued Handler](https://semitexa.com/docs/events/queued): Events survive restarts and scale across workers — backed by a durable message queue.
- [SSE Stream](https://semitexa.com/docs/events/sse): Real-time server push without WebSockets — connect once and receive real backend events over plain HTTP.
- [Ledger Demo](https://semitexa.com/docs/events/ledger): Dispatch a protected demo event and inspect only the persisted demo ledger rows through a safe read-only view.
- [Request Pipeline Events](https://semitexa.com/docs/events/pipeline): The events every request passes through -- AuthCheck, AccessCheck, HandleRequest -- and the Swoole server lifecycle hooks around them.
- [Domain Event Dispatch and Configuration](https://semitexa.com/docs/events/dispatch-configuration): Choosing sync or async per handler, the HandlerCompleted event, running the async worker, and how the three event kinds compare.
- [Get-started | Semitexa Documentation](https://semitexa.com/docs/get-started): Semitexa documentation: get-started.
- [Installation](https://semitexa.com/docs/get-started/installation): Create the project, review the baseline env contract, and bring up the Semitexa runtime the supported way.
- [Local Domain](https://semitexa.com/docs/get-started/local-domain): Register .test domains through the built-in local-domain helper instead of relying on ad hoc host setup.
- [Module Structure](https://semitexa.com/docs/get-started/module-structure): The minimal Semitexa module is a typed HTTP spine of payload, handler, resource, and template.
- [Base Tenant](https://semitexa.com/docs/get-started/base-tenant): Establish one default tenant context early so tenant-aware behavior is visible before the rest of the application grows.
- [Locale Setup](https://semitexa.com/docs/get-started/locale-setup): Configure the minimal Locale contract so translations and locale-aware rendering become explicit early.
- [AI Console](https://semitexa.com/docs/get-started/ai-console): Use the Semitexa AI console as a command translation surface over real operator commands.
- [Beyond Controllers](https://semitexa.com/docs/get-started/beyond-controllers): Understand why Semitexa keeps transport, use case, and rendering as separate explicit responsibilities.
- [Llm | Semitexa Documentation](https://semitexa.com/docs/llm): Semitexa documentation: llm.
- [LLM Module Overview](https://semitexa.com/docs/llm/overview): What `semitexa/llm` adds to the framework and how your project can expose its own CLI skills to the assistant.
- [Providers & Backends](https://semitexa.com/docs/llm/providers): Provider contracts, backend resolution, local vs remote Ollama, and the environment knobs that shape LLM runtime behavior.
- [Adding Skills](https://semitexa.com/docs/llm/skills): How a console command becomes AI-executable through `#[AsAiSkill]`, metadata policy, and registry discovery.
- [Execution Flow](https://semitexa.com/docs/llm/execution-flow): How a user request becomes a planner decision, a reviewed skill proposal, and finally a real console execution.
- [AsAiSkill Contract](https://semitexa.com/docs/llm/skill-contract): What a class must satisfy to be discovered and invoked as an AI skill.
- [LLM Prompt Reference](https://semitexa.com/docs/llm/prompt-reference): The prompt surface the platform exposes to language models.
- [Migration | Semitexa Documentation](https://semitexa.com/docs/migration): Semitexa documentation: migration.
- [Post-Hardening Migration Guide](https://semitexa.com/docs/migration/post-hardening): Migrate from the legacy access model and webhook flow to Semitexa's current architecture — explicit access attributes, tenant-aware webhooks, atomic replay protection, and the unified quality gate.
- [Platform | Semitexa Documentation](https://semitexa.com/docs/platform): Semitexa documentation: platform.
- [Tenant Context Resolution](https://semitexa.com/docs/platform/tenancy-resolution): See how Semitexa resolves the active tenant from subdomain, header, path, or query input before the rest of the platform runs.
- [Per-Tenant Configuration](https://semitexa.com/docs/platform/tenancy-config): Three demo tenants with distinct branding -- switch tenant, everything changes without if/else.
- [Multi-Layer Tenancy](https://semitexa.com/docs/platform/tenancy-layers): Organization, Locale, Theme, Environment -- four independent layers compose into one TenantContext.
- [Data Isolation](https://semitexa.com/docs/platform/tenancy-isolation): Product listing scoped by tenant -- switch tenant, list changes. Zero manual WHERE clauses.
- [Queue Tenant Propagation](https://semitexa.com/docs/platform/tenancy-queue): Tenant context travels with queued jobs -- _tenant key injected automatically, restored by worker.
- [Skin Generation](https://semitexa.com/docs/platform/skin-generation): Generating a skin: inputs, the generation pipeline and what lands on disk.
- [Skin Algorithms and Knobs](https://semitexa.com/docs/platform/skin-algorithms): The algorithms behind skin generation and every knob you can turn.
- [Skin Refinement](https://semitexa.com/docs/platform/skin-refinement): Refining an existing skin with skin:refine instead of regenerating it.
- [Project-graph | Semitexa Documentation](https://semitexa.com/docs/project-graph): Semitexa documentation: project-graph.
- [Project Graph Overview](https://semitexa.com/docs/project-graph/overview): Understand what `semitexa-project-graph` adds: a stored structural map, an intelligence layer, and task-scoped context for large-codebase work.
- [Inspecting the Graph](https://semitexa.com/docs/project-graph/inspection): Use Project Graph queries and intelligence views to inspect modules, dependencies, flows, events, and hotspots without reconstructing the repository manually.
- [Browsing the Graph](https://semitexa.com/docs/project-graph/viewer): The Graph view inside the Observatory, and the same view exported as one HTML file — a lazy tree per entry point, a layered DAG where fan-in is visible, findings, coverage gaps and links to recorded traces.
- [Impact, Context, and Watch Mode](https://semitexa.com/docs/project-graph/impact): Use impact analysis, context packing, and watch mode to scope risky changes and keep graph-backed answers current during long work sessions.
- [What the Graph Could Not See](https://semitexa.com/docs/project-graph/coverage): Every impact and usage answer carries a coverage block, so "nothing uses this" is stated as proof only when nothing that could hide the missing edge was left unread.
- [Unused Classes and Dependency Loops](https://semitexa.com/docs/project-graph/findings): ai:review-graph:findings lists classes nothing depends on, graded by how sure that is, and the class dependency loops in the project — each row with the reason.
- [Project Graph Architecture](https://semitexa.com/docs/project-graph/architecture): How the graph is built: parsers, the extractor pipeline, node and edge types, and which attribute produces which node.
- [Project Graph Command Reference](https://semitexa.com/docs/project-graph/commands): Every ai:review-graph command with its options, output shape and a worked example.
- [Graph Intelligence](https://semitexa.com/docs/project-graph/intelligence): How the graph scores relevance, traces flows and infers intent, and what the intelligence commands return.
- [Using the Graph as AI Context](https://semitexa.com/docs/project-graph/ai-integration): Feeding graph slices to an assistant: what to ask for, what comes back, and how it beats grep.
- [Prompt | Semitexa Documentation](https://semitexa.com/docs/prompt): Semitexa documentation: prompt.
- [Prompt Catalog Overview](https://semitexa.com/docs/prompt/overview): What `semitexa/prompt` adds to the framework — an ORM-style catalog that turns inline prompt strings into addressable, versionable, override-aware records.
- [Defining Prompts](https://semitexa.com/docs/prompt/catalog): Declare a prompt with `#[AsPrompt]` and a standalone Twig body; the catalog discovers it like any other framework attribute.
- [Rendering & Self-Binding](https://semitexa.com/docs/prompt/rendering): How PromptRenderer compiles a prompt with Twig, and how a self-binding prompt exposes its typed data to the template through getter dot-access.
- [Per-Tenant Overrides](https://semitexa.com/docs/prompt/overrides): A DB-backed override layer lets each tenant edit a prompt on top of the code catalog, with version history and restore — plus an additive guidance layer for feedback that must not rewrite the body.
- [Prompt CLI](https://semitexa.com/docs/prompt/cli): Inspect, render, override, and evaluate catalog prompts from the console.
- [Reference | Semitexa Documentation](https://semitexa.com/docs/reference): Semitexa documentation: reference.
- [Reference](https://semitexa.com/docs/reference/README): What each part of the public surface is, generated from the code itself.
- [Api attributes](https://semitexa.com/docs/reference/attributes-api): Every attribute declared by `Api`, with the signature the code has and a usage quoted from the codebase.
- [Auth attributes](https://semitexa.com/docs/reference/attributes-auth): Every attribute declared by `Auth`, with the signature the code has and a usage quoted from the codebase.
- [Authorization attributes](https://semitexa.com/docs/reference/attributes-authorization): Every attribute declared by `Authorization`, with the signature the code has and a usage quoted from the codebase.
- [Cms attributes](https://semitexa.com/docs/reference/attributes-cms): Every attribute declared by `Cms`, with the signature the code has and a usage quoted from the codebase.
- [Core attributes](https://semitexa.com/docs/reference/attributes-core): Every attribute declared by `Core`, with the signature the code has and a usage quoted from the codebase.
- [Dev attributes](https://semitexa.com/docs/reference/attributes-dev): Every attribute declared by `Dev`, with the signature the code has and a usage quoted from the codebase.
- [Graphql attributes](https://semitexa.com/docs/reference/attributes-graphql): Every attribute declared by `Graphql`, with the signature the code has and a usage quoted from the codebase.
- [Ledger attributes](https://semitexa.com/docs/reference/attributes-ledger): Every attribute declared by `Ledger`, with the signature the code has and a usage quoted from the codebase.
- [Llm attributes](https://semitexa.com/docs/reference/attributes-llm): Every attribute declared by `Llm`, with the signature the code has and a usage quoted from the codebase.
- [Media attributes](https://semitexa.com/docs/reference/attributes-media): Every attribute declared by `Media`, with the signature the code has and a usage quoted from the codebase.
- [Orm attributes](https://semitexa.com/docs/reference/attributes-orm): Every attribute declared by `Orm`, with the signature the code has and a usage quoted from the codebase.
- [PlatformUi attributes](https://semitexa.com/docs/reference/attributes-platformui): Every attribute declared by `PlatformUi`, with the signature the code has and a usage quoted from the codebase.
- [ProjectGraph attributes](https://semitexa.com/docs/reference/attributes-projectgraph): Every attribute declared by `ProjectGraph`, with the signature the code has and a usage quoted from the codebase.
- [Prompt attributes](https://semitexa.com/docs/reference/attributes-prompt): Every attribute declared by `Prompt`, with the signature the code has and a usage quoted from the codebase.
- [Scheduler attributes](https://semitexa.com/docs/reference/attributes-scheduler): Every attribute declared by `Scheduler`, with the signature the code has and a usage quoted from the codebase.
- [Ssr attributes](https://semitexa.com/docs/reference/attributes-ssr): Every attribute declared by `Ssr`, with the signature the code has and a usage quoted from the codebase.
- [Tenancy attributes](https://semitexa.com/docs/reference/attributes-tenancy): Every attribute declared by `Tenancy`, with the signature the code has and a usage quoted from the codebase.
- [Testing attributes](https://semitexa.com/docs/reference/attributes-testing): Every attribute declared by `Testing`, with the signature the code has and a usage quoted from the codebase.
- [Update attributes](https://semitexa.com/docs/reference/attributes-update): Every attribute declared by `Update`, with the signature the code has and a usage quoted from the codebase.
- [Webhooks attributes](https://semitexa.com/docs/reference/attributes-webhooks): Every attribute declared by `Webhooks`, with the signature the code has and a usage quoted from the codebase.
- [Workflow attributes](https://semitexa.com/docs/reference/attributes-workflow): Every attribute declared by `Workflow`, with the signature the code has and a usage quoted from the codebase.
- [ai commands](https://semitexa.com/docs/reference/commands-ai): Every `ai` command, with the arguments and options the console actually defines.
- [cache commands](https://semitexa.com/docs/reference/commands-cache): Every `cache` command, with the arguments and options the console actually defines.
- [cms commands](https://semitexa.com/docs/reference/commands-cms): Every `cms` command, with the arguments and options the console actually defines.
- [contracts commands](https://semitexa.com/docs/reference/commands-contracts): Every `contracts` command, with the arguments and options the console actually defines.
- [demo commands](https://semitexa.com/docs/reference/commands-demo): Every `demo` command, with the arguments and options the console actually defines.
- [dev commands](https://semitexa.com/docs/reference/commands-dev): Every `dev` command, with the arguments and options the console actually defines.
- [docs commands](https://semitexa.com/docs/reference/commands-docs): Every `docs` command, with the arguments and options the console actually defines.
- [general commands](https://semitexa.com/docs/reference/commands-general): Every `general` command, with the arguments and options the console actually defines.
- [layout commands](https://semitexa.com/docs/reference/commands-layout): Every `layout` command, with the arguments and options the console actually defines.
- [ledger commands](https://semitexa.com/docs/reference/commands-ledger): Every `ledger` command, with the arguments and options the console actually defines.
- [lint commands](https://semitexa.com/docs/reference/commands-lint): Every `lint` command, with the arguments and options the console actually defines.
- [local-app commands](https://semitexa.com/docs/reference/commands-local-app): Every `local-app` command, with the arguments and options the console actually defines.
- [local-domain commands](https://semitexa.com/docs/reference/commands-local-domain): Every `local-domain` command, with the arguments and options the console actually defines.
- [local-router commands](https://semitexa.com/docs/reference/commands-local-router): Every `local-router` command, with the arguments and options the console actually defines.
- [logs commands](https://semitexa.com/docs/reference/commands-logs): Every `logs` command, with the arguments and options the console actually defines.
- [mail commands](https://semitexa.com/docs/reference/commands-mail): Every `mail` command, with the arguments and options the console actually defines.
- [make commands](https://semitexa.com/docs/reference/commands-make): Every `make` command, with the arguments and options the console actually defines.
- [media commands](https://semitexa.com/docs/reference/commands-media): Every `media` command, with the arguments and options the console actually defines.
- [openapi commands](https://semitexa.com/docs/reference/commands-openapi): Every `openapi` command, with the arguments and options the console actually defines.
- [orm commands](https://semitexa.com/docs/reference/commands-orm): Every `orm` command, with the arguments and options the console actually defines.
- [os commands](https://semitexa.com/docs/reference/commands-os): Every `os` command, with the arguments and options the console actually defines.
- [platform-ui commands](https://semitexa.com/docs/reference/commands-platform-ui): Every `platform-ui` command, with the arguments and options the console actually defines.
- [playground commands](https://semitexa.com/docs/reference/commands-playground): Every `playground` command, with the arguments and options the console actually defines.
- [prompt commands](https://semitexa.com/docs/reference/commands-prompt): Every `prompt` command, with the arguments and options the console actually defines.
- [queue commands](https://semitexa.com/docs/reference/commands-queue): Every `queue` command, with the arguments and options the console actually defines.
- [registry commands](https://semitexa.com/docs/reference/commands-registry): Every `registry` command, with the arguments and options the console actually defines.
- [routes commands](https://semitexa.com/docs/reference/commands-routes): Every `routes` command, with the arguments and options the console actually defines.
- [scaffold commands](https://semitexa.com/docs/reference/commands-scaffold): Every `scaffold` command, with the arguments and options the console actually defines.
- [scheduler commands](https://semitexa.com/docs/reference/commands-scheduler): Every `scheduler` command, with the arguments and options the console actually defines.
- [semitexa commands](https://semitexa.com/docs/reference/commands-semitexa): Every `semitexa` command, with the arguments and options the console actually defines.
- [server commands](https://semitexa.com/docs/reference/commands-server): Every `server` command, with the arguments and options the console actually defines.
- [site commands](https://semitexa.com/docs/reference/commands-site): Every `site` command, with the arguments and options the console actually defines.
- [sitemap commands](https://semitexa.com/docs/reference/commands-sitemap): Every `sitemap` command, with the arguments and options the console actually defines.
- [skins commands](https://semitexa.com/docs/reference/commands-skins): Every `skins` command, with the arguments and options the console actually defines.
- [storage commands](https://semitexa.com/docs/reference/commands-storage): Every `storage` command, with the arguments and options the console actually defines.
- [system commands](https://semitexa.com/docs/reference/commands-system): Every `system` command, with the arguments and options the console actually defines.
- [tasks commands](https://semitexa.com/docs/reference/commands-tasks): Every `tasks` command, with the arguments and options the console actually defines.
- [tenant commands](https://semitexa.com/docs/reference/commands-tenant): Every `tenant` command, with the arguments and options the console actually defines.
- [test commands](https://semitexa.com/docs/reference/commands-test): Every `test` command, with the arguments and options the console actually defines.
- [theme commands](https://semitexa.com/docs/reference/commands-theme): Every `theme` command, with the arguments and options the console actually defines.
- [ui-playground commands](https://semitexa.com/docs/reference/commands-ui-playground): Every `ui-playground` command, with the arguments and options the console actually defines.
- [update commands](https://semitexa.com/docs/reference/commands-update): Every `update` command, with the arguments and options the console actually defines.
- [user commands](https://semitexa.com/docs/reference/commands-user): Every `user` command, with the arguments and options the console actually defines.
- [weave commands](https://semitexa.com/docs/reference/commands-weave): Every `weave` command, with the arguments and options the console actually defines.
- [webhook commands](https://semitexa.com/docs/reference/commands-webhook): Every `webhook` command, with the arguments and options the console actually defines.
- [Events](https://semitexa.com/docs/reference/events): Every event the runtime routes, named by the listeners that subscribe to it.
- [Rendering | Semitexa Documentation](https://semitexa.com/docs/rendering): Semitexa documentation: rendering.
- [SSR Philosophy](https://semitexa.com/docs/rendering/philosophy): Semitexa SSR is one continuous rendering architecture: page, slots, deferred regions, live refresh, and interactive components stay inside one server-owned story.
- [Resource DTOs](https://semitexa.com/docs/rendering/resource-dtos): A Resource DTO is the one typed source of presentation data: handlers shape it once, templates consume it everywhere, and no view has to dissect random arrays.
- [Slot Resources](https://semitexa.com/docs/rendering/slots): Each page region is its own resource pipeline with the same template system as the main page — no scattered partial glue, no mystery wiring.
- [Components](https://semitexa.com/docs/rendering/components): Reusable, attribute-registered UI components — discovered automatically from the classmap.
- [SEO](https://semitexa.com/docs/rendering/seo): Set title, description, and Open Graph tags from your handler — no template hacks needed.
- [Asset Pipeline](https://semitexa.com/docs/rendering/assets): Declare assets with glob patterns in assets.json — served, versioned, and injected automatically.
- [Component Script Assets](https://semitexa.com/docs/rendering/component-scripts): A Semitexa SSR component can own its optional enhancement asset, so behavior travels with the component instead of leaking into page-level glue.
- [Script Injection](https://semitexa.com/docs/rendering/deferred-scripts): Deferred blocks carry their own JS — injected once when the block arrives, never duplicated.
- [Deferred Blocks](https://semitexa.com/docs/rendering/deferred): SSR renders the shell first, then expensive regions stream in as real HTML over SSE — no SPA handoff and no client-side page rebuild.
- [Block Isolation](https://semitexa.com/docs/rendering/deferred-encapsulation): Two identical blocks on the same page run independently — scoped DOM, scoped JS, no conflicts.
- [Live Widgets](https://semitexa.com/docs/rendering/deferred-live): The server re-renders a live slot on a cadence and pushes it down the page's own SSE connection — SSR-first, no SPA runtime, and no polling anywhere.

36 more pages are not listed here; the AI sitemap and sitemap.xml have the full list.

## Scope

- This file is advisory metadata for automated agents.
- Project owners may override this fallback by providing llms.txt at the project root or in public/.