Repave
Generate. Adopt. Configure. Upgrade. Observe. Remediate.
- Problem
- Repositories drift from the approved path.
- Input
- An approved baseline, a repository, and a requested lifecycle change.
- Outcome
- A gated generate, adopt, update, upgrade, observe, or remediate record.
- Availability
- Early access. Hosted generate is waitlist and invite.
by OpsDevCode
Try Repave with your repositorySee the governed lifecycleAll products
Job
Keep a repository on an approved path with deterministic gates, provenance, and evidence.
Repave owns the governed lifecycle of software repositories: golden-path generation, brownfield adoption, configuration change on an approved baseline, standards upgrades, observation of governed state, and restore of supported drift.
Those lifecycle capabilities are implemented. Hosted access is waitlist and invite — not general self-serve availability. Portal and catalog surfaces are ways to use Repave; they are not the product category, and Repave is not the OpsDevCode umbrella.
Observe now attaches a structured policy preview — allowed, denied, conditionally allowed, or unknown — from recorded ownership, baseline, and evidence. Writes still stop on deterministic gates. That is evaluation and routing, not family-wide enforcement.
Current state
Implemented: generate, adopt, configure, upgrade, observe, and remediate. Hosted generate is waitlist and invite, not general self-serve. There is no card form on the waitlist.
Owns
- Repository generation from approved blueprints
- Brownfield adoption without rewriting source
- Governed configuration change
- Standards and baseline upgrades
- Observe and supported remediate of governed files
- Deterministic gates and delivery evidence
Boundaries
- Infrastructure state custody (Overpass)
- Engineering economics (Toll)
- Cross-domain intelligent experience (Dispatch)