GovernanceOS home: Defensible AI Platform Northline Advisory
NA

Signed in as Practitioner, Northline Advisory.

AccountHelp and supportSign out

Bring in the documents behind this client’s systems: model documentation, validation reports, policies, notebooks. Upload them, or connect the GitHub repository where they already live.

Page states

Authorization recorded. “I am authorized by Nebula Mutual to bring these files into this workspace.” Ticked by Practitioner, Northline Advisory, for Nebula Mutual, on 2026-10-12 10:02 CT.

Upload files

Drop files hereor PDF, Word, Excel, CSV, Markdown, JSON, YAML and notebooks, up to [size limit] each.

GitHub

One repository is connected.

Learn more about the GitHub app

The GovernanceOS app reads files only. It can never write, run anything, or see a repository you did not choose.

Connected repository

RepositoryBranch and pathsPinned toLast readApproved
nebula-mutual/claims-routing-model
read-only: contents and metadata
main; docs/, validation/, registers/ commit 9f2c1e7, 2026-10-15 2026-10-16 09:12 CT, on your request by the organization owner of nebula-mutual on GitHub, 2026-10-15
Learn more about reading again

Reading the pinned commit again changes nothing unless a file is missing. Moving to the latest commit brings changed files in as new versions.

Files in this workspace

FileSourceHash at arrivalArrivedUsed in
model-card-claims-routing-v3.pdfUploaded by the practitioner
de050edafe57… show full hashde050edafe57b1616e0430829ee28204a1a014217e618fffa960d82d34148c7b
2026-10-14Claims routing: cited in a draft finding
validation/backtest-2026Q3.ipynbGitHub, nebula-mutual/claims-routing-model at commit 9f2c1e7
a47d6e80e738… show full hasha47d6e80e7388ed191d8c8f3fa970e2507af82e8322adcf953e15ec4c29ede95
2026-10-16Claims routing: cited in a draft finding
docs/prompt-policy.mdGitHub, nebula-mutual/claims-routing-model at commit 9f2c1e7
5dbfee8490cd… show full hash5dbfee8490cdcc712f521ce956c822757af642ff8b30b86c79b8775f462af0ae
2026-10-16Not used yet
vendor-attestation-2026.pdfUploaded by the practitioner
7ed9a31c82f7… show full hash7ed9a31c82f79d8d9b638b0dda8f68410886bc5de228d28e48bb175f146ff054
2026-10-12Customer assistant: vendor file
.envGitHub, nebula-mutual/claims-routing-model at commit 9f2c1e7none: not readRefused 2026-10-16refused: looks like a secrets file; not read, not stored
Learn more about files and evidence

A file in this workspace is not evidence. Evidence is attached to a gate by a named person, in the institution’s own tenant.

How a file becomes evidence

Learn more about files and evidence

A file here is not evidence yet. It becomes evidence when a named person attaches it to a gate, in the institution’s own tenant. At that moment its hash, and for GitHub its commit, go into the record. A later change to the file arrives as a new version. The attached version never changes.

What GovernanceOS never does

  • Run code or notebooks from these files
  • Write to a repository
  • Read or keep files that look like secrets, such as keys and .env files
  • See repositories nobody chose
  • Keep GitHub access after a disconnect

Where files live, and what happens at handover

  • In this client’s workspace, in the Canadian region.
  • When you hand a client’s workspace over, the files move to the client with it. As its consultant you keep a read-only copy that lists each file’s name and hash, not the file.
  • When you hand over your own institution’s workspace, everything moves, files included, and you keep no copy.
  • If your trial ends, the files freeze with the workspace and go into its one export file.

Handover

Who sees them

You, until the client claims the workspace; then the people the client adds.

Learn more about your assistant and files

Your assistant can read file names and hashes through the connector. It can never attach a file to a gate.

© 2026 GovernanceOS All rights reserved.Ver: 1.1.0

Disconnect GitHub from this workspace

Repository
nebula-mutual/claims-routing-model
What ends
The app’s read access, at once. No token is kept.
What stays
The four files already read, with their hashes and commit, and the refusal of .env.
On GitHub
The organization owner can also remove the app there.

This is a practitioner action on your own connection, not a decision by the client. You act as Practitioner, Northline Advisory.