Praxis — Semantic Platform for AI-Native Enterprise Applications

Core thesis: Do not build AI on the side of the application. Build an enterprise application that, by definition, is already readable and operable by AI, humans, and integrations.

Tese central: Não construir IA ao lado da aplicação. Construir uma aplicação corporativa que, por definição, já seja legível e operável por IA, humanos e integrações.

What Praxis Is

Praxis Platform is a semantically oriented platform for AI-native enterprise applications — and a governed semantic decision and runtime materialization platform for internal applications — in which resources, rules, actions, data, and policies are described once in your Java/Spring Boot backend and operated across four channels:

Traditional Interfaces (@praxisui/* in Angular): tables, forms, lists, CRUD shells, dialogs, charts, and drawers rendered inside the company host application.
Generative & Composed Interfaces: dynamic pages (WidgetPageDefinition) and governed runtime variations materialized without generating disposable screen code.
Governed AI Agents: consultative and operational assistants grounded on /schemas/filtered, /schemas/domain, /schemas/surfaces, /schemas/actions, /{resource}/capabilities, and /api/praxis/config/ai/** within deterministic fail-closed boundaries.
HTTP Integrations & External Clients: REST/HATEOAS consumers operating over the exact same versioned contracts (ETag, If-Match, Idempotency-Key).

Praxis delivers the metadata leverage that platforms like Salesforce, SAP, and ServiceNow accumulated over decades, implemented cleanly on open enterprise standards (Java/Spring Boot, Angular, OpenAPI, JSON Schema, and JSON Logic) without proprietary lock-in.

O Que É a Plataforma Praxis

A Praxis Platform é uma plataforma semanticamente orientada para aplicações corporativas AI-native — e uma plataforma de decisões semânticas governadas e materialização em runtime — em que recursos, regras, ações, dados e políticas são descritos uma vez no backend Java/Spring Boot e operados por interfaces tradicionais, interfaces generativas, agentes de IA e integrações, mantendo autenticação, rotas, marca e deploy sob controle do host da empresa.

Canonical Source-of-Truth Hierarchy

Repository / Owner	Role Kind	Canonical Responsibility
`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.