# [Product display name] project map

**Project ID:** `[stable-project-id]`
**View:** Observed / Proposed / Unconfirmed (identify mixed rows explicitly)
**Coordination repository:** `[repository key and actual location]`

## Scope and ownership

[Product outcome, owner if known, non-goals, and distinction from integrating products.]

## Repositories and responsibilities

| Key | Actual repository URL | Role and owner | Maintained docs / contracts | Release relationship | Evidence / open decision |
|---|---|---|---|---|---|
| core | [URL or unknown] | [responsibility] | [canonical path/version] | [independent/coordinated] | [observed/proposed/unconfirmed] |

Identify shared repositories once with an accountable owner and linked consumers. Local copies, worktrees and forks are relationships/locations, not automatically new products.

## Delivery boards

| Board | Actual URL or not created | Purpose and item scope | Authoritative fields / status | Owner / review or archival trigger |
|---|---|---|---|---|
| Delivery | [actual URL or not created] | [repo-owned tasks] | [execution status] | [known owner] |

Add a Roadmap, migration or portfolio board only for a distinct need. Additional table/board/roadmap views can use the same Project; do not claim custom fields synchronize across Projects without verified automation.

## Documentation authority

| Subject | Canonical repository and path | Update trigger |
|---|---|---|
| Product scope / cross-repo architecture | [coordination location] | [boundary/scope changes] |
| Repository implementation and operations | [member-repo docs] | [relevant change] |
| Public contract and compatible versions | [publishing owner] | [versioned interface change] |

## Local management and aliases

- Private checkout/worktree mapping: [local-only location, no private paths in a public map]
- Preserved legacy names and any proposed naming changes:
- Submodules, embedded source or local-path remotes needing explicit version ownership:

## Integration and release

- Coordinating issue/plan and member-repository tasks:
- Tested component version/commit set:
- Compatibility, rollout order and recovery for partial delivery:
- Unconfirmed relationships and the evidence needed to resolve them: