4nk/smart_ide
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
smart_ide/docs/ia_dev-submodule.md
Nicolas Cantu 088eab84b7 Platform docs, services, ia_dev submodule, smart_ide project config 
- Add ia_dev submodule (projects/smart_ide on forge 4nk)
- Document APIs, orchestrator, gateway, local-office, rollout
- Add systemd/scripts layout; relocate setup scripts
- Remove obsolete nginx/enso-only docs from this repo scope
2026-04-03 16:07:58 +02:00

2.4 KiB
Raw Blame History

Submodule ia_dev

The repository 4nk/ia_dev is integrated as a Git submodule at ./ia_dev.

It holds the centralized AI agent team (definitions under .cursor/agents/, .cursor/rules/), deploy/, gitea-issues/, projects/<id>/conf.json, etc. Execution remains from the ia_dev root per upstream README; smart_ide provides the surrounding IDE vision, host scripts, and systemd units.

Clone with submodule

git clone --recurse-submodules https://git.4nkweb.com/4nk/smart_ide.git
cd smart_ide

Submodule already present but empty

git submodule update --init --recursive

Update to latest ia_dev commit

cd ia_dev
git fetch origin
git checkout <branch-or-tag>   # e.g. main
cd ..
git add ia_dev
git commit -m "chore: bump ia_dev submodule"

SSH remote for ia_dev (optional)

If you use SSH instead of HTTPS for the submodule:

git config submodule.ia_dev.url git@git.4nkweb.com:4nk/ia_dev.git

(Requires host key and deploy key configured for Gitea.)

Relation to smart_ide

Repository Role
smart_ide IDE target UX, local AI stack scripts, systemd, docs for deployment
ia_dev (submodule) Agent registry, project configs, deploy/ticketing/notary pipelines

The future agent gateway should treat ./ia_dev as the canonical checkout path on the server unless overridden by configuration. See system-architecture.md.

Trajectoire : service ia-dev-gateway

Un service HTTP dédié (features/ia-dev-service.md, API/ia-dev-gateway.md) prendra le relais pour les clients (Lapce, front, orchestrateur) : le sous-module reste la source de vérité des fichiers ia_dev jusqu’à migration vers un fork cloné ou embarqué au même chemin (IA_DEV_ROOT).

  1. Phase actuelle : sous-module + exécution manuelle / scripts depuis la racine ia_dev.
  2. Phase gateway : binaire ia-dev-gateway sur l’hôte, IA_DEV_ROOT pointant vers ./ia_dev.
  3. Phase fork : le fork ia_dev est référencé par smart_ide (sous-module mis à jour vers le fork ou remplacement documenté) ; le gateway ne change pas de contrat HTTP.

Ne pas supprimer le sous-module tant que la CI et les postes de dev ne sont pas alignés sur le fork et le service.