semitexa.com

mx

mx.imena.ua

ns

nsd1.srv53.net

nsa3.srv53.com

nsa3.srv53.org

nsc2.srv53.net

nsc1.srv53.org

nsb4.srv53.com

nsb3.srv53.org

nsb4.srv53.net

caa

txt

google-site-verification=4ovhYt0urIY8RQO7bbfpAaXpGDn1KERm1hGmDj1KArY

dmarc

User-agent: *
Allow: /

# Semitexa crawler hints
# LLMS: https://semitexa.com/llms.txt
# AI sitemap: https://semitexa.com/sitemap.json
# HTML pages may expose a machine-readable alternate JSON document.
# Try the same page with ?_format=json when you want page/meta/slot IRIs.
# Slot documents are addressable with ?_format=json&_slot=<name>.
# Deferred regions stay part of the same SSR page model.

Sitemap: https://semitexa.com/sitemap.xml

# 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

- [SSE-Driven Data Grid in PHP: The Table Is a Subscription](https://semitexa.com/blog/live-data-grid): A PHP data grid driven by Server-Sent Events: the server owns the view, re-runs it on change and sends only the rows that moved. Watch the wire live.
- [Your Next Customer Might Send an AI Agent](https://semitexa.com/blog/your-next-customer-ai-agent): Can an external AI agent find reliable facts and a supported action on your site? Follow real Semitexa discovery documents step by step.
- [Your API Changed. Did Your Docs Notice?](https://semitexa.com/blog/api-changed-did-docs-notice): Follow Semitexa's Payload, Handler and Resource pipeline to see how API docs and contract facts stay tied to the code that actually runs.
- [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 review through capture, storage, sharing and a publication boundary.
- [Your AI Agent Sounds Right. Do You Know Why?](https://semitexa.com/blog/cognitive-surrender): Cognitive surrender starts when a convincing AI patch replaces your judgment. Check it with Semitexa rules, Project Graph, traces and verification.
- [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 retries, inbox deduplication and leases, and what still needs idempotency.
- [Is Your AI Agent Stupid or Your Project Hard to See?](https://semitexa.com/blog/is-your-ai-agent-stupid): See your project through the evidence an AI agent can retrieve. Walk a real route in Semitexa's visual Project Graph and learn what the map cannot prove.
- [Domain-Driven Design in PHP with Semitexa](https://semitexa.com/blog/domain-driven-design-semitexa): Follow a fulfilment decision through domain policy, bounded contexts, contracts and version-checked persistence, and see how Semitexa supports DDD in PHP.
- [Domain Models in PHP: From Rows to Business Rules](https://semitexa.com/blog/database-rows-to-business-rules): Follow an API credential through a persistence resource, a mapper, immutable domain behavior and repository writes: where SQL ends and business rules begin.
- [PHP Attributes to SQL: Inside Semitexa Schema Sync](https://semitexa.com/blog/php-attributes-to-sql): See how independent modules add columns to one table and how Semitexa turns PHP attributes into a merged schema, a comparison and a safe SQL plan.
- [PageSpeed 100 Desktop, 98 Mobile: Semitexa Case Study](https://semitexa.com/blog/semitexa-pagespeed-case): Four perfect desktop scores and 98 on mobile over Slow 4G. Inspect the report and the HTML, font, analytics and asset choices behind Semitexa's homepage.
- [One Edit, Two Languages: A Museum Publishing Workflow](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, with retries, tenant boundaries and limits.
- [From Conversation to Booking: an AI Concierge in PHP](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 the owner's decision on Semitexa.
- [32 Hours to Build a Rental Platform: 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: Faster Time to Market](https://semitexa.com/blog/from-idea-to-first-customer): Launch the first useful customer workflow sooner: see how Semitexa brings the interface, application structure and business capabilities into one path.
- [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, 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: 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): What is SSE? Learn how Server-Sent Events work, what SSE streaming is, how it compares with WebSockets and polling, and when to use it.
- [API | Semitexa PHP Docs](https://semitexa.com/docs/api): Build REST and GraphQL APIs in PHP with Semitexa: versioned endpoints, Deprecation and Sunset headers, structured errors and schema discovery.
- [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 PHP Docs](https://semitexa.com/docs/auth): Authentication and authorization in Semitexa PHP: session auth, Google sign-in, machine tokens, RBAC and permission checks on protected routes.
- [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.
- [CSRF](https://semitexa.com/docs/auth/csrf): Every unsafe request from a signed-in browser must carry the session's CSRF token; a plain HTML form gets it with csrf_field(), JavaScript with the X-CSRF-Token header.
- [Google Authorization](https://semitexa.com/docs/auth/google): Sign in with Google in Semitexa PHP: the OAuth flow, CSRF state, a typed session identity, and why long-lived SSE streams require an authenticated user.
- [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 PHP Docs](https://semitexa.com/docs/cli): The Semitexa command line: scaffolding generators, the ORM console, workers and scheduling, project graph introspection and runtime maintenance.
- [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): Semitexa Dev is the project-aware 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 & ORM | Semitexa PHP Docs](https://semitexa.com/docs/data): Data in Semitexa PHP: a type-safe query builder, relations without N+1, filtering, pagination, repositories and schema sync instead of migrations.
- [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 with resource slices that load the exact columns and relations each screen needs, instead of hiding queries behind implicit 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.
- [Dependency Injection | Semitexa PHP Docs](https://semitexa.com/docs/di): Dependency injection in Semitexa PHP: declaring services, contracts, readonly and mutable injection, factories and configuration injection.
- [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 that the container builds and injects, and this page shows 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 picks a contract implementation by backed-enum key. Execution-scoped implementations come back fresh each time.
- [Configuration Injection](https://semitexa.com/docs/di/configuration): #[Config] reads a scalar from the environment into a typed property, with a default in code. It is the only supported way a service 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 PHP Docs](https://semitexa.com/docs/events): Events in Semitexa PHP: sync, deferred and queued handlers, domain event dispatch, request pipeline events and Server-Sent Events (SSE) streams.
- [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, so 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.
- [Server-Sent Events (SSE)](https://semitexa.com/docs/events/sse): Live Server-Sent Events demo: one long-lived HTTP connection streams real backend events to the browser via EventSource. No WebSockets, plain PHP.
- [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 PHP Docs](https://semitexa.com/docs/get-started): Get started with Semitexa, the PHP framework built for AI agents: installation, module structure, local domain, locale setup and the AI console.
- [Installation](https://semitexa.com/docs/get-started/installation): Create the project with the one-line installer, start it, create the database tables, and know what the installer changes outside the project.
- [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 PHP Docs](https://semitexa.com/docs/llm): The Semitexa LLM module: providers and backends, AI skills with the AsAiSkill contract, the execution flow and the prompt reference for PHP apps.
- [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 Semitexa platform exposes to language models: every prompt, its inputs and where it is used in a PHP application.
- [Migration | Semitexa PHP Docs](https://semitexa.com/docs/migration): Migration guides for Semitex