The Shared Drive and Project repository map
The firm's Projects Shared Drive is the production matter-file root. Its top-level folders are Navigator Project
codes, not display titles: a matter whose code is henderson-bungalow-purchase lives at
Projects/henderson-bungalow-purchase/. A code uses only lowercase letters, digits, and single hyphens; Navigator
requires it when a Project opens because the name is an equality check, not a display-name normalization.
The same convention is deployment-owned rather than guessed from a laptop or a repository:
| Deployment | Shared Drive root | Organization |
|---|---|---|
| Neon Law production | Projects | neon-law |
| Neon Law staging | Staging Projects | neon-law |
| Neon Law Foundation | NLF Projects | neon-law-foundation |
The organization is configuration rather than a name in Navigator's source, and one string means two different things
across the two vocabularies: the organization neon-law is staging, while the GCP project neon-law is production.
The organizations are named for the entities and the GCP projects for the deployments.
A Project has one repository and one portal, and both are the code. That matter's source lives at
neon-law/henderson-bungalow-purchase, holding its notation templates under templates/ and its client portal under
portal/, and Navigator serves that portal at /app/projects/henderson-bungalow-purchase/portal/ — the repository name
plus one literal segment. Nothing is composed, so nothing has to be parsed back apart, and there is no manifest anywhere
restating a name the repository already carries.
Drive holds the firm's legal working files and Navigator holds the matter record and asset provenance. Project repositories hold source only: never client uploads, answers, generated legal documents, secrets, dependencies, or build output. When CI publishes approved Project-scoped template or application output to Drive, it resolves the matter folder from Navigator rather than from a repository-supplied folder ID, writes one way, and records the publication for audit. A hand edit to that published output is drift, not a source change. Project participation grants Navigator and deployed-application access; it never grants GitHub Enterprise access.