Bring files in

Steps

1. On Files, tick that the client authorized you to bring these files in. It is recorded with your role, the time and the client.

2. To upload, drop files on Files: PDF, Word, Excel, CSV, Markdown, JSON, YAML and notebooks, up to [size limit] each.

3. To read from GitHub, choose Connect GitHub on Files and install the GovernanceOS app on the repositories you choose, on GitHub’s own page. For an organization’s repositories, its owner approves the app there.

4. Check the list on Files: each file shows its source, its hash at arrival and where it is used.

5. To bring in changed files, choose Move to the latest commit on Files. Reading the pinned commit again changes nothing unless a file is missing.

Good to know

• 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.
• The GitHub app reads files only. It can never write, run anything, or see a repository you did not choose.
• Files that look like secrets, such as keys and .env files, are refused: not read and not stored.
• For a client whose profile is residency-bound, first choose what the workspace keeps: names and hashes only, or the files themselves, stored in Canada.
• At handover the files move to the client. As its consultant you keep each file’s name and hash, not the file.

Where in the product

• Files
• Import a register

These open the prototype, on fictional institutions. People are shown as roles.

Related guides

• Import a register from a spreadsheet

  Upload a CSV or XLSX register, map its columns, and import every row as a typed value.

• Hand a workspace to the client

  Send the claim to the client’s administrator. After the claim, you keep a read-only copy.

• Draft a finding

  Write a finding that cites records, says what they show and who decides, then share it with the client.