BOHICA-LABS / BOHICA-LABS/vsdd-factory

process-gap(orchestrator): dispatches that RECOMMEND the structurally-safer remediation form instead of MANDATING it — producers pick the fragile option

Open
#666 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2
Forks
1
Avg merge
6h 43m
Merged PRs (30d)
29

Description

Two data points from one convergence cycle:

- For a growing commit-chain reference inside a slow-moving document section, the orchestrator dispatch offered pointer-vs-enumeration and RECOMMENDED the pointer. The producer chose the enumeration — which was complete and correct at write time. It staled within ONE pass when the chain grew by a commit, costing a full convergence pass plus a fix round.
- When the same class recurred later in the cycle, the dispatch MANDATED the pointer form. No recurrence of that surface since.

Rule adopted: when one remediation form is structurally safer than another — pointer vs enumeration, derived-from-command-output vs retyped, construct-sweep vs instance-fix — the dispatch MANDATES the safer form. Optionality in dispatches is reserved for genuinely equivalent alternatives. "Recommend" reads to a producer as "either is acceptable," and producers reasonably optimize for local completeness (the enumeration looked MORE informative), not for staleness dynamics they cannot see from inside one task.

Related-but-distinct: #550 covers prescriptive-spec-vs-implementer-latitude tension at the spec level; this is the inverse edge — structural safety properties are not style choices and should not be delegated as preferences.

Contributor guide

Open the contributing guide

Research direction

The issue describes a change to the orchestrator's dispatch logic to mandate structurally safer remediation forms instead of recommending them. Look for the dispatch logic in the codebase, likely in a module handling convergence cycles or task assignments. Identify where remediation options (pointer vs enumeration, derived-from-command-output vs retyped) are defined and how recommendations are currently made. The goal is to change the logic to enforce the safer option. Testing will involve verifying that dispatches no longer offer optional choices when one form is structurally safer.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.