Solutions / Quality, regulatory and compliance leads
Show who changed what with AI, who signed for it, and that the record is intact.
For quality, regulatory and compliance leads in regulated engineering. Neural Inverse produces the evidence; your quality system and your assessor decide what it proves.
- For
- Quality, regulatory and compliance leads
- Record
- Hash-chained, sealed every minute
- Approvals
- Signature records with re-authentication
- Verification
- Offline, standalone verifier
- Standards
- Evidence toward your frameworks
What you own
What quality and compliance answer for.
Controlled changeChanges to controlled items, released baselines and trace data go through your change process, whoever or whatever drafted them.
Signatures that mean somethingAn approval needs a named person, a meaning and a reason, and the author cannot approve their own work.
Accounting for AI useAn assessor may ask which parts of a release AI produced, with which model, and who reviewed them.
Records that lastRecords are kept for years, unchanged, and must be checkable by someone who does not trust your systems.
AI services outside your toolsUse of AI vendors' own services belongs in the record too.
What Neural Inverse gives you
Evidence produced as the work happens.
Each row is a capability of Neural Inverse Build or Govern in use today.
Written with the changeEvery change and every enforced decision is written in the same database transaction as the change. If the entry cannot be written, the change does not happen.Govern · Audit and evidence
Electronic signature recordsAn approval is a signature record in the repository with the signer's printed name, time, meaning and reason, made with re-authentication. Verification refuses a changed request, a replayed record and any separation-of-duties breach.Build · Editor, Agents and CLI
Evidence packsA signed pack for a release, a change, a trace or a time range answers which lines AI touched, which model and context were used, who approved and what left the boundary, with every gap listed.Build · Editor
Sector templatesStarting agent rules for avionics, medical devices, automotive, finance, mainframe, firmware, FPGA and industrial control. Applying one never removes or loosens a rule you already have.Govern · Agent policy and approvals
Retention and legal holdsOlder entries move to your own bucket as signed segments, under Object Lock in compliance mode where you choose. Retention can be lengthened, never shortened, and a legal hold keeps entries in the hot tier.Govern · Audit and evidence
Compliance rule packsRule packs for SOC 2, ISO 42001, the EU AI Act, GDPR, HIPAA and other frameworks check your organisation's state and store findings and evidence records. A pass means a check found what it looks for, not that a control is met.Govern · Audit and evidence
Vendor audit recordsAudit and usage records pulled from AI vendors' APIs or pushed by tools, kept beside Govern's own with their own signed exports.Govern · Audit and evidence
How a change moves
How a controlled change moves.
- ProposeAn engineer or an agent drafts a change to a controlled item.
- VerifyYour qualified tools and your organisation's signed checks run on it.
- ApproveEnrolled approvers other than the author sign with re-authentication, stating the meaning and the reason.
- RecordChange, results and signatures are kept together, and CI re-checks the exact commit.
- Verify offlineYour assessor checks the evidence pack or signed export without access to your systems.
For your auditor
What you can show an auditor.
Neural Inverse provides evidence toward the frameworks you report against. Certification stays with your organisation and assessor.
Signed exportsNDJSON or CSV for any time window, with a manifest signed with Ed25519 that names the file's hash and its place in the chain.
Offline verificationA standalone verifier checks exported chains and archived segments with no network access and no connection to Govern, using the public keys of your installation.
Evidence packs per releaseIn OSCAL, in-toto, SLSA and CycloneDX, with an HTML report and CSV tables. Packs from several developers combine into one.
Access review decisionsEvery item, decision, reviewer and time of a campaign, with the audit entries behind them, exportable as JSON or CSV.
Context evidenceWhich context fed each AI request, which model call used it and which agent instructions a session started with, in a separate chain.
Neural Inverse provides evidence toward the standards you report against. Certification stays with your organisation and assessor.
What's next
Still being built.
Listed so you can plan around it. None of it is part of what works today.
Automatic evidence collectionMost compliance checks report a warning until someone records evidence for the control. Collecting evidence automatically is not part of this release.
Domain module verificationThe modules that drive your vendor tools are pre-release, and nothing is verified by a customer yet. Their verification state is published per capability.
Access reviews in the consoleAccess reviews run through the API today; their console page is not available yet.
Talk to our team.
Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.