DOCUMENT GOVERNANCE SDK

Make every document change traceable

Keep an append-only record of how people and AI change your documents.

Document change log showing AI-proposed changes, human edits, approval status, and reviewer details.

The final document doesn't tell you how it got there

It doesn’t show whether a change came from a person or AI, what changed, or who approved or rejected it.

Final contract document linked to an approved AI change and a rejected human change record.

Document Management SDK manages document state and versions. Document Governance SDK records who or what changed the document, and how that change was handled.

See what changed, who produced it, and who approved or rejected it

Changes are appended as new records. The SDK cannot update or delete a record once it is written.

FILE_WRITE

Content was added, modified, or deleted in an editing session, by a person or by AI.

A proposed change does not produce this event unless it is applied to the document.

FILE_CHANGE_REVIEWED

A proposed change was approved or rejected. Records who produced it and who decided on it.

FILE_SAVE

Document changes were saved and committed as a new version.

Contract_Template.docx

Both changes produced by AI · Contract Review Agent

Reviewed by Jamie Carter · Human

Paragraph 3

Approved

BEFORE

The contract term is one year.

AFTER

The contract term begins on the signing date and remains effective for one year.

Paragraph 7

Rejected

BEFORE

Disputes shall be resolved through consultation.

AFTER

Disputes shall be resolved through arbitration by the Korean Commercial Arbitration Board.

				
					<pre>{
  "eventType": "FILE_CHANGE_REVIEWED",
  "object": {
    "name": "Contract_Template.docx",
    "version": 35
  }
}</pre>  

Answer the questions behind a document change

01

Who produced this change?

Identify whether a change came from a person, an AI model, or a system process.

02

Who approved
or rejected it?

Trace the actor responsible for the final decision.

03

What was proposed but not accepted?

Rejected changes stay in the record. The document only carries what was accepted.

INTEGRATION

End-to-end traceability for your documents

Capture evidence from both in-editor changes and storage-level file operations.

Diagram showing Editor SDK and Management SDK events flowing into Document Governance SDK change records.

GET STARTED

Bring traceable change records into your application

Explore the developer documentation to see how Document Governance SDK fits into your document workflow.