#78 - No module blocking/availability tracking - blocked modules not configurable — Phase 3: Solution Required - Mark/osint-hub - cyguin git: Adlerian Hierarchical Self-Actualization Syllogism

Mark commented

2026-05-28 00:31:52 +00:00

Owner

Phase 3: Solution Required

Check module requirements at investigation start
Mark modules as "blocked" if required config missing
Exclude blocked modules from allowed_modules
Store blocked module list in InvestigationRun.config_json
Allow user to configure blocked modules per investigation
LLM should know which modules are available vs blocked

Decomposed from osint-hub#19

## Phase 3: Solution Required 1. Check module requirements at investigation start 2. Mark modules as "blocked" if required config missing 3. Exclude blocked modules from allowed_modules 4. Store blocked module list in InvestigationRun.config_json 5. Allow user to configure blocked modules per investigation 6. LLM should know which modules are available vs blocked --- _Decomposed from [osint-hub#19](https://forgejo.tail018ac4.ts.net/Mark/osint-hub/issues/19)_

Mark added the

needs-triage

label

2026-05-28 00:31:52 +00:00

Mark referenced this issue

2026-05-28 00:31:53 +00:00

No module blocking/availability tracking - blocked modules not configurable #19

Mark added

blocked:needs-decision

and removed

needs-triage

labels

2026-05-28 00:33:24 +00:00

Mark commented

2026-05-28 00:33:24 +00:00

Author

Owner

⏸ Needs Decision

Blocking factors:

Didn't meet auto-approve criteria — scope=medium, risk=low, spec=aligned

Scope: medium Risk: low Spec: aligned Type: feature
Summary: Add module config requirement checking, blocked module tracking, and per-investigation module configuration to OSINT Hub.
Suggestion: Define config_requirements on EvidenceModule base class, check requirements at investigation start in the orchestrator, store blocked modules in InvestigationRun.config_json, add API for per-run module overrides, and surface blocked/available modules in LLM tools.
Rationale: Medium scope because it touches the module base + registry, investigation service, models, API router, and LLM integration — 5-15 files with new logic but no new subsystems. Low risk because it's largely additive: modules without requirements are unaffected, existing paths remain unchanged, and the filtering happens at a single orchestration point. Fully aligned with project's 42-module architecture and issue #19 decomposition.

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=medium, risk=low, spec=aligned --- **Scope:** medium **Risk:** low **Spec:** aligned **Type:** feature **Summary:** Add module config requirement checking, blocked module tracking, and per-investigation module configuration to OSINT Hub. **Suggestion:** Define config_requirements on EvidenceModule base class, check requirements at investigation start in the orchestrator, store blocked modules in InvestigationRun.config_json, add API for per-run module overrides, and surface blocked/available modules in LLM tools. **Rationale:** Medium scope because it touches the module base + registry, investigation service, models, API router, and LLM integration — 5-15 files with new logic but no new subsystems. Low risk because it's largely additive: modules without requirements are unaffected, existing paths remain unchanged, and the filtering happens at a single orchestration point. Fully aligned with project's 42-module architecture and issue #19 decomposition. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.

Mark added

triage-approved

quickfix

and removed

blocked:needs-decision

labels

2026-05-28 07:18:42 +00:00

Mark commented

2026-05-28 11:14:18 +00:00

Author

Owner

🤖 [quickfix-osint-hub-78] still working — overseer retry