@pieai/pro-gov 0.7.2 → 0.7.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -10
- package/assets/docs/reference/adoption/adoption-playbook.md +8 -8
- package/assets/docs/reference/adoption/migration-v1.0.md +3 -3
- package/assets/docs/reference/adoption/recommended-agent-tooling.md +16 -5
- package/assets/integrations/.gitkeep +1 -0
- package/assets/portfolio-dashboard/app.js +5 -5
- package/assets/profiles/engineering-runtime/manifest.yml +0 -2
- package/assets/profiles/engineering-runtime/profile.md +5 -4
- package/assets/public-agent-assets/registry.json +1 -1
- package/assets/starter/.github/workflows/docs-check.yml +11 -1
- package/assets/starter/docs/governance/agents-routing/engineering-runtime-v1.1.md +19 -1
- package/assets/starter/docs/governance/boundary.md +3 -4
- package/assets/starter/docs/governance/doc-agent-rules.md +2 -2
- package/assets/starter/docs/governance/doc-types.md +2 -2
- package/assets/starter/docs/governance/ssot-v1.1.md +3 -5
- package/assets/starter/docs/governance/templates/adr.md +24 -2
- package/assets/starter/docs/reference/documentation-map.md +1 -1
- package/dist/cli.js +381 -85
- package/package.json +2 -2
- package/assets/integrations/mattpocock-skills.md +0 -42
|
@@ -8,8 +8,6 @@ required:
|
|
|
8
8
|
source: external shared-rule SSOT
|
|
9
9
|
agents_routing: docs/governance/agents-routing/engineering-runtime-v1.1.md
|
|
10
10
|
current_work: docs/reference/execution/current-work.md
|
|
11
|
-
optional:
|
|
12
|
-
mattpocock_skills: integrations/mattpocock-skills.md
|
|
13
11
|
project_local_required:
|
|
14
12
|
- docs/policy/best-practice-for-this-project.md
|
|
15
13
|
- AGENTS.md lane summary
|
|
@@ -9,7 +9,6 @@ Use for code-heavy projects: apps, games, runtimes, services, browser products,
|
|
|
9
9
|
- `docs/governance/ssot-v1.1.md`
|
|
10
10
|
- external AI-in-the-Loop policy linked by target projects under `docs/policy/shared-rules/ai-in-the-loop.md`
|
|
11
11
|
- `docs/governance/agents-routing/engineering-runtime-v1.1.md`
|
|
12
|
-
- `integrations/mattpocock-skills.md`
|
|
13
12
|
- starter `docs/governance/` and `docs/policy/` templates
|
|
14
13
|
|
|
15
14
|
## Requires Project-Local Rules
|
|
@@ -28,7 +27,6 @@ Each project must define:
|
|
|
28
27
|
- stack-specific rules
|
|
29
28
|
- game/app-specific lane wording
|
|
30
29
|
- external workflow plugin bodies
|
|
31
|
-
- mattpocock/skills body
|
|
32
30
|
|
|
33
31
|
## Automation Boundary
|
|
34
32
|
|
|
@@ -42,5 +40,8 @@ their required governance commands remain present.
|
|
|
42
40
|
|
|
43
41
|
For non-trivial engineering work, run `pro-gov learn recall --query "<task
|
|
44
42
|
summary>"` before changing files so existing `docs/reference/learnings/**` and
|
|
45
|
-
`CONCEPTS.md` lessons can shape the work. After verified
|
|
46
|
-
`capture-learning`
|
|
43
|
+
`CONCEPTS.md` lessons can shape the work. After completed, verified, non-trivial
|
|
44
|
+
work, let `capture-learning` make a visible soft closeout decision. Capture only
|
|
45
|
+
when a non-obvious reusable lesson exists; a skip is valid and no exit hook is
|
|
46
|
+
required. Resolve the CLI through the project (`pnpm pro-gov` in this source
|
|
47
|
+
repository), not by assuming a global `pro-gov` binary.
|
|
@@ -24,12 +24,22 @@ on:
|
|
|
24
24
|
- "package.json"
|
|
25
25
|
- "pnpm-lock.yaml"
|
|
26
26
|
|
|
27
|
+
permissions:
|
|
28
|
+
contents: read
|
|
29
|
+
|
|
30
|
+
concurrency:
|
|
31
|
+
group: docs-check-${{ github.ref }}
|
|
32
|
+
cancel-in-progress: true
|
|
33
|
+
|
|
27
34
|
jobs:
|
|
28
35
|
doc-gov:
|
|
29
36
|
name: doc-gov
|
|
30
|
-
runs-on: ubuntu-
|
|
37
|
+
runs-on: ubuntu-slim
|
|
38
|
+
timeout-minutes: 10
|
|
31
39
|
steps:
|
|
32
40
|
- uses: actions/checkout@v7
|
|
41
|
+
with:
|
|
42
|
+
persist-credentials: false
|
|
33
43
|
|
|
34
44
|
- uses: pnpm/action-setup@v6
|
|
35
45
|
with:
|
|
@@ -6,7 +6,7 @@ status: stable
|
|
|
6
6
|
canonical: true
|
|
7
7
|
owner: human
|
|
8
8
|
created: 2026-07-13
|
|
9
|
-
last_reviewed: 2026-07-
|
|
9
|
+
last_reviewed: 2026-07-16
|
|
10
10
|
domain: agents-routing
|
|
11
11
|
tags:
|
|
12
12
|
- agents-routing
|
|
@@ -41,6 +41,24 @@ flowchart TD
|
|
|
41
41
|
|
|
42
42
|
Use this router only to pick depth and workflow. Do not use it as a project roadmap.
|
|
43
43
|
|
|
44
|
+
## Local-First Verification And Release Boundary
|
|
45
|
+
|
|
46
|
+
- Before pushing, run the smallest project-local verification ladder that fully
|
|
47
|
+
covers the changed surface. Do not use hosted CI as a remote debugging loop.
|
|
48
|
+
- If a relevant local gate fails, fix it locally before pushing. If it cannot run
|
|
49
|
+
locally, record the exact blocker and do not push repeated guesses.
|
|
50
|
+
- Automatic hosted CI is a short independent smoke check. Keep it path-scoped,
|
|
51
|
+
cached, least-privileged, time-bounded, and configured to cancel stale runs.
|
|
52
|
+
- Expensive browser, performance, packaging, staging, publishing, and deployment
|
|
53
|
+
lanes are local or manually triggered release evidence unless a project records
|
|
54
|
+
a specific exception.
|
|
55
|
+
- Implementation and release are separate phases. The same solo developer or AI
|
|
56
|
+
may perform both, but a product task does not silently authorize publishing a
|
|
57
|
+
shared package or mutating staging/production.
|
|
58
|
+
|
|
59
|
+
This is a behavior contract, not a requirement to add another hook, CI service,
|
|
60
|
+
or local tool. Reuse the project's existing scripts and verification ladder.
|
|
61
|
+
|
|
44
62
|
## Project-Local Lane Profile
|
|
45
63
|
|
|
46
64
|
Every engineering project must define its own lane profile in `AGENTS.md` or `docs/policy/best-practice-for-this-project.md`.
|
|
@@ -57,7 +57,7 @@ project-specific AI development habits live.
|
|
|
57
57
|
| Project AI development practices | `docs/policy/best-practice-for-this-project.md` |
|
|
58
58
|
| Current work index | `docs/reference/execution/current-work.md` |
|
|
59
59
|
| Product or world truth | `docs/canon/` |
|
|
60
|
-
| Durable decisions | `docs/adr/`,
|
|
60
|
+
| Durable decisions | `docs/adr/`, governed decision records |
|
|
61
61
|
| Active implementation work | `docs/plans/active/` |
|
|
62
62
|
| Completed proof records | `docs/plans/completed/` |
|
|
63
63
|
| Reusable project learnings | `docs/reference/learnings/**` as governed reference documents |
|
|
@@ -78,6 +78,5 @@ product packages, workbenches, prompt libraries, source folders, or asset
|
|
|
78
78
|
folders can be product artifacts. Keep those files where the product package
|
|
79
79
|
expects them unless a project explicitly opts them into doc-gov.
|
|
80
80
|
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
do not copy ADRs into a second PGS decision directory.
|
|
81
|
+
Decision records under `docs/adr/**` are governed documents. Do not copy them
|
|
82
|
+
into a second PGS decision directory.
|
|
@@ -58,8 +58,8 @@ draft -> active -> completed -> stable -> superseded -> archived
|
|
|
58
58
|
|
|
59
59
|
`completed` is for finished execution records or specs that should no longer appear in active folders.
|
|
60
60
|
|
|
61
|
-
Durable decisions belong only in `docs/adr/**`. They use
|
|
62
|
-
|
|
61
|
+
Durable decisions belong only in `docs/adr/**`. They use the governed decision
|
|
62
|
+
frontmatter and decision lifecycle; do not duplicate them elsewhere.
|
|
63
63
|
|
|
64
64
|
## Upstream Rule
|
|
65
65
|
|
|
@@ -42,5 +42,5 @@ Normal documents use:
|
|
|
42
42
|
draft -> active -> completed -> stable -> superseded -> archived
|
|
43
43
|
```
|
|
44
44
|
|
|
45
|
-
Durable decisions use the
|
|
46
|
-
|
|
45
|
+
Durable decisions use the governed `docs/adr/**` surface and the decision
|
|
46
|
+
lifecycle. Do not duplicate them in another decision folder.
|
|
@@ -54,12 +54,10 @@ Markdown.
|
|
|
54
54
|
|
|
55
55
|
Extra governed roots are allowed only when a project explicitly opts in.
|
|
56
56
|
|
|
57
|
-
|
|
58
|
-
|
|
57
|
+
External and optional-tool artifacts are explicitly outside the default Doc Gov
|
|
58
|
+
schema:
|
|
59
59
|
|
|
60
60
|
- `CONTEXT.md` and `CONTEXT-MAP.md`
|
|
61
|
-
- `docs/adr/**`
|
|
62
|
-
- `docs/agents/**`
|
|
63
61
|
- `docs/brainstorms/**`
|
|
64
62
|
- `docs/pulse-reports/**`
|
|
65
63
|
|
|
@@ -161,7 +159,7 @@ works for governed docs:
|
|
|
161
159
|
| Agents-routing rules | `docs/governance/agents-routing/` |
|
|
162
160
|
| Doc-system rules, templates, and manifest | `docs/governance/` |
|
|
163
161
|
| Project AI/development policy | `docs/policy/` |
|
|
164
|
-
| Durable decisions | `docs/adr/`,
|
|
162
|
+
| Durable decisions | `docs/adr/`, governed decision records |
|
|
165
163
|
| Product or feature requirement | `docs/specs/` |
|
|
166
164
|
| Step-by-step implementation work | `docs/plans/` |
|
|
167
165
|
| Reusable learning records | `docs/reference/learnings/**`, governed as `reference` documents and recalled on demand |
|
|
@@ -1,3 +1,25 @@
|
|
|
1
|
-
|
|
1
|
+
---
|
|
2
|
+
id: REPLACE-ME
|
|
3
|
+
title: Replace Me
|
|
4
|
+
type: decision
|
|
5
|
+
status: proposed
|
|
6
|
+
canonical: true
|
|
7
|
+
owner: human
|
|
8
|
+
created: YYYY-MM-DD
|
|
9
|
+
last_reviewed: YYYY-MM-DD
|
|
10
|
+
domain: meta
|
|
11
|
+
tags:
|
|
12
|
+
- replace-me
|
|
13
|
+
pinned: false
|
|
14
|
+
related: []
|
|
15
|
+
supersedes: []
|
|
16
|
+
superseded_by: null
|
|
17
|
+
---
|
|
2
18
|
|
|
3
|
-
|
|
19
|
+
# REPLACE-ME: Replace Me
|
|
20
|
+
|
|
21
|
+
## Context
|
|
22
|
+
|
|
23
|
+
## Decision
|
|
24
|
+
|
|
25
|
+
## Consequences
|
|
@@ -35,7 +35,7 @@ Use `AGENTS.md` for startup reading. It should point agents to:
|
|
|
35
35
|
| Area | Purpose |
|
|
36
36
|
| --- | --- |
|
|
37
37
|
| `docs/policy/` | Project policy and AI development rules |
|
|
38
|
-
| `docs/adr/` |
|
|
38
|
+
| `docs/adr/` | Governed durable decision records |
|
|
39
39
|
| `docs/specs/active/` | Active requirements |
|
|
40
40
|
| `docs/specs/completed/` | Completed specs |
|
|
41
41
|
| `docs/plans/active/` | Active implementation plans |
|