quinzee.cloud

Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.

Contributor’s guide

2. Source layout and conventions

Path Responsibility
include/http/, lib/http/src/ Public HTTP API and private Asio/Beast/OpenSSL transport
include/quinzee/, lib/quinzee/src/ Host/capability contracts, helpers, persistence, engine mailbox and telemetry
src/quinzee_cloud/ Options, catalogue, migration, composition root and executable
src/quinzee_cloud/modules/ Service implementations, including deployments, managed engines and monitoring
src/qhq/ Native UI, background jobs and public-API client
deps/simple/ Build policy for the independent Simple package; no local toolkit source copy
lib/boost_json/ One compiled Boost.JSON implementation and wrapper
infrastructure/engines/ Fixed engine images, supervisor, TLS/CRL and engine telemetry
infrastructure/functions/ Registered-image runtime helper, private TLS gateway and real Functions host image
tests/compatibility/service_bus/, tests/compatibility/functions/ Locked official SDK/worker projects and isolated end-to-end fixtures
infrastructure/directory/ Dedicated PostgreSQL launcher, TLS slapd frontend and Windows attribute schema
src/quinzee_cloud/modules/directory_protocols/ Separate Entra/RBAC/managed-identity/LDAP frontends over the authority
infrastructure/observability/ Optional Collector/Grafana/Prometheus/Loki/Tempo configuration
test/ .NET/React compatibility application and its Bicep template
tests/ C++/helper/container/browser-adjacent compatibility checks and fixtures
scripts/deps/, scripts/dev/ Verified tool acquisition and development environment ownership
deps/ Dependency identities, patches and license evidence

Apply C++ standards (source checkout required), React standards (source checkout required) and the relevant cross-language standards before edits. Follow the public/private header boundary, RAII, explicit ownership and narrow third-party warning handling. Do not expose Boost transport types through include/http/ or make QHQ depend on provider state.

The canonical directory map and prerequisites are in project overview (source checkout required). The documentation ownership map (source checkout required) determines where a changed fact belongs; avoid copying protocol tables into multiple manuals.