OMT-Global Flow

Org-level autonomous flow protocol for OMT-Global issues, PRs, worker lanes, and merge gates.

For the high-level relationship between flow, bootstrap, .github, individual repos, Pheidon, and worker lanes, see OMT-Global Operating Map.

What Flow Defines

• A GitHub-visible state machine for issues, pull requests, checks, reviews, labels, and merge readiness.
• Worker lane contracts for Pheidon, Apollo, Daedalus, Ares, Hephaestus, and Hermes.
• Autonomy classes that decide when a worker may observe, patch, repair, or must escalate.
• PR-first queue policy so open review, repair, mergeability, and CI work outrank starting new issues.
• Merge-gate rules for linked issues, validation evidence, approvals, requested changes, checks, and auto-merge.
• Baseline schemas, issue forms, labels, project fields, dashboards, and policy docs that bootstrap can project into product repos.

Repository Map

• FLOW.md - concise protocol and controller loop.
• agents/ - lane contracts for the named worker roles.
• policies/ - autonomy, WIP, stall-handling, and merge-gate policy.
• schemas/ - issue and PR contract schemas.
• github/ - canonical labels, issue templates, project fields, and PR template inputs.
• dashboards/ - saved query patterns for operational review.
• scripts/flow/inspect_repo_flow.py - local inspector for repo flow metadata.
• docs/autonomous-flow-platform.md - design rationale and rollout plan.
• docs/omt-global-operating-map.md - org-level ownership map.

Controller Loop

The controller should repeatedly:

1. Inspect live GitHub issues and pull requests.
2. Normalize each item into one flow state.
3. Choose one next action and one accountable actor.
4. Dispatch a worker only when autonomy policy permits.
5. Validate worker output.
6. Update GitHub-visible state.
7. Arm auto-merge or route approval only when gates are satisfied.

PR-First Queue Policy

Open PR clearance has priority over starting new implementation work:

1. Merge clean approved green PRs.
2. Refresh or repair dirty, behind, conflicted, or failing PRs.
3. Resolve requested changes.
4. Review PRs needing review.
5. Start new issues only when the PR queue is healthy.

Validation

python -m json.tool schemas/issue-contract.schema.json >/dev/null
python -m json.tool schemas/pr-contract.schema.json >/dev/null
python -m py_compile scripts/flow/inspect_repo_flow.py

Run the repo CI gate before opening a PR:

bash scripts/ci/run-fast-checks.sh

Bootstrap Relationship

flow defines the operating protocol. bootstrap projects the relevant repo-local pieces into OMT-Global repositories through project.bootstrap.yaml, managed templates, labels, workflows, and GitHub policy. Update policy here first, then let bootstrap reconcile downstream repos deliberately.

Project Identity

• Product name: OMT-Global Flow
• Repository: OMT-Global/flow
• Manifest: project.bootstrap.yaml
• Visibility: public
• Default branch: main
• Archetype: generic-empty