GCC Build OSv0
/api

Lock decision-logging practice (where, by whom, format)pmo.dec.decision_logging_practice_lock

P1 GCC

Summary

Lock the practice for capturing Steerco and Working Group decisions. After lock, every Steerco minute names the rapporteur and points at the durable decision log.

Rationale prompt skeleton

Rationale should reference the decision-logging-practice question and the Steerco constitution. Specify the rapporteur role and the SLA from meeting end to durable record.

Default options (2)

platform_decision_log Decisions logged directly in the GCC Build OS Decision Graph

Every Steerco decision is captured as a Decision node with rationale and Programme Memory Events at the moment it's made. Programme Lead is the rapporteur.

Pros
  • + Decisions are queryable, linkable, and trace through to downstream impact
  • + No tool sprawl; the platform is the source of truth
  • + Programme Memory works as designed
Cons
  • − Depends on platform availability and Programme Lead bandwidth
  • − Requires discipline to capture in real-time, not after the fact
minutes_then_log Decisions captured in meeting minutes, transcribed to Decision Graph within 24h

Programme Lead captures decisions in minutes during the meeting; PMO Analyst transcribes into Decision Graph within 24 hours.

Pros
  • + Lower in-meeting cognitive load
  • + Allows for post-meeting clarification before locking
Cons
  • − 24h gap creates re-litigation window
  • − Adds a second source of truth (minutes)

Default approval chain

  1. Admin
  2. ExecutiveViewer

Linked evidence questions (1)

id prompt workstream
pmo.q.decision_log_practice What is the practice for capturing decisions made at Steerco and Working Groups? Where are they recorded, who is accountable for the recording, and how are they referenced afterward? pmo.governance_forums