# Your data needs visible boundaries 2026-10-27 ยท Architecture Designing a local workflow and explaining when a task uses an external service. ## Local is a configuration, not a slogan RadMesh is designed around an institutional node. Storing images and reports there does not mean every AI task runs there. Each deployment must explain which service processes each task and what information it receives. ## Every transfer needs an explanation Authorization, data minimization and an outgoing-transfer log are part of the design. When a feature uses an external service, its scope must be inspectable. Switching models should not hide a change in that boundary. ## The website has a boundary too Ask ChatGPT and Ask Claude share an editorial question and a public document URL. They do not attach studies, clinical conversations or private source code. Visitors can read and copy the question before opening the service. ## What this note does not certify This explains product architecture and communication. It does not certify regulatory compliance, installation security or suitability for real patient data. Those require deployment-specific verification. https://www.radicalmesh.com/en/research-and-posts/data-and-control