Engineering notes

How Lumidocs models compliance, and why.

4 notes · 10 minutes in allBy Mathias Milsø Stephensen, Co-founder

  1. DOCUMENTDECISIONPLANOBLIGATIONPARAGRAPHOTHER DOCUMENTABBREVIATIONROLECROSS-REFERENCECONTRADICTION01ComplianceCompliance is a graph. Documents were the wrong place to keep it.Compliance lives in the relationships between obligations, decisions, facts and guidance. Documents hide them. A graph makes them explicit, and agents make the graph practical to build.The problem with documentsWhat a graph changesLet the agents wire the graphFix the type, not the document2 min readRead the note
  2. WORKFLOWREAD ALLCOMPAREREPORTVERIFY ALLAGAIN, EACH RUNFROM SCRATCHSTATEDOCUMENTPARAGRAPHCHANGEDPARAGRAPHSAME OBLIGATIONTERMOBLIGATIONDESIGN INPUTDESIGN OUTPUTDETERMINISTIC · ONE PER LINK: IS IT THERE?JUDGEMENT · ANY NUMBER: CONSISTENT? ADDRESSES IT?02ComplianceModel the domain firstAI on top of documents gives you fast drafts and reports, and all of it has to be verified from scratch. Model the domain first, and compliance becomes a state you can trust: you assert every piece of information, and every change is checked the same way, every time.Workflows inherit our problemsCompliance is a state, not a workflowModel the domainOwning the state2 min readRead the note
  3. PARAGRAPHDRAFTED · AGENTEDITED · QA LEADREVIEWED · QA LEADAPPROVE · RA LEADLINKADDED · AGENTEDITED · QA LEADREVIEWED · QA LEADCHANGE · QA LEADPLANFOR REVIEWDRAFTED · RA LEADREVISED · AGENTAPPROVE · RA LEADOBLIGATIONADDED · RA LEADFIXED TEXTFINDINGOPENRAISED · AGENTPROCEDURE: 3 DAYSINSTRUCTION: 5 DAYSCLOSE · QA LEAD03TrustTrusting AI in compliance: review what changed, onceHeld as a graph, compliance is owned piece by piece: every interpretation, decision, requirement and paragraph carries its own provenance and its own review. No assumption or changed decision slips into a document unnoticed.What did the AI do? Provenance down to the paragraphDoes my approval still hold? Signatures pinned to contentWhat else did this change? Impact traced through the graphCould the AI approve something? Only people can signUnder the hood3 min readRead the note
  4. SOURCE SYSTEMSSOURCE SYSTEMSONE GRAPHGITHUBCHANGEJIRAREQUIREMENTXRAYTESTEXCELTRACE ROWCONFLUENCESPECQMSPROCEDURESHAREPOINTDOCUMENTERP · PLMPARTWRITE-BACK · NOT YETCOMPLIANCE LIVES IN BETWEEN04Compliance operationsCompliance as a system of systemsMuch of what decides a company's compliance lives outside its documents and its QMS, in systems built for other jobs. To see compliance as a whole, all of them have to be brought into one graph.Compliance lives in many systemsCompliance lives in betweenStart from the source systemsOne piece at a timeWhere this is going3 min readRead the note

Talk to us

See what Lumidocscould do for your team.

Bring us a regulatory or quality problem. We’ll show you how we’d approach it with Lumidocs.

Who you’ll talk to

Mathias StephensenFounderms@lumi-docs.com