MARCELODeveloper infrastructure · Active development
RevDev
A native Windows control surface for durable multi-project AI-assisted development via Dev Relay—built to keep execution guarded, state visible, and long-running engineering work resumable across projects, chats and model boundaries.
The problem
AI-assisted development needs durable state, not chat memory.
Working across several repositories with AI assistants creates a coordination problem: goals drift, long operations lose visibility, failures repeat, and a new chat or model can inherit only fragments of what happened.
RevDev makes that work visible and resumable without becoming the execution authority. It is the operator-facing Windows surface; Dev Relay remains the guarded backend that validates branch/HEAD state, executes bounded missions and records exact results.
Architecture boundary
Control surface and execution authority stay separate.
The UI can show state, queue guarded work and expose typed product actions, but it does not turn into an arbitrary shell or silently bypass Dev Relay's safety contracts.
Durable continuity
A fresh agent can resume from machine-readable truth.
Project goals, exact results, evidence pointers and repository state live outside the conversation. That makes continuation possible across ChatGPT tiers, other hosted models, local agents or a human operator without reconstructing the project from memory.
Tool hub
Five products, one bounded operator surface.
RevDev integrates ExactArtifact, GapTrace, VektorDeck, CrashScope and EasyFlix through explicit provider contracts. Typed actions can open evidence or invoke product-owned workflows without merging repositories or exposing an unrestricted command surface.
Progress + failure learning
One user action can stay understandable across many internal operations.
The current architecture models grouped multi-step interaction cycles with plan, progress and liveness state, restart-safe persistence and one terminal outcome so a long cycle can remain visibly active without producing duplicate completion signals.
Structured outcomes, recurrence-aware classification and evidence integrity turn repeated automation failures into explicit recovery rules instead of repeated guesswork.
Windows lifecycle
Packaging is part of the system.
RevDev has a self-contained Windows x64 package, guarded installer/update/uninstall lifecycle, integrity manifests and a canonical installed-app/shortcut identity. Final restart acceptance and release-lifecycle qualification are still in progress.
Screenshots
Real final-state captures only.
The public screenshot set is intentionally pending the final acceptance pass. No mock dashboard is substituted here; the future dashboard, live-progress and tool-hub captures will come from the accepted normal installed state and will be sanitized before publication.
Current boundary
ACTIVE DEVELOPMENT — not a public release.
The durable architecture is portfolio-ready, but public release remains intentionally gated on final runtime, packaging, screenshot and publication acceptance. Repository publication, license selection, release tags and LinkedIn launch remain explicit approval gates.