# navapbc/strata architecture

> Architecture diagram of the GitHub repository navapbc/strata, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-04-06). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/navapbc/strata
- Repository: https://github.com/navapbc/strata

## Overview

1. **What this repository is**
   - This is not an application runtime repo. It is the **Strata umbrella repository**: a landing page, governance hub, and documentation home for Nava’s broader Strata ecosystem.
   - The architecture here is primarily about **project organization, contribution workflow, and decision tracking**, not services, APIs, or deployment.

2. **Ecosystem boundary**
   - The README makes clear that the actual product surface lives in separate repositories:
     - infrastructure templates: AWS and Azure
     - application templates: Rails, Next.js, Flask
     - SDK: Rails-based Strata SDK
     - CLI: Strata platform CLI
   - This repo’s role is to **direct users to those component repos** rather than contain the implementations itself.

3. **Documentation subsystem**
   - `README.md` is the primary entry point and system overview.
   - `docs/` contains supporting architecture documentation, especially decision records.
   - This suggests a **documentation-first governance model**, where the repo captures the platform vision and architectural standards.

4. **Architectural decision records**
   - `docs/decisions/` contains ADR-style records, including:
     - `0000-use-markdown-architectural-decision-records.md`
     - `template.md`
     - `index.md`
   - These files form a **lightweight architecture governance layer** for recording and indexing platform decisions in Markdown.

5. **GitHub collaboration workflow**
   - `.github/` contains the operational interface for contributors:
     - issue templates for bugs, features, and epics
     - pull request template
     - `CODEOWNERS`
   - This is the repo’s **human workflow boundary**: issues and PRs are structured before changes enter the repository.

