Praxis LLM Source of Truth
Canonical hierarchy and reading guidance for agents interpreting the Praxis platform.
Praxis is a governed semantic decision and runtime materialization platform for enterprise internal applications. This document is a derived public projection; the canonical owners below remain the sources of contract truth.
Canonical hierarchy
praxis-metadata-starter
Role: 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
Role: 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
Role: 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
Role: 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
Role: published-operational-evidence
Defines what is operational now on the published backend and classifies examples as llmOperational, protectedContract, or referenceOnly.
praxis-ui-landing-page
Role: official-public-docs
Publishes official public documentation, guides, and LLM-facing entry points, but does not redefine canonical backend or runtime contracts.
Recommended reading order
- Need a fast orientation to the platform: https://praxisui.dev/llms.txt
- Need expanded contract, caveats, and precedence: https://praxisui.dev/llms-full.txt
- Need to annotate a host or understand how an LLM learns host business semantics: https://praxisui.dev/guides/ai-host-business-grounding
- Need to know what works now on the published backend: https://praxisui.dev/llm-operational-evidence
- Need the safe-first operational lane on the published backend: https://github.com/codexrodrigues/praxisui-http-examples/blob/main/LLM_BOOTSTRAP.md
- Need the buyer-facing enterprise proof for Praxis: https://praxisui.dev/enterprise-proof
- Need the executive commercial promise and top-level platform thesis: https://praxisui.dev/
- Need to explain how Praxis fits into Spring and Angular without taking ownership away from the host team: https://praxisui.dev/platform
- Need an adoption sequence from first value to controlled enterprise rollout: https://praxisui.dev/adoption
- Need to shape a first enterprise pilot around one API, one workflow, and one governed variation: https://praxisui.dev/start-pilot
- Need to explain the design partner or rollout partnership model after one flow is proven: https://praxisui.dev/design-partner
- Need to explain governed AI authoring over a table/runtime example: https://praxisui.dev/ai-authoring-proof
- Need an end-to-end page example with metadata, Angular runtime, quickstart API, public UI, and AI recipe: https://praxisui.dev/examples/dynamic-page
- Need machine-readable metadata for every Dynamic Page example: https://praxisui.dev/examples/dynamic-page.json
Evidence classes
- 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.
When sources diverge
- 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.