stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
7503c19b8ffa7f2891e5e672f9cfbf7efa4e2efb
git.stella-ops.org/docs/governance/default-approval-protocol.md
StellaOps Bot 7503c19b8f Add determinism tests for verdict artifact generation and update SHA256 sums script 
- Implemented comprehensive tests for verdict artifact generation to ensure deterministic outputs across various scenarios, including identical inputs, parallel execution, and change ordering.
- Created helper methods for generating sample verdict inputs and computing canonical hashes.
- Added tests to validate the stability of canonical hashes, proof spine ordering, and summary statistics.
- Introduced a new PowerShell script to update SHA256 sums for files, ensuring accurate hash generation and file integrity checks.
2025-12-24 02:17:34 +02:00

2.6 KiB
Raw Blame History

Default Approval Protocol

Decision ID: GOV-APPROVAL-001 Status: APPROVED Effective Date: 2025-12-06

Purpose

This protocol establishes a default decision-making framework for tasks blocked on approvals, staffing decisions, or owner assignments. It enables autonomous progress while maintaining accountability.

48-Hour Silence Rule

Principle: Silence within 48 hours of a documented request constitutes implicit approval.

Scope

This rule applies to:

  • Schema approvals pending guild review
  • Design document sign-offs
  • Staffing/owner assignment requests
  • Contract freeze decisions
  • Migration approval gates

Exclusions

This rule does NOT apply to:

  • Security-critical decisions (key rotation, credential issuance)
  • Production deployment approvals
  • Customer-facing contract changes
  • License or legal decisions

Decision Artifact Pattern

When a decision is needed, create a Decision Contract document:

# <Topic> Decision Contract

**Decision ID:** DECISION-<ID>
**Status:** PENDING-APPROVAL (48h window starts: <timestamp>)
**Deadline:** <timestamp + 48h>
**Notify:** <guild-leads@stella-ops.org>

## Proposed Decision
<What is being decided>

## Rationale
<Why this is the recommended default>

## Impact
- Tasks unblocked: <count>
- Sprint files affected: <list>

## Reversibility
<How to override if the default is not acceptable>

After 48 hours without objection:

  1. Update Status: to DEFAULT-APPROVED
  2. Update dependent sprint files
  3. Record the decision in the relevant sprint file execution log (docs/implplan/SPRINT_*.md)

Owner Manifest Pattern

When a task is blocked on staffing/ownership:

# <Component> Owner Manifest

**Decision ID:** OWNER-<ID>
**Status:** ASSIGNED
**Effective Date:** <date>

## Assignment
<Component> is owned by <Guild/Team> for implementation purposes.

## Rationale
<Why this assignment makes sense>

## Scope
<What this owner is responsible for>

## Escalation Path
<Who to escalate to if blocked>

## Authority Granted
This manifest grants implementation authority to proceed with tasks
blocked on staffing.

Governance Log

All decisions made via this protocol MUST be logged in:

  • docs/governance/decisions-log.md (append-only)
  • Relevant sprint file execution logs

Escalation

If a decision is contested after default approval:

  1. Raise in next daily standup
  2. Escalate to steering committee if unresolved in 24h
  3. Decision may be reversed but work already done is preserved

References

  • Exceptions API entry point: docs/api/exceptions.md
  • Exception governance migration guide: docs/migration/exception-governance.md