docs(governance): add SIG overlay, MAINTAINERS.md, and continuity rules

.cspell.json

@@ -77,7 +77,14 @@
     "whiteboarding",
     "ˈpræksɪs",
     "πρᾶξις",
-    "agentic"
+    "agentic",
+    "chaosdinosaur",
+    "katriendg",
+    "agreaves",
+    "bindsi",
+    "rezatno",
+    "Msirh",
+    "Risner"
   ],
   "reporters": [
     "default",

.github/CODEOWNERS

@@ -10,8 +10,10 @@
 # Default owner for all files (fallback)
 * @microsoft/edge-ai-core-dev
 
-# Self-protection: CODEOWNERS file changes require core team approval
+# Self-protection: governance files require core team approval
 /.github/CODEOWNERS @microsoft/edge-ai-core-dev
+/GOVERNANCE.md @microsoft/edge-ai-core-dev
+/.github/MAINTAINERS.md @microsoft/edge-ai-core-dev
 
 # GitHub configuration (workflows, templates, instructions)
 /.github/ @microsoft/edge-ai-core-dev
@@ -24,3 +26,43 @@
 
 # Documentation
 /docs/ @microsoft/edge-ai-core-dev
+
+# ---------------------------------------------------------------------------
+# SIG-scoped ownership (commented stubs)
+#
+# The following per-SIG entries are commented out until GitHub Teams
+# `@microsoft/hve-core-sig-<id>` are provisioned. Uncomment one entry per SIG
+# when its team exists; see `docs/community/sigs/<sig-id>/CHARTER.md`.
+# ---------------------------------------------------------------------------
+
+# Engineering — build, scripts, packaging, CI, intake/triage
+# /scripts/                                     @microsoft/hve-core-sig-engineering
+# /extension/                                   @microsoft/hve-core-sig-engineering
+# /.github/workflows/                           @microsoft/hve-core-sig-engineering
+# /.github/instructions/ado/                    @microsoft/hve-core-sig-engineering
+# /.github/instructions/github/                 @microsoft/hve-core-sig-engineering
+# /.github/instructions/jira/                   @microsoft/hve-core-sig-engineering
+#
+# Emerging AI — experimental incubation surface
+# /.github/agents/experimental/                 @microsoft/hve-core-sig-emerging-ai
+# /.github/skills/experimental/                 @microsoft/hve-core-sig-emerging-ai
+# /collections/experimental.collection.*        @microsoft/hve-core-sig-emerging-ai
+#
+# Standards — coding standards, prompt-builder, doc IA
+# /.github/instructions/coding-standards/       @microsoft/hve-core-sig-standards
+# /.github/instructions/hve-core/               @microsoft/hve-core-sig-standards
+# /docs/contributing/                           @microsoft/hve-core-sig-standards
+# /docs/templates/                              @microsoft/hve-core-sig-standards
+#
+# Security — review, threat modeling, supply chain, CI hardening
+# (overrides Engineering for security-scoped paths via later-match-wins)
+# /.github/instructions/security/               @microsoft/hve-core-sig-security
+# /.github/skills/security/                     @microsoft/hve-core-sig-security
+# /scripts/security/                            @microsoft/hve-core-sig-security
+# /scripts/linting/                             @microsoft/hve-core-sig-security
+#
+# RAI — responsible AI planning
+# /.github/instructions/rai-planning/           @microsoft/hve-core-sig-rai
+#
+# Data Science — DS collection and DS-scoped artifacts
+# /collections/data-science.collection.*        @microsoft/hve-core-sig-data-science

.github/MAINTAINERS.md

@@ -0,0 +1,20 @@
+---
+title: Maintainers
+description: Current maintainers of microsoft/hve-core including pro tem assignments
+---
+
+This file is the canonical roster of `microsoft/hve-core` maintainers. The Maintainer Continuity and Quorum rules in [GOVERNANCE.md](../GOVERNANCE.md) govern additions, leaves of absence, and pro tem assignments.
+
+| Name              | Handle           | Role                | Notes                                           |
+|-------------------|------------------|---------------------|-------------------------------------------------|
+| Bill Berry        | @WilliamBerryiii | Maintainer          | Project lead                                    |
+| Katrien De Graeve | @katriendg       | Project lead          |                                                 |
+| Allen Greaves     | @agreaves-ms     | Project lead (on LOA) | Seat backfilled pro tem                         |
+| Chris Risner      | @ChrisRisner     | Maintainer          | Standards & Practices lead                      |
+| Emmeline Hoops    | @chaosdinosaur   | Maintainer Pro Tem  | Promoted 2026-04-25; backfills @agreaves-ms LOA |
+
+Last updated: 2026-04-25.
+
+---
+
+🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.

GOVERNANCE.md

@@ -2,15 +2,15 @@
 title: Governance
 description: Project governance model, roles, decision-making processes, and contribution authority for HVE Core
 author: HVE Core Team
-ms.date: 2026-02-07
+ms.date: 2026-04-25
 ms.topic: reference
 keywords:
   - governance
   - decision-making
   - roles
   - maintainers
   - contributors
-estimated_reading_time: 5
+estimated_reading_time: 8
 ---
 
 HVE Core uses a liberal contribution model where active contributors are recognized for current work. Microsoft maintains stewardship of the project while welcoming community contributions and leadership.
@@ -28,14 +28,14 @@ This project operates under a corporate-sponsored maintainer model:
 
 The following matrix summarizes capabilities by role:
 
-| Capability             | Maintainer | Triage | Contributor |
-|:-----------------------|:----------:|:------:|:-----------:|
-| Code review            |     ✅      |   ✅    |      ✅      |
-| Merge pull requests    |     ✅      |   ❌    |      ❌      |
-| Release management     |     ✅      |   ❌    |      ❌      |
-| Architecture decisions |     ✅      | Advise |   Propose   |
-| Issue triage           |     ✅      |   ✅    |      ❌      |
-| Label management       |     ✅      |   ✅    |      ❌      |
+| Capability             | Maintainer | SIG Chair | Triage | Contributor |
+|:-----------------------|:----------:|:---------:|:------:|:-----------:|
+| Code review            |     ✅      |  Advise   |   ✅    |      ✅      |
+| Merge pull requests    |     ✅      |  Advise   |   ❌    |      ❌      |
+| Release management     |     ✅      |     ❌     |   ❌    |      ❌      |
+| Architecture decisions |     ✅      |  Advise   | Advise |   Propose   |
+| Issue triage           |     ✅      |  Advise   |   ✅    |      ❌      |
+| Label management       |     ✅      |     ❌     |   ✅    |      ❌      |
 
 ### Maintainers
 
@@ -48,7 +48,34 @@ Maintainers guide project direction, manage releases, and resolve conflicts.
 | Community health    | Enforce code of conduct and foster inclusive participation  |
 | Access management   | Grant and revoke repository permissions                     |
 
-Current maintainers are members of the [@microsoft/edge-ai-core-dev](https://github.com/orgs/microsoft/teams/edge-ai-core-dev) team.
+The current maintainer roster is published in [.github/MAINTAINERS.md](.github/MAINTAINERS.md). Membership in the [@microsoft/edge-ai-core-dev](https://github.com/orgs/microsoft/teams/edge-ai-core-dev) team backs repository permissions.
+
+#### Maintainer Continuity and Quorum
+
+The active maintainer roster maintains a minimum of three members. Maintainer status is
+earned through sustained contribution and is added as the bar described in Role
+Progression is met; there is no upper cap on the number of maintainers.
+
+If a maintainer takes a Leave of Absence (LOA), is otherwise unable to serve, or the
+active roster would drop below three, the remaining maintainers vote under the
+Governance-tier decision rules (consensus + one-week comment window) to promote a
+contributor to **Maintainer Pro Tem**.
+
+A Maintainer Pro Tem holds full maintainer authority and serves until the earlier of:
+
+1. Three months elapsed since promotion, or
+2. The LOA maintainer returning to active service.
+
+At the end of the pro tem term, the pro tem either steps down, is reaffirmed as a
+permanent maintainer under the standard Role Progression rules if their contribution
+record qualifies, or, by re-vote of the remaining maintainers, has the pro tem term
+extended for one additional three-month period if the original LOA continues.
+
+Reaffirmation requires an explicit vote of the remaining maintainers under
+Governance-tier rules. The vote process and discussion are conducted privately; the
+**outcome** (promotion confirmed, pro tem ended, or term extended) is announced
+publicly in the `Maintainers` GitHub Discussions category and reflected in
+`MAINTAINERS.md`.
 
 ### Triage Contributors
 
@@ -71,6 +98,47 @@ Contributors improve the project through code, documentation, and community enga
 | Issue reporting         | Report bugs with reproduction steps and suggest enhancements |
 | Community participation | Engage in discussions and help other users                   |
 
+## Special Interest Groups
+
+A Special Interest Group (SIG) is an artifact-owning team that takes responsibility for a defined surface of the repository (directories, collections, and instructional content). Each SIG operates under a charter and is attached to [.github/CODEOWNERS](.github/CODEOWNERS) once its GitHub Team is provisioned.
+
+| SIG                                                                 | Owned Surface                                                                                                              |
+|:--------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------|
+| [SIG Engineering](docs/community/sigs/sig-engineering/CHARTER.md)   | Build, scripts, packaging, plugin generation, CI workflows, and backlog/intake/triage instruction surface.                 |
+| [SIG Standards](docs/community/sigs/sig-standards/CHARTER.md)       | Coding standards, prompt-builder standards, agent/prompt/instruction information architecture, and documentation style.    |
+| [SIG Security](docs/community/sigs/sig-security/CHARTER.md)         | Security review, threat modeling, OWASP skills, supply-chain security, CI hardening, dependency pinning, and scorecards.   |
+| [SIG RAI](docs/community/sigs/sig-rai/CHARTER.md)                   | Responsible AI planning artifacts and review rubric.                                                                       |
+| [SIG Data Science](docs/community/sigs/sig-data-science/CHARTER.md) | Data Science collection, notebook and Python skill conventions, and data-handling guidance.                                |
+| [SIG Emerging AI](docs/community/sigs/sig-emerging-ai/CHARTER.md)   | Experimental agents, prompts, skills, and collections (incubation surface that promotes proven patterns to receiving SIG). |
+
+Full charters live under [docs/community/sigs/](docs/community/sigs/README.md).
+
+### Chair Recruitment
+
+SIG chairs are recruited in two phases. Phase 0 seeds chairs internally from the active maintainer pool to bootstrap each SIG. Phase 1 opens a public call inviting non-maintainer contributors who have demonstrated sustained contribution to the owned surface.
+
+Eligibility:
+
+* Candidate is not a current maintainer.
+* Candidate has demonstrated prior contribution to the SIG's owned surface (code, review, documentation, or triage).
+* Candidate declares any conflicts of interest in the charter pull request.
+
+Terms and onboarding:
+
+* Chair term: 12 months, renewable once for a maximum of 24 consecutive months.
+* 6-month cooldown before a former chair may be re-nominated for the same SIG.
+* Onboarding: (1) charter PR opened, (2) COI declaration recorded, (3) chair listed in `MAINTAINERS.md` and the SIG charter, (4) repository team membership granted, (5) public announcement in the `Maintainers` GitHub Discussions category.
+
+Removal:
+
+* Voluntary step-down at any time.
+* Inactivity removal after 90 days of no SIG activity.
+* For-cause removal by Governance-tier vote of the remaining maintainers.
+
+### Working Groups (Deferred)
+
+Working Groups (WGs) may be added through a future amendment to this document. The structural charter template, sponsoring-SIG mechanic, and chair-eligibility rules will mirror those defined for SIGs above.
+
 ## Decision-Making Process
 
 Decisions follow a tiered model based on impact and reversibility.
@@ -106,6 +174,20 @@ Modifications to this governance document or project policies:
 * Require consensus among active maintainers
 * Allow one-week comment period for community input
 
+### Public Activity
+
+All SIG activity (design proposals, decision logs, scope debates, and routine
+deliberation) SHALL occur in public channels (GitHub Discussions, public issues,
+public PRs) wherever possible. Private deliberation is permitted only for:
+
+1. Security disclosures handled under `SECURITY.md`,
+2. Personnel matters (e.g., maintainer pro tem and reaffirmation votes), and
+3. Pre-publication coordination with Microsoft stewardship.
+
+For private deliberations, the resulting **decision** is published in the appropriate
+public channel (Discussions category, `MAINTAINERS.md`, or `GOVERNANCE.md` amendment)
+even when the deliberation itself remains private.
+
 ## Role Progression
 
 Contributors advance through demonstrated commitment and quality work.

docs/community/sigs/README.md

@@ -0,0 +1,28 @@
+---
+title: Special Interest Groups
+description: Index of artifact-owning SIGs in microsoft/hve-core with links to each charter
+ms.topic: overview
+ms.date: 2026-04-25
+author: HVE Core Maintainers
+---
+
+A Special Interest Group (SIG) is an artifact-owning team in microsoft/hve-core that takes responsibility for a defined surface of the repository (directories, collections, and instructional content). Each SIG operates under a charter, will be attached to [.github/CODEOWNERS](https://github.com/microsoft/hve-core/blob/main/.github/CODEOWNERS) once its GitHub Team is provisioned, and is led by chairs recruited under the Chair Recruitment Plan defined in [GOVERNANCE.md](https://github.com/microsoft/hve-core/blob/main/GOVERNANCE.md).
+
+## SIGs
+
+| SIG                                             | Owned Surface                                                                                                                  | Charter                                |
+|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|
+| [SIG Engineering](sig-engineering/CHARTER.md)   | Build, scripts, packaging, plugin generation, CI workflows, and backlog/intake/triage instruction surface.                     | [Charter](sig-engineering/CHARTER.md)  |
+| [SIG Standards](sig-standards/CHARTER.md)       | Coding standards, prompt-builder standards, agent/prompt/instruction information architecture, and documentation style.        | [Charter](sig-standards/CHARTER.md)    |
+| [SIG Security](sig-security/CHARTER.md)         | Security review, threat modeling, OWASP skills, supply-chain security, CI hardening, dependency pinning, and scorecards.       | [Charter](sig-security/CHARTER.md)     |
+| [SIG RAI](sig-rai/CHARTER.md)                   | Responsible AI planning artifacts and review rubric.                                                                           | [Charter](sig-rai/CHARTER.md)          |
+| [SIG Data Science](sig-data-science/CHARTER.md) | Data Science collection, notebook and Python skill conventions, and data-handling guidance.                                    | [Charter](sig-data-science/CHARTER.md) |
+| [SIG Emerging AI](sig-emerging-ai/CHARTER.md)   | Experimental agents, prompts, skills, and collections (incubation surface that promotes proven patterns to the receiving SIG). | [Charter](sig-emerging-ai/CHARTER.md)  |
+
+## Working Groups
+
+Working Groups (WGs) are deferred. A future amendment will introduce WGs; see the forward-reference in [GOVERNANCE.md](https://github.com/microsoft/hve-core/blob/main/GOVERNANCE.md).
+
+---
+
+🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.