Workflow 5: Review A Governance Portfolio

After validating one signed board approval file, Lea now has a broader operational question: is the surrounding governance portfolio in good shape, or are there other documents that are overdue, incomplete, or missing metadata?

The scenario shift

This step is no longer mainly about one signer. It is about the health of a whole governance collection such as release approvals, procedures, onboarding records, and policy documents.

Run a register report across the directory

protoparser register "./governance" statistics
protoparser register "./governance" html

This gives Lea a governance-oriented portfolio view rather than a single-file trust result.

What Lea is looking for

documents missing @record_id, @author, @version, or @status
documents whose @review_date is due or overdue
documents whose @valid_until has expired
documents that still contain open tasks or unresolved follow-up work

Why this matters after trust validation

A file can be signed correctly and still be operationally weak if governance metadata is stale or missing. Trust answers "can I trust this artifact?", while register reporting helps answer "is the governance set being managed properly?"

Typical follow-up

If the portfolio report looks healthy, Release Operations can proceed confidently. If not, Lea may need a more practical release-facing workflow that combines governance, validation, and packaging checks for one concrete release package.

Continue with

That next step is covered in Workflow 6: Release Operations Without A Board Story.