Technical review path
Proof that can be inspected, not just claimed.
A fast route for reviewers to check backend/platform work, AI workflow systems, DevOps discipline, public demos, CI, docs, runbooks, incident handling, and recovery behavior.
15-Minute Review
- Open the DriveDesk Core review route and public demo.
- Open the latest DriveDesk Core CI and Pages runs.
- Scan the skill evidence matrix.
- For AI automation roles, open the AI Ops offer demo.
- Open the proof repo matching the role.
- Check tests, CI, docs, runbooks, demo paths, and reviewer snapshots.
Pinned Proof Order
- DriveDesk Core: flagship backend/platform foundation.
- AI Ops offer demo: transcript, RAG, scoring, approval, and mock Bitrix handoff proof.
- DeployMate: DevOps and release discipline.
- MPlusForm: validation and trust boundaries.
Evidence Signals
- FastAPI/PostgreSQL backend and integration boundaries.
- Public demo, CI, OpenAPI, tests, and docs.
- AI workflow/RAG ingestion, retrieval, transcript analysis, lead scoring, approvals, and CRM handoff boundary.
- Release gates, runbooks, incidents, and recovery steps.
Current Principle
The point is not a perfect screenshot. The useful proof is that code, docs, CI, release gates, runbooks, incidents, and recovery steps are visible enough for a technical reviewer to evaluate behavior.