[GH-05] Rewrite organization profile around one product and repository maturity

[jaavid]

Background

CoreLink is managed as one product across multiple implementation boundaries. This work is owned by .github under EPIC-01.

Problem

The organization needs a verified, consistently maintained maturity baseline so public organization claims do not outrun repository/release evidence.

Goal

Keep the organization profile aligned with CoreLink as one product and make repository maturity/status authoritative, reviewable, and evidence-backed.

Parent

• Primary Product Epic: EPIC-01
• Backlog ID: GH-05

Scope

• Maintain the organization profile and repository maturity inventory in .github.
• Reconcile affected product claims, ownership, security, release, documentation, and repository maturity.
• Retain acceptance evidence for the Foundation gate.

Out of Scope

• Runtime feature implementation in this Issue.
• Duplicating the product roadmap in repository README files.
• Presenting scaffolds or planned capability as a supported release.

Acceptance Criteria

• The organization profile and repository maturity inventory are implemented in their authoritative location.
• Affected repositories link to the source of truth instead of copying it.
• Ownership, review cadence, and exception paths are explicit.
• Security, license, privacy, and release impacts are addressed where applicable.
• The result is validated against a real repository workflow.
• Acceptance evidence is fully reconciled with the parent Epic before closure.

Implementation Evidence

• PR #8 merged on 2026-08-11 as ee8005d2732cbe2d0f4682cf826f73dc3d9eeb98.
• Repository maturity inventory reconciles implemented, prerelease/Alpha, Scaffold, and Planned states without treating repository visibility as release status.
• Community Health CI was re-run successfully before merge.
• The unavailable CoreLinkPlatform/examples entry point was removed from the organization profile.

Technical Notes

Product maturity claims must distinguish Scaffold, Experimental, Alpha, Beta, Stable, Deprecated, and Planned. Merge completion is implementation evidence; Issue closure still requires the remaining organization-link/ownership/policy and parent-Epic acceptance checks above.

Dependencies

• Prerequisite completed: Repository maturity inventory was delivered and validated in PR Align the organization profile with repository maturity #8.
• Active blockers: No implementation blocker is recorded in this Issue body; remaining work is Foundation acceptance/reconciliation.
• Blocks: EPIC-01 Foundation governance acceptance.
• Cross-repository: Link concrete affected Issues; do not duplicate implementation.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Docs
• Priority: P1
• Product milestone: Foundation
• Domains: governance, docs
• Area: documentation
• Complexity: S
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:docs

Definition of Done

• Acceptance criteria demonstrated.
• Implementation workflow validation passed.
• Organization and repository links are reconciled.
• Security and policy implications are reviewed.
• Documentation and release notes are updated where applicable.
• Pull request/configuration change is linked.

[jaavid]

Implementation / acceptance update — 2026-08-08

PR #8 is the current implementation candidate for GH-5 and appears to cover the repository-maturity inventory, organization-profile rewrite, and Community Health validation guardrails required by this issue.

Its PR description still says GitHub Actions evidence is pending due to the current Actions incident. That blocker is now stale at the organization level: hosted Actions have been running again in CoreLink repositories since Aug 1, with successful workflow evidence recorded elsewhere in the organization. Cross-repository success is not acceptance evidence for this repository, so the correct next step is to run/retain .github's own Community Health CI evidence on the PR/current head and then evaluate GH-5 against its acceptance criteria.

Do not close GH-5 solely because #8 is mergeable or because Actions work in another repository. Close only after this repository's evidence is retained and the EPIC-01 parent record is reconciled.

[jaavid]

Governance evidence update (2026-08-11): PR #8 is now merged as ee8005d2732cbe2d0f4682cf826f73dc3d9eeb98. Community Health CI run 31123085815 was re-run after the earlier cancelled job; both profile-maturity and issue-forms completed successfully. This satisfies the implementation + repository-workflow validation portion of GH-5. Keep GH-5 open until the remaining acceptance items are explicitly reconciled: authoritative-link coverage across affected repositories, ownership/review/exception-path evidence, and parent EPIC-01 update/acceptance.