Dogfood Public Repository Standard v1 in Flow

[jmcte]

Problem statement

Flow does not yet consume and conform to its own released policy through Bootstrap.

Desired outcome

Flow is migrated through Bootstrap plan/apply with pinned versions, generated ownership, security, conformance, diagrams, and provenance passing.

Scope

• Inventory product-owned versus managed files.
• Migrate project.bootstrap.yaml with previewed diffs.
• Apply only after plan review and validate all gates.

Non-goals

• Fleet-wide rollout.

Acceptance criteria

• No production policy ref points at main.
• No direct generated-file edits remain.
• README contract and required diagrams pass.
• CI, security, provenance, and conformance checks pass.

Test expectations

Run Bootstrap plan, golden migration tests, and live CI/conformance verification.

Security implications

Do not place sink credentials or private provenance in the repository.

Documentation implications

Record migration outcome and any temporary exception.

Dependencies

Released Flow policy and Bootstrap resolver/projection/conformance/provenance work.

Human decision points

Any class deviation, permanent exception, license change, or other hard stop.

[jmcte]

The released Flow-policy prerequisite is now satisfied.

• Exact immutable consumer reference: v1.0.1
• Release: https://github.com/OMT-Global/flow/releases/tag/v1.0.1
• Tagged commit: 504c79e59689f906a234e7145ee5752588b438b3
• Published ZIP SHA-256: 25137ba7b3d8eea8db1c125f9a6de27dbf263d1996d5b1d581233ffd28b48fd0
• Offline verification passed independently after download.
• Governing release issue: Publish and verify the first immutable Flow policy release #23

The remaining prerequisite is Bootstrap's verified resolver/projection path. OMT-Global/bootstrap#67 is green and contains the requested path-confinement fix and regression test, but it still has stale CHANGES_REQUESTED review state and awaits independent re-review. No unresolved inline threads remain.

While that review gate remains, the next safe action for #13 is a read-only Bootstrap plan against current Flow main using the exact v1.0.1 release bundle; repository apply must wait for the Bootstrap dependency to land.

[jmcte]

Issue #13 plan-first migration update

Completed prerequisites and evidence:

• Published and independently verified immutable Flow policy release v1.0.1.
• Tagged commit: 504c79e59689f906a234e7145ee5752588b438b3.
• Published release ZIP SHA-256: 25137ba7b3d8eea8db1c125f9a6de27dbf263d1996d5b1d581233ffd28b48fd0.
• Canonical policy-object digest accepted by the Bootstrap resolver: 52877f4225a192c6ac2250a7f289f479be83a923ce15152c517db77ab0d5249d.
• Prepared a clean v2 manifest migration in an isolated issue worktree and ran Bootstrap plan before any apply.
• The plan preserves the human hard stops tracked separately in Complete public repository stewardship and security reporting surfaces #26: it does not select or overwrite a license, security contact, or code-of-conduct decision.

The plan exposed two blockers that make repository apply unsafe today:

1. Bootstrap PR #67 is mergeable and all checks pass, but it remains blocked by stale CHANGES_REQUESTED state and awaits independent re-review. No unresolved inline review threads remain.
2. The current PR #67 renderer records managed-file ownership and exposes standalone conformance/provenance capabilities, but plan/apply do not yet resolve the declared Flow bundle or project the full required security, contribution, diagram, and provenance artifact set. Applying its current plan would therefore create a partial Bootstrap state while claiming strict policy consumption.

I also audited the older comprehensive Bootstrap implementation branches. They contain more projection logic, but are based on an older main and have been superseded by the current issue-specific stack; grafting them onto Flow would bypass the active review and supply-chain fixes.

Safe next action: keep #13 blocked, land and independently approve the current Bootstrap resolver stack, then finish the remaining projection integration on issue-backed Bootstrap branches. Resume this exact Flow worktree, rerun plan, review the managed/product-owned inventory, and only then run apply, conformance, security, provenance, and live CI verification.