6. **Community and policy layer**
   - Top-level files like `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, and `SECURITY.md` define the rules for participation, behavior, and reporting vulnerabilities.
   - These are not runtime components, but they are part of the repo’s **operating model** and should be shown as governance concerns in any architecture diagram.

7. **Branding and presentation assets**
   - `docs/assets/` contains the Strata logo and related visual assets used by the README and docs.
   - This is a small but distinct **presentation layer** supporting the platform identity.

8. **Repository metadata**
   - `code.json` appears to be a metadata/configuration file for repository-level tooling or cataloging.
   - There is no evidence in this tree of application source, package manifests, CI pipelines, or build/runtime code.

9. **Primary information flow**
   - The main flow is:
     - users land on the README
     - README routes them to the correct template/SDK/CLI repo
     - contributors use GitHub issue/PR templates to propose changes
     - architectural decisions are recorded in `docs/decisions/`
   - In other words, the repo acts as a **control plane for documentation and community interaction**, not a data plane.

10. **Operational implication**
   - If you are drawing the architecture, represent this repo as a **central reference and governance node** connected outward to multiple product repositories.
   - Avoid showing it as a service with request handling, storage, or compute; those responsibilities live elsewhere in the Strata ecosystem.

11. **Technology footprint**
   - The visible stack is intentionally minimal: Markdown documentation, GitHub-native contribution tooling, and static assets.
   - The only external platform materially implied here is **GitHub**, which hosts the repo and its issue/PR workflows.

12. **Overall architectural summary**
   - Strata’s architecture in this repository is a **platform foundation for standards, templates, and decisions**.
   - It provides the canonical description of the ecosystem and the governance artifacts that keep the separate template and tooling repositories aligned.

Main entry points: [`README.md`](https://github.com/navapbc/strata/blob/main/README.md) (README), [`CONTRIBUTING.md`](https://github.com/navapbc/strata/blob/main/CONTRIBUTING.md) (Contributing), [`docs`](https://github.com/navapbc/strata/tree/main/docs) (Docs), [`.github/pull_request_template.md`](https://github.com/navapbc/strata/blob/main/.github/pull_request_template.md) (PR template)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_core["Core docs"]
  node_readme["README<br/>entry point<br/>[README.md]"]
  node_docs["Docs<br/>documentation"]
  node_code_json["code.json<br/>repository metadata<br/>[code.json]"]
end

subgraph group_governance["Governance"]
  node_adr_index["ADR index<br/>decision index<br/>[index.md]"]
  node_adr_template["ADR template<br/>decision template<br/>[template.md]"]
  node_adr_0000["Markdown ADRs<br/>decision record"]
  node_contributing["Contributing<br/>policy<br/>[CONTRIBUTING.md]"]
  node_code_of_conduct["Code of conduct<br/>policy<br/>[CODE_OF_CONDUCT.md]"]
  node_security["Security<br/>policy<br/>[SECURITY.md]"]
end

subgraph group_workflow["Contributor workflow"]
  node_codeowners["CODEOWNERS<br/>ownership<br/>[CODEOWNERS]"]
  node_bug_issue["Bug issue<br/>issue template<br/>[1_bug_report.yml]"]
  node_feature_issue["Feature issue<br/>issue template"]
  node_epic_issue["Epic issue<br/>issue template<br/>[epic.md]"]
  node_pr_template["PR template<br/>pull request template"]
end

subgraph group_presentation["Branding"]
  node_assets[("Brand assets<br/>static assets")]
end

subgraph group_ecosystem["Strata ecosystem"]
  node_github["GitHub<br/>hosting platform"]
  node_infra_templates["Infra templates<br/>external repo"]
  node_app_templates["App templates<br/>external repo"]
  node_sdk_repo["SDK<br/>external repo"]
  node_cli_repo["CLI<br/>external repo"]
end

node_readme -->|"explains"| node_docs
node_readme -->|"routes to"| node_infra_templates
node_readme -->|"routes to"| node_app_templates
node_readme -->|"routes to"| node_sdk_repo
node_readme -->|"routes to"| node_cli_repo
node_docs -->|"contains"| node_adr_index
node_docs -->|"contains"| node_adr_template
node_docs -->|"contains"| node_adr_0000
node_adr_index -->|"indexes"| node_adr_0000
node_adr_template -.->|"guides"| node_adr_0000
node_contributing -->|"defines"| node_pr_template
node_contributing -->|"guides"| node_bug_issue
node_contributing -->|"guides"| node_feature_issue
node_contributing -->|"guides"| node_epic_issue
node_codeowners -.->|"reviews"| node_pr_template
node_code_of_conduct -->|"governs"| node_contributing
node_security -->|"extends"| node_contributing
node_assets -->|"supports"| node_readme
node_code_json -.->|"metadata for"| node_readme
node_bug_issue -.->|"hosted on"| node_github
node_feature_issue -.->|"hosted on"| node_github
node_epic_issue -.->|"hosted on"| node_github
node_pr_template -.->|"hosted on"| node_github

click node_readme "https://github.com/navapbc/strata/blob/main/README.md"
click node_docs "https://github.com/navapbc/strata/tree/main/docs"
click node_adr_index "https://github.com/navapbc/strata/blob/main/docs/decisions/index.md"
click node_adr_template "https://github.com/navapbc/strata/blob/main/docs/decisions/template.md"
click node_adr_0000 "https://github.com/navapbc/strata/blob/main/docs/decisions/0000-use-markdown-architectural-decision-records.md"
click node_contributing "https://github.com/navapbc/strata/blob/main/CONTRIBUTING.md"
click node_code_of_conduct "https://github.com/navapbc/strata/blob/main/CODE_OF_CONDUCT.md"
click node_security "https://github.com/navapbc/strata/blob/main/SECURITY.md"
click node_codeowners "https://github.com/navapbc/strata/blob/main/.github/CODEOWNERS"
click node_bug_issue "https://github.com/navapbc/strata/blob/main/.github/ISSUE_TEMPLATE/1_bug_report.yml"
click node_feature_issue "https://github.com/navapbc/strata/blob/main/.github/ISSUE_TEMPLATE/2_feature_request.yml"
click node_epic_issue "https://github.com/navapbc/strata/blob/main/.github/ISSUE_TEMPLATE/epic.md"
click node_pr_template "https://github.com/navapbc/strata/blob/main/.github/pull_request_template.md"
click node_assets "https://github.com/navapbc/strata/tree/main/docs/assets"
click node_code_json "https://github.com/navapbc/strata/blob/main/code.json"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_readme,node_docs,node_code_json toneBlue
class node_adr_index,node_adr_template,node_adr_0000,node_contributing,node_code_of_conduct,node_security toneAmber
class node_codeowners,node_bug_issue,node_feature_issue,node_epic_issue,node_pr_template toneMint
class node_assets toneRose
class node_github,node_infra_templates,node_app_templates,node_sdk_repo,node_cli_repo toneIndigo
```

## Components

### Core docs

Primary repository entry points and supporting documentation.

