Skip to content

docs(catalog): move IP-029 details into the Work Routing family - #4322

Closed
BigDataDZ wants to merge 1 commit into
loopx-project:mainfrom
BigDataDZ:docs/catalog-move-ip-029-to-work-routing
Closed

BigDataDZ wants to merge 1 commit into
loopx-project:mainfrom
BigDataDZ:docs/catalog-move-ip-029-to-work-routing

Conversation

@BigDataDZ

Copy link
Copy Markdown
Contributor

Summary

  • Relocate the IP-029 Handoff Todo Gate State detail entry from the Human Decision details block into the Work Routing details block, positioned between IP-003 and IP-021.
  • The catalog index table and the pattern-to-canary design matrix both list IP-029 under Work Routing, and the IP-026 cross-references describe it as a routing gate. Only the Pattern Details block placed it under Human Decision, so the details order disagreed with the table it is supposed to mirror (Pattern details use the same family order as the catalog).
  • Content is unchanged. The block is moved verbatim — no wording, ordering, or validation reference inside IP-029 was edited.
  • Documentation only. No behavior, CLI contract, or table row is changed.

Issue Or Task

  • Closes: N/A — docs-only cleanup, which CONTRIBUTING.md allows to go straight to a pull request.
  • Contributor task ID: N/A

Validation

  • Tested revision: 67788c6cc8b29fb2bd4053d93a78f434023ee7fc
  • Run state: finished
  • Input classes: none
Check kind Result Public-safe evidence / limitation
static passed loopx check --scan-path docs/concepts/interaction-pattern-catalog.md → ok: True, errors=0, public boundary scan clean: 1 files.
regression_parity passed Content-preservation check: git diff --stat is 80 insertions(+), 80 deletions(-) and the file is 2445 lines before and after. Sorting the old and new line sets yields identical output, proving this is a pure relocation with no textual change. Failing-before condition: the Work Routing details block previously omitted IP-029 while the Work Routing table listed it.
  • Coverage and gaps: Documentation-only change, so no real-entrypoint or real-backend row applies and runtime behavior is not modified. The static boundary scan covers the edited file, and the sorted-line-set comparison is an independent oracle for the claim that no content changed. No untested path is introduced by this diff.

Frontend / Visual Evidence

  • UI impact: none
  • Before:
  • After:
  • States and viewports shown:
  • Source data: none

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Refactoring (no functional changes)
  • Documentation update
  • Test update

LoopX Area

  • Control plane (goals, todos, quota, scheduler, registry, runtime)
  • Benchmark boundary (adapters, runners, verifiers, scoring, evidence)
  • Capability or extension (providers, adapters, skills)
  • Public docs or presentation surface (README, protocols, dashboard)
  • Build, packaging, installer, or CI
  • Host or runtime integration

Technical Direction

  • Core control-plane hardening

  • Long-horizon benchmark evidence

  • Operator surface and IM integration

  • Shared Goal Authority and cross-host coordination

  • Architecture and research incubator

  • Target base branch: main

  • Direction tracker or promotion unit: N/A

Shared-authority RFC fixture impact

  • Production-scale fixture schema: N/A
  • Semantic dimensions changed, or reviewed no-impact rationale: N/A — this PR does not claim progress against the TypeScript migration or shared Goal Authority RFC.
  • Provider conformance arms run: N/A
  • Read-only legacy/file/PostgreSQL three-arm rehearsal (required for promotion, runtime-routing, or compatibility-projection changes): N/A

Boundary Checklist

  • Neither the diff nor this PR body/comments/attachments disclose private state, credentials, raw traces or verifier output, internal links, or local machine paths (including .loopx/, .codex/goals/, and live ACTIVE_GOAL_STATE.md).
  • I did not duplicate maintainer-owned benchmark work unless a maintainer split out a public issue for it.
  • I kept the change scoped to the linked issue/task.
  • I completed the visual evidence section for UI changes, or marked UI impact none.
  • Every commit includes a DCO Signed-off-by trailer (git commit -s).

The catalog index table and the pattern-to-canary design matrix both
list IP-029 Handoff Todo Gate State under Work Routing, and the
cross-references in IP-026 describe it as a routing gate. Only the
Pattern Details block placed it under Human Decision, so the details
order disagreed with the table it is supposed to mirror.

Move the IP-029 detail entry into the Work Routing block, between
IP-003 and IP-021, matching the catalog row order. Content is
unchanged: the block is relocated verbatim.

Signed-off-by: BigDataDZ <76271875+BigDataDZ@users.noreply.github.com>
@BigDataDZ

Copy link
Copy Markdown
Contributor Author

Superseded by #4324, which carries both detail-order relocations (IP-029 and IP-026) as a single change. Closing this one so the catalog is not split across two near-identical PRs editing the same file.

The IP-029 relocation is unchanged and is included verbatim in #4324 (same block boundaries, same 80 insertions / 80 deletions within the combined 190/190 diff).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant