Skip to content

chore(standards): sync from AzureLocal/platform #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(standards): sync from AzureLocal/platform #44

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions standards/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ This repository follows the **org-wide AzureLocal standards** maintained on the
|----------|-----------|------------------|
| Documentation | [Documentation Standards](documentation) | [Full Reference](https://azurelocal.cloud/standards/documentation/documentation-standards) |
| Repository Management | [Repository Management Standard](repository-management) | [Full Reference](https://azurelocal.cloud/standards/repository-management/) |
| Project Management | [Project Management](project-management) | [HCS Base Standard](https://platform.hybridsolutions.cloud/standards/project-management/) |
| Scripting | [Scripting Standards](scripting) | [Full Reference](https://azurelocal.cloud/standards/scripting/scripting-standards) |
| Variables | [Variable Standards](variables) | [Full Reference](https://azurelocal.cloud/standards/variable-management/) |
| Naming Conventions | [Naming Conventions](naming) | [Full Reference](https://azurelocal.cloud/standards/documentation/naming-conventions) |
Expand Down
34 changes: 34 additions & 0 deletions standards/project-management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
title: Project Management
description: AzureLocal rules for tracker-authoritative planning and reusable PMO boards.
---

# Project Management

This page is the AzureLocal overlay for the HCS
[project-management standard](https://platform.hybridsolutions.cloud/standards/project-management/).
Only AzureLocal-specific differences are defined here.

## Authoritative source

GitHub Issues and the AzureLocal organization Project are the primary intake and work-tracking
surfaces. Issues may synchronize into HCS Azure DevOps under the existing split-source rules, but
operators author and update GitHub-native issue data in GitHub.

The reusable PMO board is a read-only snapshot of those issues. It MUST NOT store browser edits or
write changes back to GitHub. Every displayed item links to its authoritative issue.

## Scope selection

AzureLocal uses the per-repository project model unless `registry.yaml` explicitly assigns a
shared project. A board SHOULD represent one repository. A cross-repository portfolio board MAY
use the organization Project when its configuration names that scope explicitly.

## Publication

Generated snapshots stay under ignored `.artifacts/pmo/`. Scheduled automation publishes an
authenticated workflow artifact. Claude or Codex publication remains owner-only or
workspace-restricted unless the repository owner explicitly approves public access.

See also [Repository Management](repository-management.md) and the HCS
[work-item sync standard](https://platform.hybridsolutions.cloud/standards/work-item-sync/).
4 changes: 2 additions & 2 deletions standards/testing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ description: "MAPROOM fixtures, TRAILHEAD scenarios, and IIC canon — how Azure
Testing in AzureLocal is centralized. The frameworks, schemas, and canonical test data live in [`AzureLocal/platform/testing/`](https://github.com/AzureLocal/platform/tree/main/testing) and are consumed by every product repo. This standard defines **what each repo must test** and **which framework primitives it must use** — it does not re-describe the frameworks themselves (those have their own docs under [`docs/maproom/`](https://github.com/AzureLocal/platform/tree/main/docs/maproom) and [`docs/trailhead/`](https://github.com/AzureLocal/platform/tree/main/docs/trailhead) once Phase 2 ships).

!!! info "Phase status"
Phase 1 (this document) establishes the **standard**. Phase 2 ships the **framework** (`AzureLocal.Maproom` PowerShell module, fixture + IIC schemas, TRAILHEAD harness). Until Phase 2 lands, repos continue to reference [`azurelocal-S2DCartographer/tests/maproom/`](https://github.com/AzureLocal/azurelocal-S2DCartographer/tree/main/tests/maproom) as the interim canonical implementation.
Phase 1 (this document) establishes the **standard**. Phase 2 ships the **framework** (`AzureLocal.Maproom` PowerShell module, fixture + IIC schemas, TRAILHEAD harness). Until Phase 2 lands, repos continue to reference [`azurelocal-s2d-cartographer/tests/maproom/`](https://github.com/AzureLocal/azurelocal-s2d-cartographer/tree/main/tests/maproom) as the interim canonical implementation.

---

Expand Down Expand Up @@ -48,7 +48,7 @@ MAPROOM fixtures are JSON documents describing the **expected shape** of a targe

### Fixture schema

Fixtures MUST validate against [`platform/testing/maproom/schema/fixture.schema.json`](https://github.com/AzureLocal/platform/tree/main/testing/maproom/schema) (ships in Phase 2). Until then, use the schema derived from `azurelocal-S2DCartographer/tests/maproom/schema/` and expect to migrate on Phase 2 cutover.
Fixtures MUST validate against [`platform/testing/maproom/schema/fixture.schema.json`](https://github.com/AzureLocal/platform/tree/main/testing/maproom/schema) (ships in Phase 2). Until then, use the schema derived from `azurelocal-s2d-cartographer/tests/maproom/schema/` and expect to migrate on Phase 2 cutover.

### IIC canon as fixture source

Expand Down