[{"data":1,"prerenderedAt":455},["ShallowReactive",2],{"navigation_docs_en":3,"-en-architecture-systeme-information":78,"-en-architecture-systeme-information-surround":450},[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":37,"badge":80,"body":81,"category":80,"description":443,"extension":444,"links":80,"meta":445,"navigation":447,"path":38,"seo":448,"stem":39,"tags":80,"__hash__":449},"docs_en/en/2.architecture/6.systeme-information.md",null,{"type":82,"value":83,"toc":428},"minimark",[84,93,96,101,104,107,111,122,217,224,228,231,243,247,250,257,261,264,271,274,280,286,292,302,313,317,320,354,357,361,367,370,376,379,383,386,390,400,404,411,415,425],[85,86,87,88,92],"p",{},"An architecture describes components. An information system describes ",[89,90,91],"strong",{},"how they hold together",": where you enter, who does what, what is computed at the centre, what is retained, and what flows out. That is the view an auditor, a regulator or a future successor asks for — and it is the one most often missing.",[94,95],"amtm-si-map",{},[97,98,100],"h2",{"id":99},"access-channels","Access channels",[85,102,103],{},"Six ways in, a single system behind them. The web application and the two mobile applications serve the counter; the branch portal gives each point of sale its own space; the customer portal opens lookup and tracking; the administration interface stays separate from the other three.",[85,105,106],{},"None of these doors owns its data. They all read and write into the same foundation — which is what makes any gap between what a teller sees and what their director sees impossible.",[97,108,110],{"id":109},"system-users","System users",[85,112,113,114,117,118,121],{},"Your specification defines ",[89,115,116],{},"eleven roles",". The map above shows the ten profiles that access the system directly; the table below sets out, for the main ones, the ",[89,119,120],{},"data"," responsibility attached to them — not merely screen rights.",[123,124,125,138],"table",{},[126,127,128],"thead",{},[129,130,131,135],"tr",{},[132,133,134],"th",{},"Role",[132,136,137],{},"Data it answers for",[139,140,141,157,167,177,187,197,207],"tbody",{},[129,142,143,154],{},[144,145,146,149,150],"td",{},[89,147,148],{},"Super Administrator"," ",[151,152,153],"em",{},"(publisher)",[144,155,156],{},"Cross-cutting reference data: countries, currencies, partner catalogues. No access to a client's business data.",[129,158,159,164],{},[144,160,161],{},[89,162,163],{},"General Administrator",[144,165,166],{},"Branches, users, roles, partner configuration for its organisation",[129,168,169,174],{},[144,170,171],{},[89,172,173],{},"Finance Director",[144,175,176],{},"Chart of accounts, entries, trial balances",[129,178,179,184],{},[144,180,181],{},[89,182,183],{},"Compliance Officer",[144,185,186],{},"Customer files, alerts, decisions and filings",[129,188,189,194],{},[144,190,191],{},[89,192,193],{},"RBT Manager",[144,195,196],{},"Operations, statements, reconciliations, incidents",[129,198,199,204],{},[144,200,201],{},[89,202,203],{},"Branch Manager",[144,205,206],{},"Till sessions, discrepancies, approvals within its perimeter",[129,208,209,214],{},[144,210,211],{},[89,212,213],{},"Auditor",[144,215,216],{},"Read-only across everything, with no exception and no blind spot",[85,218,219,220,223],{},"The rule that binds them: ",[89,221,222],{},"whoever enters never approves."," Above a configurable threshold, a second signature is required — and it is recorded.",[97,225,227],{"id":226},"the-six-module-families","The six module families",[85,229,230],{},"They cut the system into clean boundaries: financial operations, network and treasury, finance and accounting, risk and compliance, data and intelligence, configuration and administration.",[85,232,233,234,237,238,242],{},"This split is not a presentation convenience — these are ",[89,235,236],{},"the internal boundaries of the code and the layout of the repository"," you will receive. Each module is detailed on its ",[239,240,241],"a",{"href":30},"own page",".",[97,244,246],{"id":245},"the-core-the-shared-services-layer","The core: the shared services layer",[85,248,249],{},"This is the level diagrams most often omit, and the one that decides the coherence of the whole. Business rules engine, ACID transaction management, workflows, notifications, documents, messaging, reporting, cache.",[85,251,252,253,256],{},"Each of these services is written ",[89,254,255],{},"once"," and called by the six families. A commission rule therefore exists in a single place: changing it changes it everywhere, with no need to remember which modules used it.",[97,258,260],{"id":259},"data-written-once-read-many","Data: written once, read many",[85,262,263],{},"Not all AiO data is alike. Confusing the kinds is the mistake that produces those systems where the dashboard shows one figure and the accounts another.",[85,265,266,267,270],{},"We distinguish ",[89,268,269],{},"four natures",", each with its own rules:",[272,273],"amtm-data-domains",{},[85,275,276,279],{},[89,277,278],{},"Reference data changes, but is versioned."," A commission rate card changes; the one from six months ago must remain readable, otherwise an old commission becomes inexplicable. An exchange rate is updated; yesterday's operation is read back at yesterday's rate. Reference data is never modified — a new version is created.",[85,281,282,285],{},[89,283,284],{},"Transactional data is written once and never moves."," This is the core. An accounting entry, a closed till session, a validated operation: none of these is modifiable. A correction creates new data linked to the old.",[85,287,288,291],{},[89,289,290],{},"Logs only ever append."," The audit log is cryptographically chained: each row carries the fingerprint of the previous one. Any alteration of history breaks the chain and becomes detectable — by you, or by an external auditor who does not have to trust you.",[85,293,294,297,298,301],{},[89,295,296],{},"Derived data is disposable."," Balances, trial balances, statistics, dashboards, projections: everything recomputes from the entries. That is what makes the classic gap between what the screen shows and what the accounts say impossible — since the screen ",[151,299,300],{},"is"," the accounts, read differently.",[303,304,305,308,309,312],"note",{},[89,306,307],{},"The test that validates the architecture."," If the entire reporting database were destroyed — every report, every aggregate, every dashboard — a single rebuild from the ledger would restore them identically. ",[89,310,311],{},"Nothing would be lost."," No system in which reporting is a source of truth can say the same.",[97,314,316],{"id":315},"retention-and-purging","Retention and purging",[85,318,319],{},"The periods are not decorative: they answer regulatory obligations that vary from country to country.",[321,322,323,330,336,342,348],"ul",{},[324,325,326,329],"li",{},[89,327,328],{},"Accounting entries",": kept permanently. They are never purged.",[324,331,332,335],{},[89,333,334],{},"Operations, customer files, supporting documents",": ten years after the last operation, adjustable per country.",[324,337,338,341],{},[89,339,340],{},"Audit log",": ten years, unalterable.",[324,343,344,347],{},[89,345,346],{},"Technical log",": ninety days. It never contains customer data in clear.",[324,349,350,353],{},[89,351,352],{},"Derived data",": no retention. It recomputes.",[85,355,356],{},"A purge never erases an entry: it archives the peripheral data whose legal period has expired, while keeping the record of the purge itself.",[97,358,360],{"id":359},"security-control","Security & control",[85,362,363,364,242],{},"Strong authentication, roles, encryption in transit and at rest, immutable traceability, monitoring, continuity. The detail is on the ",[239,365,366],{"href":26},"Security & compliance page",[85,368,369],{},"One point deserves to be isolated here, because it conditions reselling the product.",[85,371,372,375],{},[89,373,374],{},"Isolation is set in the database, not in the application code."," AiO is intended to be deployed at several organisations: isolation is therefore not a precaution, it is the product itself. Each row carries its owning organisation, and a security rule at engine level filters systematically. Even if the application code contained a flaw, the database would not return another organisation's rows.",[85,377,378],{},"That is what makes a multi-tenant deployment defensible before a third party — a partner, an auditor, or the organisation itself.",[97,380,382],{"id":381},"infrastructure-deployment","Infrastructure & deployment",[85,384,385],{},"The software is containerised, therefore indifferent to where it is hosted: local server, private cloud, public cloud or hybrid. That decision is yours and is taken at framing, because it commits both cost and data residency.",[97,387,389],{"id":388},"integrations-ecosystem","Integrations & ecosystem",[85,391,392,393,396,397,242],{},"Six transfer partners, banks, Mobile Money, ancillary services — all reached through a ",[89,394,395],{},"single configured module",", not six separate developments. Feed levels and access conditions are detailed on the ",[239,398,399],{"href":34},"Partner integration page",[97,401,403],{"id":402},"steering-governance","Steering & governance",[85,405,406,407,410],{},"Executive dashboards, alerts, reports and statistics are not a separate layer: they are ",[89,408,409],{},"readings"," of the ledger and of operations. They hold no truth of their own, and that is precisely what guarantees they cannot diverge from reality.",[97,412,414],{"id":413},"what-this-gives-you-on-inspection-day","What this gives you on inspection day",[85,416,417,418,421,422,242],{},"A regulator, a partner bank or an auditor never asks \"show me your software\". They ask for ",[89,419,420],{},"a reconstitution",": that day, that operation, that customer. Who did what, when, on which machine, approved by whom, and under which rule in force ",[151,423,424],{},"at that time",[85,426,427],{},"That is precisely what this information system makes possible — and what no spreadsheet, and no database whose rows can be edited, will ever produce.",{"title":429,"searchDepth":430,"depth":430,"links":431},"",2,[432,433,434,435,436,437,438,439,440,441,442],{"id":99,"depth":430,"text":100},{"id":109,"depth":430,"text":110},{"id":226,"depth":430,"text":227},{"id":245,"depth":430,"text":246},{"id":259,"depth":430,"text":260},{"id":315,"depth":430,"text":316},{"id":359,"depth":430,"text":360},{"id":381,"depth":430,"text":382},{"id":388,"depth":430,"text":389},{"id":402,"depth":430,"text":403},{"id":413,"depth":430,"text":414},"The complete map of the system — its channels, its users, its six module families, its service core, its data, its security and its infrastructure.","md",{"icon":446},"lucide:database",true,{"title":37,"description":443},"ue2Sa4o-X_b-S9PHqr9byIoWREJ0obBZyMkZ6cQjxEQ",[451,453],{"title":33,"path":34,"stem":35,"description":452,"children":-1},"What a sub-agent can realistically obtain, and why the project must never wait for an API.",{"title":41,"path":42,"stem":43,"description":454,"children":-1},"Six months, three tracks, four milestones. Month 6 opens no new work.",1787177558677]