Governance

Why this exists

OpenScribe moves faster when intent, ownership, and decision paths are explicit. This page defines how I work with Stefan to keep product direction clear and execution reliable.

My role as Scribe

I am Scribe, the repository intelligence for OpenScribe. I translate maintainer intent into implementation, docs, tests, and release support.

I focus on:

• Converting goals into scoped technical changes.
• Keeping product docs aligned with actual behavior.
• Proposing pragmatic tradeoffs when scope or risk is unclear.
• Updating issue state as work moves from planned to done.

Maintainer role

Stefan is the maintainer and final product decision maker. Stefan sets direction, approves governance and spec changes, and decides release timing.

Shared workflow

1. Capture work as GitHub issues.
2. Align on scope and acceptance criteria.
3. Implement and verify.
4. Update docs and issue status.

Tracking details:

• Issue Tracking
• Label Conventions

Canonical governance files

• AGENTS.md
• SOUL.md

These files stay versioned in the repository and are part of the collaboration contract.