[{"data":1,"prerenderedAt":193},["ShallowReactive",2],{"navigation_docs_en":3,"-en-architecture-modules":78,"-en-architecture-modules-surround":188},[4,14,40,54,60,66,72],{"title":5,"path":6,"stem":7,"children":8},"The essentials","/en/proposition","en/1.proposition/1.index",[9,10],{"title":5,"path":6,"stem":7},{"title":11,"path":12,"stem":13},"Your need, understood","/en/proposition/comprehension","en/1.proposition/2.comprehension",{"title":15,"path":16,"stem":17,"children":18},"Overview","/en/architecture","en/2.architecture/1.index",[19,20,24,28,32,36],{"title":15,"path":16,"stem":17},{"title":21,"path":22,"stem":23},"Technical choices","/en/architecture/stack","en/2.architecture/2.stack",{"title":25,"path":26,"stem":27},"Security & compliance","/en/architecture/securite","en/2.architecture/3.securite",{"title":29,"path":30,"stem":31},"The modules","/en/architecture/modules","en/2.architecture/4.modules",{"title":33,"path":34,"stem":35},"Partner integration","/en/architecture/partenaires","en/2.architecture/5.partenaires",{"title":37,"path":38,"stem":39},"Information system","/en/architecture/systeme-information","en/2.architecture/6.systeme-information",{"title":41,"path":42,"stem":43,"children":44},"The plan","/en/roadmap","en/4.roadmap/1.index",[45,46,50],{"title":41,"path":42,"stem":43},{"title":47,"path":48,"stem":49},"The method","/en/roadmap/methodologie","en/4.roadmap/2.methodologie",{"title":51,"path":52,"stem":53},"The budget","/en/roadmap/budget","en/4.roadmap/3.budget",{"title":55,"path":56,"stem":57,"children":58},"Vortex-Soft","/en/equipe","en/5.equipe/1.index",[59],{"title":55,"path":56,"stem":57},{"title":61,"path":62,"stem":63,"children":64},"Specification","/en/cdc","en/6.cdc/1.index",[65],{"title":61,"path":62,"stem":63},{"title":67,"path":68,"stem":69,"children":70},"Infrastructure","/en/infrastructure","en/7.infrastructure/1.index",[71],{"title":67,"path":68,"stem":69},{"title":73,"path":74,"stem":75,"children":76},"Mockups","/en/maquette","en/8.maquette/1.index",[77],{"title":73,"path":74,"stem":75},{"id":79,"title":29,"badge":80,"body":81,"category":80,"description":181,"extension":182,"links":80,"meta":183,"navigation":185,"path":30,"seo":186,"stem":31,"tags":80,"__hash__":187},"docs_en/en/2.architecture/4.modules.md",null,{"type":82,"value":83,"toc":175},"minimark",[84,93,100,103,106,109,114,121,128,132,135],[85,86,87,88,92],"p",{},"Twenty-three modules in ",[89,90,91],"strong",{},"7 functional families",", which are also the internal boundaries of the code and the layout of the repository you will receive.",[85,94,95,96,99],{},"This list covers chapters 8 to 27 of your specification, the foundation that carries them, and the ",[89,97,98],{},"two modules announced in chapter 4 without a detailed chapter"," — Visa Cards and Banking Partners. They are included in the commitment; their specification is produced with you at framing, before any development.",[85,101,102],{},"The count of twenty-three reconciles a gap the proposal flags in your document: chapter 4 announces 21 modules, the detailed chapters describe only 20. To these we add the ledger and reconciliation, which we bring into scope although your document does not list them.",[85,104,105],{},"Hover over a module to unfold its key features.",[107,108],"amtm-modules",{},[110,111,113],"h2",{"id":112},"a-note-on-the-count","A note on the count",[85,115,116,117,120],{},"Your chapter 4 announces 21 modules. The detailed chapters describe 20, with different numbering: CRM & KYC is detailed in chapter 21 but missing from the list, while Visa Cards and Banking Partners appear in the list without being detailed. ",[89,118,119],{},"Our delivery covers the union of both lists"," — the only reading that drops nothing.",[85,122,123,124,127],{},"One module does not appear in your document: ",[89,125,126],{},"reconciliation",". It is our addition, and the one we care most about. Without it, importing statements produces data that nobody confronts.",[110,129,131],{"id":130},"our-definition-of-done","Our definition of \"done\"",[85,133,134],{},"A module is delivered when it passes, without us:",[136,137,138,145,151,157,163,169],"ul",{},[139,140,141,144],"li",{},[89,142,143],{},"Acceptance on your real operations",", not on textbook cases",[139,146,147,150],{},[89,148,149],{},"Verification across every role"," — each sees exactly what it must see, and nothing more",[139,152,153,156],{},[89,154,155],{},"The trial balance is exact",": on the acceptance dataset, postings sum to exactly zero",[139,158,159,162],{},[89,160,161],{},"Automated tests"," replayed on every integration",[139,164,165,168],{},[89,166,167],{},"Documentation",", user and technical",[139,170,171,174],{},[89,172,173],{},"Deployed to your staging environment",", and handled by your teams",{"title":176,"searchDepth":177,"depth":177,"links":178},"",2,[179,180],{"id":112,"depth":177,"text":113},{"id":130,"depth":177,"text":131},"The full functional coverage, family by family.","md",{"icon":184},"lucide:blocks",true,{"title":29,"description":181},"Rwm1i0v-2_49VN3atsSj4CUusTY4UM24Lh3ptD62v2k",[189,191],{"title":25,"path":26,"stem":27,"description":190,"children":-1},"Tamper-evident audit trail, split of duties, KYC/AML — the level your trade requires.",{"title":33,"path":34,"stem":35,"description":192,"children":-1},"What a sub-agent can realistically obtain, and why the project must never wait for an API.",1787177558602]