@doxajs/praxis

Controlled-adoption prerelease: Publicly downloadable under Apache-2.0; Midtown Home Improvements is the sole supported consumer. External use is permitted without compatibility, support, warranty, roadmap, or production-readiness commitments.

Praxis is Doxa's canonical generator and command suite. It owns application generation, compilation, development hot reload, migrations, runtime roles, inspection, recovery, Drizzle Studio, Gnosis knowledge, and Theoria operations.

pnpm dlx @doxajs/praxis new MyApplication
cd my-application
pnpm install
pnpm dev

Run doxa --help, doxa -h, or doxa <command> --help for the complete command surface. Help flags exit successfully without running the selected command or creating generator output.

Install Doxa's optional realtime broadcasting core with doxa add keryx. Praxis enables framework.broadcasting and scaffolds the web listener, signed worker publish path, readiness check, same-origin browser authorization route, and optional Redis topology. Keryx is not added to Application.plugins.

Use doxa make:realtime-command Feature/SendTyping --ability=messages.participate to scaffold a Standard Schema-validated, throttled role and register it in Feature.realtimeCommands. Use doxa realtime-command:list to inspect the compiled command ID, ability, throttle, and deadline. Applications that register realtime commands must enable Keryx; compilation fails closed when no broadcasting provider owns their authenticated ingress and throttling.

Praxis follows a Laravel-like migration lifecycle with developer-authored, forward-only SQL. Use doxa make:migration <Name> to create a timestamped stub, doxa migrate:status to inspect pending or drifted files, and doxa migrate to apply and track them. Models do not generate DDL, and Drizzle Studio is an inspection tool rather than a schema-diff or migration generator.

Use doxa permission-source:list (or --json) to inspect the selected application permission source and its declared abilities without evaluating runtime permission records.

doxa model:list reports mapped-table migration management and runtime read-only status as independent settings, alongside the declared physical projection, primary key, and concurrency source.

Generate the source with doxa make:permission-source Feature/ApplicationPermissions --abilities=contact.read,contact.update. Use doxa make:service Feature/ApplicationAccess --provide when its ordinary service adapter must cross a Feature boundary.

Praxis registers the local read-only Gnosis MCP server with Codex, Claude Code, Cursor, and VS Code when it creates or upgrades an application and maintains a Doxa guidance block in the root AGENTS.md. Open the repository in a supported client; the client starts and stops Gnosis on demand in the application workspace, including when the application is nested in a monorepo. Along with compiled application inspection and documentation, Gnosis can perform bounded non-production model reads through Doxa's read-only persistence path. Some clients ask you to trust a project MCP server the first time they use it. Clients discover project MCP configuration when opening the workspace or starting a task. After creation, upgrade, or gnosis:install, reload or reopen the client and start a new task; an already-running task cannot acquire the newly registered tools. If a new task still lacks them, inspect the client's MCP startup error; registration files alone do not prove that the server initialized. Registrations use a portable repository-relative Node launcher rather than a machine-specific absolute path or an undocumented cwd field; nested registrations pass the app root explicitly to doxa mcp --cwd=... before starting the installed Praxis package.

The managed guidance and MCP initialization disclose Doxa's packaged programming model automatically. Gnosis explains roles, components, transaction ownership, provider/service boundaries, and atomic versus after-commit versus eventual orchestration. If matching Gnosis guidance is unavailable, agents are instructed to stop Doxa-specific structural and architectural changes until the startup or version issue is resolved.

Human-facing builds print handbook-linked provider/service and canonical-folder advisories returned by the compiler. These warnings communicate intent without giving paths runtime meaning.

Regenerate one or more project registrations after removing or customizing them:

pnpm doxa gnosis:install --agent=codex,claude

doxa mcp is the underlying stdio entrypoint for clients and protocol diagnostics, not a process developers normally start themselves.

Upgrade an existing application with a reviewable plan and post-install validation:

pnpm doxa upgrade --dry-run
pnpm doxa upgrade --verify

For applications whose installed Praxis predates doxa upgrade, bootstrap once with pnpm dlx @doxajs/praxis upgrade.