From ab9f9ff986307e85796faa74c5769d0be59735e5 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 20 Oct 2026 01:29:56 +0000 Subject: [PATCH] docs(formal): route coordination to the active board #419 docs/FORMAL_VERIFICATION.md line 9 still sent new coordination to main #307, which has been a readable historical board since the move to #419 on 15 October 2026 (AGENTS.md). This changes that one sentence to name #419 and keep #307 as readable history. No other line, date, pinned identity or section changes. formal/README.md line 121 and formal/REVIEW_LANE.md line 91 carry the same stale route but are hash-pinned in formal/manifest.json, so they are left to the #315-first recomposition on main #358 and are not touched here. Checks at this head: tools/navigation_check.py (no problems), tools/workspace_landing_check.py (no problems), tests/test_workspace_landing.py (15 tests OK), tools/formal_gate_check.py source-only SOURCE_IDENTITY_PASS with the manifest digest unchanged. Scientific effect: NONE. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01XjmjBhHbkztFy4aSubbtiS --- docs/FORMAL_VERIFICATION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FORMAL_VERIFICATION.md b/docs/FORMAL_VERIFICATION.md index 19c959454..f47fec155 100644 --- a/docs/FORMAL_VERIFICATION.md +++ b/docs/FORMAL_VERIFICATION.md @@ -6,7 +6,7 @@ Owner directive: Dylan Roy, 27 September 2026. Scientific effect: **NONE**. This dated note is contributor routing only. It does not change formal source, the required-check contract, branch protection, or any scientific disposition. A merge or green check is not theorem acceptance. -New formal work is claimed in the relevant current formal pull request or work discussion, not on closed [main#95](https://github.com/d6g8k5htny-coder/main/issues/95). Work without a pull request uses the relevant work discussion. Use [main#275](https://github.com/d6g8k5htny-coder/main/issues/275) for tasks and claims and [main#307](https://github.com/d6g8k5htny-coder/main/issues/307) for coordination. Read the [current workflow](../governance/OP-WORKFLOW-20260930.md) before writing, and reconcile exact-path ownership with any open documentation lane. +New formal work is claimed in the relevant current formal pull request or work discussion, not on closed [main#95](https://github.com/d6g8k5htny-coder/main/issues/95). Work without a pull request uses the relevant work discussion. Use [main#275](https://github.com/d6g8k5htny-coder/main/issues/275) for tasks and claims and [main#419](https://github.com/d6g8k5htny-coder/main/issues/419) for coordination (the earlier [#307](https://github.com/d6g8k5htny-coder/main/issues/307) is readable history). Read the [current workflow](../governance/OP-WORKFLOW-20260930.md) before writing, and reconcile exact-path ownership with any open documentation lane. Examples of later formal companions, kept distinct from the September scalar pilot: