praxonneGitHub

Target architecture

A narrow waist between traffic, code, and review.

Praxonne separates the data plane that connects requests from the control plane that may generate and propose new behavior. The shared boundary is a versioned, schema-validated execution contract.

End-to-end flow

Freeze policy first. Execute second.

  1. 01

    Ingress

    Normalize the request, resolve tenant identity, and match only declared forward or reverse routes.

  2. 02

    Policy

    Freeze destination, bundle digest, model profile, budgets, and promotion permissions before execution.

  3. 03

    Child workload

    Connect request to response without a shell, inherited secrets, host mounts, or unrestricted egress.

  4. 04

    Contract

    Capture bounded output, response metadata, logs, and a content-addressed evidence record.

  5. 05

    Proposal

    For an eligible result, create an idempotent feature branch and draft PR through a least-privileged GitHub App.

Data plane

Fast path

  • Explicit route and destination policy
  • One bounded child workload per connection
  • Backpressure, deadlines, and output caps
  • Structured evidence without payload leakage

Control plane

Change path

  • Provider-neutral Agent Pontifex bridge adapter, pinned provisionally
  • Content-addressed source and prompt provenance
  • Idempotent branch and draft PR creation
  • Human review and protected deployment

Web routing invariant

One route, one path-owned module.

The Leptos web server's target pattern mirrors filesystem routing: each public path owns one route module, and a generated manifest rejects duplicates or orphaned pages at build time. SeaORM remains the data boundary; route modules never migrate schemas at boot.

src/routes/
├── index.rs          → /
├── routes/index.rs   → /routes
├── routes/_id.rs     → /routes/:id
├── runs/index.rs     → /runs
└── security.rs       → /security

Repository topology

Small ownership surfaces, one dependency order.

Interfaces → core → services → clients → infrastructure → fleet. Zed records cross-repository inputs while native toolchains compile each language.

praxonne-interfaces

Schemas and public/private type surfaces

praxonne-lib-core

SeaORM entities and shared frontend/backend rules

praxonne-sync

Praxonne facade over opto-sync contracts

praxonne-api-server.rs

Rust JSON control-plane API

praxonne-web-server.rs

Leptos multipage operations surface

prax-*-proxy-server.rs

Forward, reverse, and bidirectional data plane

praxonne-clients

Schema-conformant SDK matrix

praxonne-cli

Cross-platform operator CLI

praxonne-infra

Cloudflare and Kubernetes application manifests

praxonne-monorepo

Zed-managed fleet inventory