Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Prompt file imported from zekiriabd/SDD-Pro (.codex/prompts/sdd-reverse-init.md). Fill in {{arguments}} before use. Copyright stays with the author.
Arguments: {{arguments}}
/sdd-reverse-init {LegacyProject}
Rôle
Pré-conditionner un projet legacy déposé dans workspace/old/{LegacyProject}/ avant lancement Phase 1 (/sdd-reverse-inventory). Bootstrap purement structurel.
Pré-conditions
workspace/old/{LegacyProject}/ existe et contient ≥ 1 fichier source (non vide, non binaire-only)
Si absent → STOP + ERROR [REVERSE_NO_SOURCE].
Si binaire-only détecté (aucun fichier source lisible parmi .cs/.aspx/.java/.php/.pas/.frm/.sql/...) → STOP + ERROR [REVERSE_BINARY_ONLY] + escalade (hors-scope §0 design doc).
Actions
Créer workspace/old/{LegacyProject}/.sys/ si absent
# .sys/ — Artefacts reverse engineeringDossier généré par /sdd-reverse-init. Contient les outputs des phases 1-4 du workflow reverse.NE PAS éditer manuellement les .json (ownership scripts déterministes).Voir .sdd/docs/reverse-engineering-workflow.md
Aucune lecture du legacy lui-même (read-only sur la structure, pas sur le contenu)
No-spawn
Idempotence
Re-lancer /sdd-reverse-init {P} sur un projet déjà initialisé est un no-op silencieux (le README est préservé).
Voir .sdd/docs/reverse-engineering-workflow.md §1 + §2 pour le contexte pipeline.
Installed into a catalogue, chosen by a router
Install sdd-reverse-init and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
