Skip to content

SESSION_CHARTER.md

Latest commit

 

History

History
168 lines (119 loc) · 5.49 KB

SESSION_CHARTER.md

File metadata and controls

168 lines (119 loc) · 5.49 KB

Session Charter Template

Copy this file to start a new collaborative session. Fill in each section before work begins. All agents must review and sign the handshake before implementation starts.

Governance reference: Protocol Core | Human Governance | Conflict Resolution

1) Session metadata

Field Value
Session ID
Date
Project
Milestone
Risk tier

2) Agent roster

List every participant. Each agent must have a defined lane before implementation begins.

Role Agent Model/Provider Lane
Maintainer — Final authority, merge, lane assignment

3) Lane ownership

Each file has exactly one owner. If two agents might edit the same file, redesign the split. Lane changes require a logged maintainer decision in the WORKLOG. See Protocol Core, section 3.

Lane Owner Files/Scope
Shared (append-only) All agents WORKLOG.md

4) Shared contract

What interfaces, schemas, or contracts must be defined and tested before parallel implementation begins? See Protocol Core, invariant 2.

  • Contract location:
  • Contract owner:
  • Validation tests:
  • Status:

5) Governance settings

Setting Value
Decision mode
Objection window
Cross-review mode
Merge policy
Test policy

6) Approval gates

Define what actions each approval band covers for this session. See Human Governance for band definitions.

Band Scope
Auto
Notify + Delay
Approval Required

7) Conflict escalation

Configure the escalation ladder for this session. See Conflict Resolution for the full framework.

  • Level 1: Counter-recommendation with evidence
  • Level 2: Time-boxed rebuttal round (window: )
  • Level 3: Risk-minimizing default selection
  • Level 4: Maintainer adjudication
  • Maintainer tie-break condition:

8) Acceptance criteria

What must be true for this milestone to be considered complete?

9) Handshake acknowledgments

Each agent and the maintainer reviews this charter and signs below before implementation begins. Handshakes carry forward across protocol versions unless roles or lane assignments change.

Signing acknowledges the governance docs listed in the header: Protocol Core, Human Governance, and Conflict Resolution.

Signed: Role: Handshake status: Scope acknowledgment:

Notes:

Timestamp:

Signed: Role: Handshake status: Scope acknowledgment: Notes:

Timestamp:

Maintainer (Human)

Signed: Handshake status: Acknowledgment: Timestamp:

10) Session kickoff checklist

Run through this before any implementation begins. See Protocol Core, section 8.

  • Lane boundaries confirmed (section 3 above)
  • Shared contract exists with tests, or will be created first (section 4 above)
  • WORKLOG initialized with pinned status block (one line per agent)
  • Handoff format expectations confirmed (quick vs full thresholds)
  • Acceptance criteria confirmed (section 8 above)
  • All agents have signed the handshake (section 9 above)
  • Retro commitment acknowledged

11) Session close checklist

Run through this before declaring a session complete. See PRD-014 for the full closeout contract.

  • All agent unread mailbox counts are zero
  • WORKLOG status block updated and session entry posted
  • TURNFILE.yaml updated (locks released, tasks completed, agent status idle)
  • Session state snapshot written to chat log
  • Boot file archived and new boot file written
  • Git commits: promoted artifacts committed granularly (one commit per PRD, per tool, per structural change); remaining session work in a summary commit
  • Push to remote (only when maintainer directs)