How navapbc/strata works
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 README · CONTRIBUTING.md Contributing · docs Docs · pull_request_template.md PR template
Components 20
Core docs
Primary repository entry points and supporting documentation.
Governance
Decision records and repo policies that define how the ecosystem is managed.
- ADR index · Catalog of architectural decisions.
docs/decisions/index.md - ADR template · Markdown template for new architectural decision records.
docs/decisions/template.md - Markdown ADRs · Policy decision to use Markdown architectural decision records.
docs/decisions/0000-use-markdown-architectural-decision-records.md - Contributing · Rules for proposing and submitting changes.
CONTRIBUTING.md - Code of conduct · Participation and behavior standards for the community.
CODE_OF_CONDUCT.md - Security · Vulnerability reporting and security contact guidance.
SECURITY.md
Contributor workflow
GitHub-native issue and pull request interfaces for proposed changes.
- CODEOWNERS · Paths and review ownership for maintained areas.
.github/CODEOWNERS - Bug issue · Structured intake for bug reports.
.github/ISSUE_TEMPLATE/1_bug_report.yml - Feature issue · Structured intake for feature requests.
.github/ISSUE_TEMPLATE/2_feature_request.yml - Epic issue · Higher-level work intake for multi-step efforts.
.github/ISSUE_TEMPLATE/epic.md - PR template · Standard format for pull request submissions.
.github/pull_request_template.md
Branding
Visual assets used by the documentation site and README.
- Brand 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 · External platform hosting the repository, issues, and pull requests.
- Infra templates · Separate AWS and Azure infrastructure template repositories.
- App templates · Separate Rails, Next.js, and Flask application template repositories.
- SDK · Separate Strata Rails-based SDK repository.
- CLI · Separate Strata platform CLI repository.
Connections 23
- 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.