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.
- 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
bootstrapcan project into product repos.
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- read-only-by-default inspector for repo flow metadata; see the operator guide.docs/autonomous-flow-platform.md- design rationale and rollout plan.docs/omt-global-operating-map.md- org-level ownership map.docs/policy-index.md- current policy authority, release, and implementation evidence.docs/public-repository-standard-gap-analysis.md- historical discovery record and links to remaining migration work.
The controller should repeatedly:
- Inspect live GitHub issues and pull requests.
- Normalize each item into one flow state.
- Choose one next action and one accountable actor.
- Dispatch a worker only when autonomy policy permits.
- Validate worker output.
- Update GitHub-visible state.
- Arm auto-merge or route approval only when gates are satisfied.
Open PR clearance has priority over starting new implementation work:
- Merge clean approved green PRs.
- Refresh or repair dirty, behind, conflicted, or failing PRs.
- Resolve requested changes.
- Review PRs needing review.
- Start new issues only when the PR queue is healthy.
bash scripts/ci/run-fast-checks.shFor mainline or release-contract validation, including an offline deterministic policy build:
bash scripts/ci/run-extended-validation.shInspect a repository without mutating GitHub or local assignment state:
python scripts/flow/inspect_repo_flow.py --repo OMT-Global/flow --issuesThe inspector requires explicit mutation flags and explicit output/assignment paths. Review the proposed writes in the default report before following the apply examples.
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.
- Product name:
OMT-Global Flow - Repository:
OMT-Global/flow - Manifest:
project.bootstrap.yaml - Visibility:
public - Default branch:
main - Archetype:
generic-empty
The current immutable policy release is v1.0.1. Production consumers must pin an exact SemVer release or immutable commit SHA; main and floating compatibility aliases are discovery aids only and are never valid production policy references.
This repository uses release maturity level simple. Level 1 simple publishes immutable exact SemVer tags such as v1.2.3 and may advance floating discovery aliases such as v1.2 and v1. Level 2 governed adds preflight, full validation, explicit publish approval, postpublish verification, and release evidence.
Cut patch releases from release/X.Y branches when you maintain an older minor line. Cut new minor and major releases from main.