Reliability
Vextro ships with certifiable guarantees. Metadata depth is tested across four tiers, gated on every pull request, and documented in a published contract.
Metadata depth certification
Rich text fields can nest blocks to arbitrary depth. Vextro certifies that deeply nested content round-trips through Convex storage and back without exceeding depth or byte limits. Each tier is tested with structured fixtures and must pass all constraints.
| Tier | Authored depth | Max persisted | Min headroom | CI gate |
|---|---|---|---|---|
| D1 — Standard Sufficient for all typical nested content structures. | 25 levels | ≤ 13 | ≥ 3 | PR gate |
| D2 — Deep Covers recursive block types and deeply nested editorial workflows. | 100 levels | ≤ 13 | ≥ 3 | PR gate |
| D3 — Extended Stress-tested for extreme editorial depth, certified on every release. | 500 levels | ≤ 13 | ≥ 3 | PR gate |
| D4 — Nightly Nightly validation at extreme depth. Regression detection before it reaches a PR. | 1000 levels | ≤ 13 | ≥ 3 | Nightly |
Source: docs/superpowers/reference/metadata-depth-contract.md · Tested in packages/vextro/src/convex/__tests__/metadataDepthCertification.test.ts · Gated by .github/workflows/metadata-depth-gate.yml
Depth budgets and limits
These constants are defined in the contract and cannot be exceeded by any certified release.
Storage depth budget: 10
Maximum encoded depth stored in the Convex document. All certified tiers stay well within this budget after encoding.
Hard threshold: 14
The absolute limit before storage errors. The release gate certifies to this threshold with headroom maintained against the runtime ceiling.
Runtime ceiling: 16
Maximum depth during materialization. Certification maintains at least 3 levels of headroom between the persisted depth and this ceiling.
Partition limit: 750 KB
Maximum bytes per canonical partition. Uniform across all tiers — prevents any single document from causing storage pressure.
Total limit: 2.5 MB
Maximum total bytes across all canonical partitions. Enforced on every certification run regardless of tier.
Headroom policy: ≥ 3
Every release must maintain at least three levels of clearance between persisted depth and the runtime ceiling. No exceptions.
Schema diagnostics
A built-in diagnostics page shows fingerprint sync state for all registered collections and globals, stale metadata, and archived items — at runtime, in the admin panel itself.
Schema diagnostics docs →CI gates on every PR
D1, D2, and D3 certification runs on every pull request. D4 runs nightly. No release can ship if metadata depth certification fails — the gate is non-negotiable.
CI/CD integration docs →Audit it yourself
The depth contract, test suite, and CI workflows are all in the repository. Read them.