Engine 02 / Project recovery

Find the project’s true state. Then move one version forward.

Start a private evidence workspace, attach what exists and protect working features before the next release changes them.

Create recovery account Sign in

Indian product team reviewing project evidence and recovery checkpoints — **Private by design**Evidence, findings and version freezes stay attached to one project.

Prepare a Project Rescue brief

From original source to a reviewed checkpoint

Upload → Understand → Verify → Repair → Export

Follow the evidence for each source. These are actions and capability boundaries, not a completion score.

1
Upload
Add an archive record, then attach your ZIP (up to 25 MB). Documents support up to 5 MB. Uploaded originals are hashed and quarantined.
2
Understand
Request inventory and static observations, then inspect the bounded JS/TS function map on the source card. Locations and parameter counts are structural evidence; behaviour, callers and coverage remain unverified.
3
Verify
Choose the Node module on the source card, then request its existing script checks. Dependencies are not installed. Review all discovered modules and their current or historical results; owner reports remain separate from sandbox results.
4
Repair
Protect a checkpoint and plan one bounded fix. Make and test changes in an isolated external copy. Maviter currently records this work; it does not patch your source.
5
Export
Download frozen reports, or prepare a private bundle of your uploaded repaired ZIP and patch from a current repair review. Clean installation and GitHub publishing remain separate steps; a report is not a repaired application.

One project / Multiple evidence sources

Bring whatever proves the current state.

Use Maviter to record intended features alongside source observations and test evidence. Bounded JS/TS maps identify function locations, parameter counts and direct export flags, with skipped or unsupported files listed. Behaviour, callers and test coverage remain unverified; source repair happens in your external working copy.

GitHub repositoryRecord a locator and optionally observe public default-branch metadata; source and history are not imported.

Locator + metadata

ZIP

Project archiveUpload a private source snapshot up to 25 MB after creating its evidence record. Git history may be unavailable.

Private upload

URL

Live websiteRecord a URL and your observations. Maviter does not crawl it or inspect its private backend.

Locator + notes

Status and handoff filesUpload a UTF-8 Markdown or text document up to 5 MB. Treat its claims as unverified until checked.

Private upload

REF

Feature referencesRecord an authorized example and the behaviour you want to preserve or implement.

Locator + notes

The checkpoint rule

Record what must keep working.

Example conventionv3.1 / Festivals stable

Name the festival calculations, data contract and screens to protect, with expected results and regression tests. The checkpoint freezes the record; your external repair workflow must enforce that boundary in source code.

Example onlyTests requiredSource enforcement external