Renvor documentation

Version stamp

Applies to: renvor 0.0.0 · framework source 7d0816a · MSRV 1.94.0 · documentation set pre-release

This stamp is a single shared partial (docs/_stamp.mdx) imported by every prose page and the API reference. It binds this documentation snapshot to the immutable framework commit it describes. The framework remains unpublished and no release compatibility promise applies.

Read the status before the API

Nothing is published. No Renvor crate or executable can be installed from crates.io, and no compatibility promise applies before the first release. The code in the workspace is implemented and tested, but it is not yet a supported product. Do not adopt it for production work.

Phases 002 through 009 currently provide:

• a transport-independent kernel with seven lifecycle stages, provider resolution, configuration, cancellation, rollback, liveness, and readiness;
• the renvor CLI and transactional project generator;
• an opt-in REST and HTTP adapter, runtime validation, RFC 9457 Problem Details, OpenAPI 3.2 generation, and semantic compatibility checks;
• driver-neutral persistence ports implemented by direct SQLx and SeaORM adapters, tested on PostgreSQL and MySQL;
• an authentication domain and HTTP adapter with Argon2id passwords, verification and recovery, opaque cookie sessions, CSRF binding, authorization policies, audit events, and optional JWT and refresh-token flows.

The facade boundary still matters

The renvor facade depends on the kernel, configuration, and the off-by-default HTTP transport. It exposes neither persistence nor authentication. Those crates exist and are tested, but an application cannot opt into them through the supported facade today.

Generated projects also declare no Renvor dependency while the crates are unpublished. The CLI's route and OpenAPI relays work against a real instrumented binary, but no generated project can yet provide that binary.

The command is renvor

The product, facade crate, and installed executable share one spelling: renvor.

Item	Name
Product and organization	Renvor
Facade crate	renvor
CLI crate	renvor-cli
Executable	renvor
Project state directory	.renvor/
Environment prefix	RENVOR_

Where to go next

• CLI — command surface, output contract, and project generation
• Persistence — ports, adapters, transactions, and migrations
• Database portability — measured PostgreSQL/MySQL boundaries
• Authentication — implemented security properties and current limits
• Verification — what the repository actually runs
• API reference — rustdoc and facade boundaries
• Governance — authority and live records