Governance Documents

ProtoML is not limited to lightweight notes. It also supports more controlled documents with metadata, approvals, references, and lifecycle tracking.

Core governance metadata

Approval and signature structures

@signatures
=lead:Jane Doe,Project Lead,18.04.2026,Signed digitally

@approvals
=security:Security Review,approved,Jane Doe,18.04.2026,Reviewed and accepted

These let you separate reusable governance data from the final meeting or document narrative.

Embedding governance elements in the reader-facing document

@@signature=lead
@@approval=security
@@ref=meta:record_id

Detached signatures for governance files

protoparser sign pml "./governance/release-approval.pml" "./keys/alice-private.pem" "Alice" alice-main
protoparser verify pml "./governance/release-approval.pml" -trustRegistry="./authors-registry"

Detached file signatures complement the in-document governance blocks. They help prove the integrity and authorship of the whole .pml file without replacing semantic fields such as @signatures, @approvals, or review metadata.

Supporting sections

Why governance metadata matters

Once documents are reviewed, approved, versioned, or periodically revisited, their lifecycle becomes just as important as their prose. ProtoML's governance fields help keep that lifecycle explicit and machine-readable.

Recommended directory workflow

  1. Standardize required metadata for the document class
  2. Keep signatures and approvals in dedicated blocks
  3. Use stable @record_id values
  4. Run protoparser register "<dir>" statistics across the collection
  5. Review overdue or incomplete documents using register output

Good use cases

Related guides