Skip to content

test: break governance index (2)#4

Closed
marcusglee11 wants to merge 1 commit into
mainfrom
test/branch-protection-2
Closed

test: break governance index (2)#4
marcusglee11 wants to merge 1 commit into
mainfrom
test/branch-protection-2

Conversation

@marcusglee11

Copy link
Copy Markdown
Collaborator

Summary

Type of Change

  • Governance artefact update (content change to existing artefact)
  • New governance artefact (adds new canonical artefact)
  • Artefact index update (adds/removes/renames artefact references)
  • Infrastructure (validator, CI, templates)
  • Other (please describe)

Artefact IDs Affected

Checklist

  • Changes are scoped to docs/governance/ only
  • ARTEFACT_INDEX.json is updated if artefacts were added/renamed/removed
  • All paths in index are repo-root relative (docs/governance/...)
  • Local validator passes: python tools/validate_governance_index.py
  • Commit message follows pattern: GOV: <verb> <artefact-id(s)>

Reviewer Notes

@marcusglee11

Copy link
Copy Markdown
Collaborator Author

Closing as superseded by PR #6 and due to stale conflicts.

@marcusglee11
marcusglee11 deleted the test/branch-protection-2 branch January 16, 2026 01:15
marcusglee11 pushed a commit that referenced this pull request Apr 24, 2026
Encodes six governance decisions as ratified sections in
COO_Operating_Contract_v1.0.md and registers ADR-001 / ADR-002:

Section 7 — Active vs Standby COO and Sole-Writer Boundary:
- Exactly one active COO is sole writer of operational state.
- Standby COO may observe, rehearse, verify, and prepare switchover only.
- Standby COO may not mutate operational state while standby.
- Operational state scope defined explicitly (issue body, labels, projections,
  all receipt types).
- Seven-step switchover sequence required for activation.

Section 8 — Inter-Agent Directionality and Pushback Rules:
- Hermes and OpenClaw may exchange advisory guidance, challenge packets,
  readiness assessments, and recommendations.
- Peer-to-peer direction is advisory only; not authoritative unless re-issued
  through the active COO authority path or explicitly stamped by CEO.
- Pushback is mandatory when authority, phase, approval, or writer boundary
  is unclear.

Control surfaces updated:
- docs/01_governance/COO_Operating_Contract_v1.0.md — §7 and §8 added
- docs/10_meta/ARCHITECTURE_SOURCE_OF_TRUTH.md — normalization blockers
  #3, #4, #5 closed; §7 resolved table added; §8 renumbered
- docs/10_meta/ARCHITECTURE_CHANGELOG.md — amendment A1 entry added;
  baseline entry carried forward from origin/main
- docs/10_meta/architecture_decisions/INDEX.md — ADR-001, ADR-002 registered
- docs/10_meta/COO_Authority_Contract_Draft_2026-04-24.md — carried from
  origin/main (unmodified draft; normalization input)
- docs/INDEX.md — 10_meta section added; timestamp bumped rev16→rev17
- docs/LifeOS_Strategic_Corpus.md, docs/LifeOS_Universal_Corpus.md — regenerated

Pre-existing markdownlint failures remain in original sections of imported
files (COO_Authority_Contract_Draft, ARCHITECTURE_SOURCE_OF_TRUTH tables §1-4,
COO_Operating_Contract §1 description line). These were present on origin/main
before this amendment and are not newly introduced.

Closes: #31, #33

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
marcusglee11 pushed a commit that referenced this pull request Apr 26, 2026
Encodes six governance decisions as ratified sections in
COO_Operating_Contract_v1.0.md and registers ADR-001 / ADR-002:

Section 7 — Active vs Standby COO and Sole-Writer Boundary:
- Exactly one active COO is sole writer of operational state.
- Standby COO may observe, rehearse, verify, and prepare switchover only.
- Standby COO may not mutate operational state while standby.
- Operational state scope defined explicitly (issue body, labels, projections,
  all receipt types).
- Seven-step switchover sequence required for activation.

Section 8 — Inter-Agent Directionality and Pushback Rules:
- Hermes and OpenClaw may exchange advisory guidance, challenge packets,
  readiness assessments, and recommendations.
