ERP / API integrations

1Input

A PDF with the ERP endpoint specification and the existing integration code in the repository.

2Process

1. reads the specification and the existing code in your repository
2. presents a plan before making changes - first the intent, then the file diffs
3. writes code, runs tests and migrations; asks for consent only for a command that could break something
4. after every turn it shows “What I changed”; one click undoes the file changes of the whole turn
5. all of it in VS Code on your computer; Forge connects only to your tenant

3Result

Code changes with a “What I changed” list - in VS Code (Obsigen Forge).

4Measurement results

• 13 → 1 confirmation cards¹ - in a typical Forge turn

The configuration and source of every result are in the footnotes.

5Where the data is

The code remains in the repository on your computer; the model receives only the fragments needed in a given turn. Secrets from configuration files are excluded, and risky commands require confirmation.

where it runs code, tests and commands: your computer · model: provider in the EEA

Data, layer by layer →

6Company glossary

Terms from this process and how Obsigen remembers them - sample entries in the company glossary:

WZ

goods issue note - field wz_no, not “invoice”

MPK

cost center; the company glossary knows the list

staging

test server - deployments go there first; to production only after confirmation