Expand the organization profile into a maintained project directory

[cervantesh]

Maturity context

• Project maturity: developing (51/100)
• Dimension: product_clarity
• Priority: medium

Evidence

• PROFILE/README.md contains only a generic organization description and participation guidance
• The profile does not link https://t50.systems
• No flagship projects, maturity/status indicators, or maintainer contact path are listed

Scope

• Link the public T50 Systems website and explain the relationship between products, internal projects, and open-source tooling.
• List maintained public flagship repositories with one-line purpose, status, and audience.
• Add contribution, support, and security entry points without duplicating full policies.
• Define who reviews profile accuracy and how stale entries are removed.

Acceptance criteria

• The rendered organization profile links the canonical company website and each listed active public project.
• Every project entry includes purpose, intended user, and an explicit status signal.
• Support and security links route to the canonical organization policies.
• A documented quarterly or release-triggered profile review keeps the directory current.

Help wanted

Good documentation contribution; maintainers should choose which projects are flagship and approve status wording.

---

Generated from the repository maturity assessment dated 2026-07-11. Do not include credentials, customer data, or local-only files in public discussion.

[cervantesh]

Completed by PR #9. The merged governance change adds portable issue forms, private security reporting and response targets, CODEOWNERS/continuity policy, read-only adoption auditing, a maintained public project directory, and documented inheritance/override verification.