- [README](https://github.com/navapbc/strata/blob/main/README.md): entry point · Canonical landing page and overview for the Strata ecosystem. · `README.md`
- [Docs](https://github.com/navapbc/strata/tree/main/docs): documentation · Supporting architecture and guidance content. · `docs`
- [code.json](https://github.com/navapbc/strata/blob/main/code.json): repository metadata · Repository-level metadata or cataloging configuration. · `code.json`

### Governance

Decision records and repo policies that define how the ecosystem is managed.

- [ADR index](https://github.com/navapbc/strata/blob/main/docs/decisions/index.md): decision index · Catalog of architectural decisions. · `docs/decisions/index.md`
- [ADR template](https://github.com/navapbc/strata/blob/main/docs/decisions/template.md): decision template · Markdown template for new architectural decision records. · `docs/decisions/template.md`
- [Markdown ADRs](https://github.com/navapbc/strata/blob/main/docs/decisions/0000-use-markdown-architectural-decision-records.md): decision record · Policy decision to use Markdown architectural decision records. · `docs/decisions/0000-use-markdown-architectural-decision-records.md`
- [Contributing](https://github.com/navapbc/strata/blob/main/CONTRIBUTING.md): policy · Rules for proposing and submitting changes. · `CONTRIBUTING.md`
- [Code of conduct](https://github.com/navapbc/strata/blob/main/CODE_OF_CONDUCT.md): policy · Participation and behavior standards for the community. · `CODE_OF_CONDUCT.md`
- [Security](https://github.com/navapbc/strata/blob/main/SECURITY.md): policy · Vulnerability reporting and security contact guidance. · `SECURITY.md`

### Contributor workflow

GitHub-native issue and pull request interfaces for proposed changes.

- [CODEOWNERS](https://github.com/navapbc/strata/blob/main/.github/CODEOWNERS): ownership · Paths and review ownership for maintained areas. · `.github/CODEOWNERS`
- [Bug issue](https://github.com/navapbc/strata/blob/main/.github/ISSUE_TEMPLATE/1_bug_report.yml): issue template · Structured intake for bug reports. · `.github/ISSUE_TEMPLATE/1_bug_report.yml`
- [Feature issue](https://github.com/navapbc/strata/blob/main/.github/ISSUE_TEMPLATE/2_feature_request.yml): issue template · Structured intake for feature requests. · `.github/ISSUE_TEMPLATE/2_feature_request.yml`
- [Epic issue](https://github.com/navapbc/strata/blob/main/.github/ISSUE_TEMPLATE/epic.md): issue template · Higher-level work intake for multi-step efforts. · `.github/ISSUE_TEMPLATE/epic.md`
- [PR template](https://github.com/navapbc/strata/blob/main/.github/pull_request_template.md): pull request template · Standard format for pull request submissions. · `.github/pull_request_template.md`

### Branding

Visual assets used by the documentation site and README.

- [Brand assets](https://github.com/navapbc/strata/tree/main/docs/assets): static assets · Logo and other presentation assets used in docs. · `docs/assets`

### Strata ecosystem

External component repositories and hosting platform referenced by this umbrella repo.

- **GitHub**: hosting platform · External platform hosting the repository, issues, and pull requests.
- **Infra templates**: external repo · Separate AWS and Azure infrastructure template repositories.
- **App templates**: external repo · Separate Rails, Next.js, and Flask application template repositories.
- **SDK**: external repo · Separate Strata Rails-based SDK repository.
- **CLI**: external repo · Separate Strata platform CLI repository.

## Connections

- README → Docs: explains · The landing page points to the supporting documentation set.
- README → Infra templates: routes to · The umbrella repo directs users to external infrastructure template repos.
- README → App templates: routes to · The umbrella repo directs users to external application template repos.
- README → SDK: routes to · The umbrella repo directs users to the SDK repository.
- README → CLI: routes to · The umbrella repo directs users to the CLI repository.
- Docs → ADR index: contains · Documentation includes the decision record index.
- Docs → ADR template: contains · Documentation includes the reusable ADR template.
- Docs → Markdown ADRs: contains · Documentation includes the recorded ADR policy.
- ADR index → Markdown ADRs: indexes · The index catalogues the decision record set.
- ADR template → Markdown ADRs: guides · The template standardizes new decision records.
- Contributing → PR template: defines · Contribution guidance pairs with the PR submission template.
- Contributing → Bug issue: guides · Contribution workflow is initiated through structured issues.
- Contributing → Feature issue: guides · Contribution workflow is initiated through structured issues.
- Contributing → Epic issue: guides · Contribution workflow is initiated through structured issues.
- CODEOWNERS → PR template: reviews · Ownership rules shape pull request review routing.
- Code of conduct → Contributing: governs · Community standards frame contribution behavior.
- Security → Contributing: extends · Security reporting is part of the repo participation model.
- Brand assets → README: supports · Brand assets support the landing page and docs presentation.
- code.json → README: metadata for · Repository metadata complements the main entry point.
- Bug issue → GitHub: hosted on · Issue workflows depend on GitHub.
- Feature issue → GitHub: hosted on · Issue workflows depend on GitHub.
- Epic issue → GitHub: hosted on · Issue workflows depend on GitHub.
- PR template → GitHub: hosted on · Pull request workflow depends on GitHub.