- Peer-to-peer direction is advisory only; not authoritative unless re-issued
  through the active COO authority path or explicitly stamped by CEO.
- Pushback is mandatory when authority, phase, approval, or writer boundary
  is unclear.

Control surfaces updated:
- docs/01_governance/COO_Operating_Contract_v1.0.md — §7 and §8 added
- docs/10_meta/ARCHITECTURE_SOURCE_OF_TRUTH.md — normalization blockers
  #3, #4, #5 closed; §7 resolved table added; §8 renumbered
- docs/10_meta/ARCHITECTURE_CHANGELOG.md — amendment A1 entry added;
  baseline entry carried forward from origin/main
- docs/10_meta/architecture_decisions/INDEX.md — ADR-001, ADR-002 registered
- docs/10_meta/COO_Authority_Contract_Draft_2026-04-24.md — carried from
  origin/main (unmodified draft; normalization input)
- docs/INDEX.md — 10_meta section added; timestamp bumped rev16→rev17
- docs/LifeOS_Strategic_Corpus.md, docs/LifeOS_Universal_Corpus.md — regenerated

Pre-existing markdownlint failures remain in original sections of imported
files (COO_Authority_Contract_Draft, ARCHITECTURE_SOURCE_OF_TRUTH tables §1-4,
COO_Operating_Contract §1 description line). These were present on origin/main
before this amendment and are not newly introduced.

Closes: #31, #33

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
marcusglee11 added a commit that referenced this pull request Apr 26, 2026
* docs: ratify COO authority amendment A1 (issues #31, #33)

Encodes six governance decisions as ratified sections in
COO_Operating_Contract_v1.0.md and registers ADR-001 / ADR-002:

Section 7 — Active vs Standby COO and Sole-Writer Boundary:
- Exactly one active COO is sole writer of operational state.
- Standby COO may observe, rehearse, verify, and prepare switchover only.
- Standby COO may not mutate operational state while standby.
- Operational state scope defined explicitly (issue body, labels, projections,
  all receipt types).
- Seven-step switchover sequence required for activation.

Section 8 — Inter-Agent Directionality and Pushback Rules:
- Hermes and OpenClaw may exchange advisory guidance, challenge packets,
  readiness assessments, and recommendations.
- Peer-to-peer direction is advisory only; not authoritative unless re-issued
  through the active COO authority path or explicitly stamped by CEO.
- Pushback is mandatory when authority, phase, approval, or writer boundary
  is unclear.

Control surfaces updated:
- docs/01_governance/COO_Operating_Contract_v1.0.md — §7 and §8 added
- docs/10_meta/ARCHITECTURE_SOURCE_OF_TRUTH.md — normalization blockers
  #3, #4, #5 closed; §7 resolved table added; §8 renumbered
- docs/10_meta/ARCHITECTURE_CHANGELOG.md — amendment A1 entry added;
  baseline entry carried forward from origin/main
- docs/10_meta/architecture_decisions/INDEX.md — ADR-001, ADR-002 registered
- docs/10_meta/COO_Authority_Contract_Draft_2026-04-24.md — carried from
  origin/main (unmodified draft; normalization input)
- docs/INDEX.md — 10_meta section added; timestamp bumped rev16→rev17
- docs/LifeOS_Strategic_Corpus.md, docs/LifeOS_Universal_Corpus.md — regenerated

Pre-existing markdownlint failures remain in original sections of imported
files (COO_Authority_Contract_Draft, ARCHITECTURE_SOURCE_OF_TRUTH tables §1-4,
COO_Operating_Contract §1 description line). These were present on origin/main
before this amendment and are not newly introduced.

Closes: #31, #33

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* chore: wiki refresh + corpus regen after A1 amendment

- Restore home.md (corrupted by PR #28), add ADR register reference
- Restore backlog-task-system, coo-runtime, mission-orchestration (corrupted by PR #28)
- Fix stale source_commit_max: agent-roles, openclaw-integration, protocols-index → 4e8237c
- Regenerate LifeOS_Strategic_Corpus.md and LifeOS_Universal_Corpus.md (includes A1 §7, §8)
- Bump docs/INDEX.md → rev19

Wiki-lint: PASSED
Doc stewardship gate: PASSED

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: LifeOS Cert <cert@lifeos.local>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant