feat(profile): org-profile revamp — brand system, theme-aware banner, health files, repo standards

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,36 @@
+name: Bug report
+description: Something behaves differently than documented
+labels: ["bug"]
+body:
+  - type: input
+    id: version
+    attributes:
+      label: Version / commit
+      description: Release tag or commit SHA where you observed this
+      placeholder: v1.0.0 or a short SHA
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Reproduction
+      description: Minimal steps or code that reproduce the behavior
+      placeholder: |
+        1. …
+        2. …
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected vs actual
+      description: What the docs/README say should happen, and what happens instead
+    validations:
+      required: true
+  - type: textarea
+    id: env
+    attributes:
+      label: Environment
+      description: OS, runtime version (Node/Python), anything unusual
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/577Industries/.github/blob/main/SECURITY.md
+    about: Please report vulnerabilities privately — see our security policy.
+  - name: Commercial / general inquiries
+    url: https://577industries.com/contact
+    about: FORGE OS, custom AI development, and government/SBIR work.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,24 @@
+name: Feature request
+description: Propose a capability or improvement
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What can't you do today, or what costs more than it should?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed behavior
+      description: What you'd like to happen; API sketches welcome
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+    validations:
+      required: false

CODE_OF_CONDUCT.md

@@ -0,0 +1,85 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [info@577industries.com](mailto:info@577industries.com). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# Contributing to 577 Industries
+
+Thanks for your interest. Everything public in this organization ships with a license, CI, and citable evidence — contributions are held to the same bar we hold ourselves to.
+
+## How the organization is laid out
+
+Work is grouped into **programs**, each marked by a `577i-program-*` topic on its repositories:
+
+| Program | Topic | What it is |
+|---|---|---|
+| HELIOS | `577i-program-helios` | Calibrated heliophysics fusion (NASA SBIR) |
+| FORGE EVOLVE | `577i-program-forge-evolve` | AI-assisted legacy modernization (Navy SBIR) |
+| AEGIS | `577i-program-aegis` | Secure-messaging assessment (DARPA ASEMA) |
+| FORGE OS | `577i-program-forge-os` | Reusable TypeScript agent-infrastructure libraries |
+
+Conventions that every repo follows (topics, badges, README shape, releases) are written down in [`docs/repo-standards.md`](https://github.com/577Industries/.github/blob/main/docs/repo-standards.md).
+
+## Ground rules
+
+- **Conventional commits** — `feat:`, `fix:`, `docs:`, `test:`, `chore:`, `refactor:` (you'll see `docs(plan):`-style scopes throughout the history).
+- **PRs over pushes** — branch, open a PR, let CI run. Squash-merge is the norm.
+- **Tests ride along** — a behavior change without a test needs a stated reason.
+- **Claims need evidence** — if a README or doc states a number, it must be reproducible from the repo or cited. This is a firm house rule.
+
+## Evaluation-frozen repositories
+
+Repositories under active government evaluation say so in their READMEs (currently the AEGIS program repos). During an evaluation window they **accept issues but not external PRs**, and their names, URLs, and descriptions are frozen. Security reports are always welcome — see [SECURITY.md](SECURITY.md).
+
+## Questions and contact
+
+- Bugs and feature requests → the repo's issue templates
+- Security → [SECURITY.md](SECURITY.md)
+- Everything else → [info@577industries.com](mailto:info@577industries.com)

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,16 @@
+<!-- Thanks for contributing. Keep it evidence-first. -->
+
+## What
+
+<!-- One or two sentences: what changes and why. -->
+
+## Evidence
+
+<!-- How do we know it works? Test output, reproduction steps, before/after. -->
+
+## Checklist
+
+- [ ] Conventional-commit title (`feat:`, `fix:`, `docs:`, …)
+- [ ] Tests added/updated, or a stated reason why not
+- [ ] Docs/README updated if behavior or claims changed
+- [ ] No numbers stated without a reproducible source

SECURITY.md

@@ -0,0 +1,39 @@
+# Security Policy
+
+577 Industries builds systems for missions where being wrong is expensive. We treat security reports the same way we treat our own evidence: seriously, promptly, and with attribution.
+
+## Reporting a vulnerability
+
+- **Email**: [security@577industries.com](mailto:security@577industries.com)
+- Or use GitHub's **Report a vulnerability** (private advisory) on the affected repository.
+
+Please include: the repository and commit/release affected, reproduction steps or a proof of concept, and the impact as you understand it. Encrypted mail is fine — ask us for a key in a first plaintext message if you need one.
+
+## Scope
+
+All public repositories under the [`577Industries`](https://github.com/577Industries) organization. For anything touching the commercial FORGE OS platform (577industries.com), the same address applies.
+
+## What to expect (coordinated disclosure)
+
+| Stage | Our commitment |
+|---|---|
+| Acknowledgement | Within **3 business days** |
+| Triage + severity assessment | Within **10 business days** |
+| Fix or documented mitigation | Target **90 days** from acknowledgement; we will tell you if we need longer and why |
+| Credit | Public credit in the release notes / advisory unless you ask otherwise |
+
+We ask that you give us the 90-day window before public disclosure, and that you avoid accessing data that isn't yours, degrading service, or pivoting beyond the minimum needed to demonstrate the issue.
+
+## Safe harbor
+
+Good-faith security research conducted within this policy is authorized. We will not pursue legal action for research that respects the scope and disclosure window above. This safe harbor does not extend to social engineering, physical attacks, or testing systems we do not control.
+
+## Out of scope
+
+- Volumetric denial of service
+- Findings that require a compromised developer machine or stolen credentials as a precondition
+- Reports generated by automated scanners without a demonstrated impact
+
+## Evaluation-frozen repositories
+
+Some repositories are under active government evaluation (noted in their READMEs). Security reports on them are welcome and handled under this same policy — but fixes may land as advisories first, with code changes batched after the evaluation window, to preserve artifact stability.

brand/.gitignore

@@ -0,0 +1 @@
+node_modules/