# Praxis Platform > Contexto curto e confiável para LLMs sobre a plataforma Praxis. > Para detalhes, contratos, caveats e troubleshooting, consulte `/llms-full.txt`. ## O Que É Praxis One corporate API. Many governed experiences. Less frontend to maintain. Praxis é uma plataforma enterprise de decisões semânticas governadas e materialização runtime para aplicações internas. Ela entra no stack Java/Spring e Angular existente: o host continua dono de domínio, dados, regras executáveis, segurança, tema, rotas, observabilidade e deploy. A IA não gera JSON, patches ou código solto como unidade primária. O fluxo canônico é: `grounding governado -> intenção semântica -> decisão canônica -> simulação/revisão -> aprovação -> publicação -> materializações -> observação/explicação` Patches continuam válidos somente como materialização local quando a intenção semanticamente resolvida for uma alteração de componente. ## Entradas Principais - [Short context](https://praxisui.dev/llms.txt) - [Expanded context](https://praxisui.dev/llms-full.txt) - [Machine-readable capability index](https://praxisui.dev/llm-index.json) - [Assistant answer benchmark](https://praxisui.dev/llm-benchmark.json) - [Human source-of-truth guide](https://praxisui.dev/llm-source-of-truth) - [Published operational evidence guide](https://praxisui.dev/llm-operational-evidence) - [Markdown source-of-truth guide](https://praxisui.dev/llm-source-of-truth.md) - [Markdown operational evidence guide](https://praxisui.dev/llm-operational-evidence.md) - [Host business grounding guide](https://praxisui.dev/guides/ai-host-business-grounding) - [Enterprise proof](https://praxisui.dev/enterprise-proof) - [Dynamic Page examples catalog](https://praxisui.dev/examples/dynamic-page.json) ## Hierarquia de Fontes - `praxis-metadata-starter` (`canonical-backend-metadata`): Spring Boot starter adopted inside the host Java backend to define canonical backend metadata semantics, x-ui vocabulary, structural schema resolution, and resource-oriented discovery surfaces without moving domain ownership out of the company. - `praxis-config-starter` (`canonical-config-and-decision-governance`): Spring Boot starter adopted inside the host Java backend to define canonical remote UI config, ui_user_config semantics, ai_registry, api_metadata, AI orchestration contracts, and the natural governance boundary for semantic decision authoring, publication, and materialization. - `praxis-ui-angular` (`official-runtime`): Defines the official runtime, cockpit, and public Angular libraries installed inside the customer host app to materialize governed Praxis decisions while the host keeps routes, auth, theme, layout, deploy, and integration ownership. - `praxis-api-quickstart` (`reference-host`): Hosts the canonical starters in a real Spring Boot application and provides downstream integration proof without becoming the owner of metadata, configuration, AI, or decision semantics. - `praxisui-http-examples` (`published-operational-evidence`): Defines what is operational now on the published backend and classifies examples as llmOperational, protectedContract, or referenceOnly. - `praxis-ui-landing-page` (`official-public-docs`): Publishes official public documentation, guides, and LLM-facing entry points, but does not redefine canonical backend or runtime contracts. Regras de precedência: - Canonical contract beats editorial summary. - Published operational evidence beats site-level extrapolation about what works now. - Aggregated capabilities are snapshots, not a second source of truth for structural schema. - Do not present AI-generated JSON or patches as the primary Praxis modeling unit; use governed semantic decisions and derived materializations. ## Classes de Evidência - `confirmed_today`: Supported by current code, runtime, documentation, or local validation. - `publicly_proved`: Demonstrated through the published quickstart, Employee operations — enterprise casework, dynamic-page catalog, or HTTP examples. - `local_authenticated_proof`: Demonstrated locally against the canonical quickstart and Neon with authentication/origin protection, but not safe as a public unauthenticated example. - `architectural_direction`: Canonical platform direction for surfaces that still need repeatable public proof or productized rollout evidence. - `roadmap`: Needs productization, rollout proof, or additional public evidence before becoming sales copy. Não transforme `architectural_direction` ou `roadmap` em disponibilidade atual. Exemplos `protectedContract` documentam contratos protegidos e não são uma lane safe-first para writes por agentes. ## Catálogo Resumido de Capacidades A fonte machine-readable completa é `/llm-index.json#capabilityCatalog`; consulte-a para summaries, surfaces, consumers, exemplos e caveats por capability. - `praxis-metadata-starter`: `metadata.structural-schema` (`publicly_proved`), `metadata.semantic-discovery` (`publicly_proved`), `metadata.resource-query-and-analytics` (`publicly_proved`), `metadata.governed-option-sources` (`publicly_proved`) - `praxis-config-starter`: `config.domain-catalog` (`confirmed_today`), `config.domain-federation` (`confirmed_today`), `config.domain-knowledge` (`confirmed_today`), `config.domain-rule-lifecycle` (`publicly_proved`), `config.domain-rule-materializations` (`local_authenticated_proof`), `config.domain-rule-snapshots` (`confirmed_today`), `ai.semantic-intent-and-tools` (`confirmed_today`), `ai.shared-rule-handoff` (`confirmed_today`), `ai.generative-ui-machine-first` (`architectural_direction`) - `praxis-ui-angular`: `angular.authoring-manifests` (`confirmed_today`), `angular.runtime-observations` (`confirmed_today`), `ai.generative-ui-machine-first` (`architectural_direction`) - `praxisui-http-examples`: `evidence.http-corpus` (`publicly_proved`) ## Limites Que Devem Ser Preservados - `config.domain-knowledge`: The validator recognizes several operation types, but the current apply service executes only add_evidence and revert_evidence. - `config.domain-rule-lifecycle`: Simulation reports coverage and publication readiness; it does not evaluate the condition against business records. Write examples remain protectedContract and are not safe-first LLM operations. The direct supplier materialization read remains reference-only until the published backend confirms its committed fixture; use the governed supplier lookup as operational runtime evidence. - `config.domain-rule-snapshots`: Publication requires approved source provenance and two distinct composition approvers. The host must compile and activate snapshots with its executable registry. No public operational proof is currently linked from this index. - `ai.semantic-intent-and-tools`: Keywords, aliases and fuzzy matching may rank already-scoped candidates but must not decide primary intent. - `angular.authoring-manifests`: Manifest presence proves declaration, not complete execution, observation or platform certification. - `ai.generative-ui-machine-first`: Phase 0 is complete and Phase 1 is the active inventory milestone; broad Generative UI readiness is not currently a shipped claim. ## Exemplo End-to-End Canônico - ID: `employee-operations-casework` - Enterprise proof: `/enterprise-proof` - Public runtime: `/examples/dynamic-page/employee-operations-casework` - Catalog: `/examples/dynamic-page.json` - Operational HTTP evidence: `schemas-surfaces-human-resources-funcionarios`, `funcionarios-filter-basic`, `employee-state-snapshot-actions`, `employee-equipment-custody-surface`, `employee-payroll-history-related-resource` Use a prova enterprise e o runtime público para explicar a composição visual. Use os IDs HTTP operacionais para afirmar o que está publicado. Os IDs protegidos explicam o lifecycle governado, mas não autorizam execução write por default. ## Regras Operacionais para Agentes - Resolva intenção semanticamente por contexto, contratos, catálogos, capabilities e tools declaradas; não roteie intenção primária por palavras-chave ou regex. - Trate `/schemas/filtered` como contrato estrutural; capabilities agregadas são snapshots contextuais. - Domain Catalog, Domain Federation e Domain Knowledge fornecem significado, relações, evidência e grounding; não executam regras finais. - Domain Rules são owners de decisões reutilizáveis; UI, option sources, validações, workflow actions e approval policies são materializações consumidoras. - Domain Rule simulation diagnostica cobertura e readiness de publicação; não avalia a condição contra registros de negócio. - Quando houver `shared-rule-authoring-required`, pare o preview/apply local e faça handoff ao lifecycle governado. - Um authoring manifest prova declaração de capacidade, não certificação completa de seleção, execução, observação e explicação. - Para “o que funciona hoje no backend publicado?”, consulte primeiro `praxisui-http-examples/LLM_BOOTSTRAP.md`, depois `LLM_SURFACE.md` e `examples.manifest.json`.