Put Your Industry's Rules into Every Change
Your regulations, standards and policies are added once to AppGraph, a living map of your software. Every Change (one piece of work) is built and signed off against them, as a specialized team would.
Attach Each Rule to the Software It Covers
During onboarding, we attach your industry's standards and your own policies to the parts of your software and data they apply to.
Recorded once. Present at every step.
It does not depend on who is on the team that week.
Add Rules Once. Apply Them to Every Change
The full step-by-step process, with each engineer checkpoint, is on How it works.
- 1

Add, during the System Assessment
Matched to the parts of your software and data they cover, reviewed with you, recorded in AppGraph.
- 2

Apply at requirements
The PRD (product requirements document) covers who gets access, how data is handled, blocked access and failures.
- 3

Apply in build and test
The technical plan follows the rules. Tests are written from them.
- 4

Check at engineer sign-off
A senior engineer with industry experience reviews and signs off. AI does the work. The engineer stays accountable.
- 5

Deliver with evidence
A record of which rules applied, how they were met, the tests and who approved.
- Industry standards and your policies recorded in AppGraph during onboarding
- Requirements and specifications written from that knowledge
- Senior engineer review against the rules that apply, with the decision recorded
- Approval steps for changes, witnessed tests, the option to roll back, and the full audit trail for every Change
- Automatic linking of each rule to the parts of your software it covers, shown on the Change
- Automatic policy checks during each Change, attached to its record
- Export of Change evidence into your audit system
See the Industries Where We Have Done This
If yours is not here, the System Assessment shows which standards apply and what it takes to add them.

Healthcare
HIPAA safeguards for patient health data (PHI): access, sign-in, audit records, secure transfer; HL7 and FHIR rules for health-data exchange
Case study

Fintech and banking
Security for card payments and banking, approving transactions and keeping them accurate, handling financial data
Case study


Adtech and media
Privacy and consent under GDPR and CCPA, data-sharing and opt-out rules, advertising data flows
Case study

Manufacturing and IIoT
Safety rules for operations, reliable device data, and operational systems kept apart from the rest

eCommerce
Payment-data safeguards, customer-data privacy, staying up during traffic peaks
Follow a Healthcare Change, Step by Step
An illustrative example, based on the approach we used for Nanox.
- The Product Owner asks"Allow authorized care-team members to export a patient's medical record"
- AppGraph adds the rulesHIPAA controls, your export policies and every affected dependency
- PRD approved before codeExpected behavior, security and failure scenarios, and the estimate
- AI builds, the engineer supervisesThe engineer reviews decisions on access, patient data and connected systems
- Tests from the requirementsWritten from the rules and run on every Change
- Arrives with its recordCode, tests, rules applied and the engineer's sign-off. Then it goes through your own release process
Get the Record Your Auditor Asks For
It appears in your Portal, the AI-MSL web app, as soon as each Change is delivered. Add it to your SOC 2, HIPAA or PCI DSS evidence as is.
- Request and approved PRDWith acceptance criteria
- Controls and policies appliedPlus the affected parts of your software and the technical plan
- The code change and testsTests added or updated, with their results
- Sign-off decisions, with name and timeBy the senior engineer who signed off
- Documentation and release record
- Change approvals
- Testing evidence
- Who reviewed and when
- We develop and maintain your software to conform to the standards and policies in AppGraph, which you review and approve.
- We provide the complete record of how each Change was made, tested and approved.
- We do not audit or certify your organization or your product. Overall compliance also depends on your operations, infrastructure, agreements and, where required, an independent assessor.
- The Change record shows how the software was changed. Your app's access logs show how it runs. Both go into your audit file.
Frequently asked questions
How does AI-MSL know the rules of our industry?
They are added to AppGraph during onboarding, attached to the components and data they govern, and reviewed with you. From then on they are part of every requirement, specification, test and gate review, and the senior engineer who signs off is accountable for the match.
Who decides which standards apply to our application?
You do, with us. During the System Assessment we propose the regulations, standards and policies that apply to your components and data. You review and approve the list. It can be changed at any time.
Can we add our own security and engineering policies?
Yes. Internal policies, coding standards, access rules and architectural conventions go into AppGraph the same way and are applied the same way.
Are industry requirements tested automatically?
Testable ones are. Tests are derived from the controls and run on every Change. Requirements that cannot be verified by a test are checked by the senior engineer at the gate, and that review is recorded.
Do you guarantee our application is compliant?
No. We deliver Changes that conform to the requirements you set and the complete evidence of how. Compliance of the organization is yours, and certification is the auditor's.
What happens when a regulation or our policy changes?
The update goes into AppGraph, the affected components are identified, and the necessary work is proposed as estimated Changes for your approval.
Build Your Rules into Every Change
See which rules apply and the Changes needed to close the gaps.