Mark/osint-hub
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

System is a non-functional stub - not a real OSINT investigation tool — Phase 4: What a Real OSINT Tool Needs #82

New issue
Closed
opened 2026-05-28 00:37:01 +00:00 by Mark · 3 comments
Mark commented 2026-05-28 00:37:01 +00:00
Owner
Copy link

Phase 4: What a Real OSINT Tool Needs

  1. Complete data model (see issues #8, #9)
  2. Full playbook execution (see issue #5)
  3. Dynamic LLM-driven discovery (see issue #6)
  4. Recursive investigation branches (see issue #7)
  5. Comprehensive tracking (see issue #10)
  6. Distributed execution (see issue #11)
  7. Quality/confidence system (see issue #12)

This issue tracks the meta-problem that the system doesn't meet its stated purpose.

Decomposed from osint-hub#13

## Phase 4: What a Real OSINT Tool Needs 1. Complete data model (see issues #8, #9) 2. Full playbook execution (see issue #5) 3. Dynamic LLM-driven discovery (see issue #6) 4. Recursive investigation branches (see issue #7) 5. Comprehensive tracking (see issue #10) 6. Distributed execution (see issue #11) 7. Quality/confidence system (see issue #12) This issue tracks the meta-problem that the system doesn't meet its stated purpose. --- _Decomposed from [osint-hub#13](https://forgejo.tail018ac4.ts.net/Mark/osint-hub/issues/13)_
Mark commented 2026-05-28 04:27:01 +00:00
Author
Owner
Copy link

⏸ Needs Decision

Blocking factors:

  • Didn't meet auto-approve criteria — scope=medium, risk=medium, spec=partial

Scope: medium Risk: medium Spec: partial Type: feature
Summary: System is a non-functional stub - not a real OSINT investigation tool — Phase 4: What a Real OSINT Tool Needs
Suggestion: needs investigation
Rationale:

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=medium, spec=partial --- **Scope:** medium **Risk:** medium **Spec:** partial **Type:** feature **Summary:** System is a non-functional stub - not a real OSINT investigation tool — Phase 4: What a Real OSINT Tool Needs **Suggestion:** needs investigation **Rationale:** **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.
Mark commented 2026-05-28 08:23:52 +00:00
Author
Owner
Copy link

⏸ Needs Decision

What needs to be decided?

  • Should this be split into smaller sub-issues? If yes, remove the blocked:needs-decision label and the triage will create a decomposition issue.
  • Do you want to proceed despite the risk? If yes, remove the blocked:needs-decision label and the triage will approve it.

Blocking factors:

  • Large scope — may need decomposition into phased sub-issues
  • High risk — needs human sign-off before proceeding

Scope: large Risk: high Spec: aligned Type: other
Summary: Meta-tracker (epic/parent) for 7 foundational subsystems — data model, playbook execution, LLM discovery, recursion, tracking, distributed execution, and confidence scoring — each already decomposed into their own issues (#5-#12).
Suggestion: This is a coordination/parent issue, not independently actionable. Recommend closing it as a meta-tracker now that all sub-issues #5-#12 already exist; the real work lives in those child issues. If you want to keep a roadmap view, promote it to a milestone rather than an open issue — it will otherwise linger as a perpetually-incomplete umbrella that obscures progress tracking.
Rationale: The issue body explicitly lists 7 subsystems tracked elsewhere (#5-#12), with the text positioning this as a 'meta-problem tracker' from the original decomposition of #13. Scope is large because implementing all sub-items would be a multi-subsystem effort spanning 15+ files and new modules. Risk is high because several sub-items (distributed execution, recursive branches, LLM-driven discovery) involve core architectural changes with breaking potential. Spec alignment is full — this is exactly what the project's AGENTS.md states as its purpose, and the sub-issues were decomposed with spec awareness. Type is 'other' since it functions as an epic/tracker, not a feature, bug, or chore with independent work items.

To unblock: Remove the blocked:needs-decision label. The triage will apply the appropriate outcome based on your choice above.

## ⏸ Needs Decision **What needs to be decided?** - **Should this be split into smaller sub-issues?** If yes, remove the `blocked:needs-decision` label and the triage will create a decomposition issue. - **Do you want to proceed despite the risk?** If yes, remove the `blocked:needs-decision` label and the triage will approve it. **Blocking factors:** - **Large scope** — may need decomposition into phased sub-issues - **High risk** — needs human sign-off before proceeding --- **Scope:** large **Risk:** high **Spec:** aligned **Type:** other **Summary:** Meta-tracker (epic/parent) for 7 foundational subsystems — data model, playbook execution, LLM discovery, recursion, tracking, distributed execution, and confidence scoring — each already decomposed into their own issues (#5-#12). **Suggestion:** This is a coordination/parent issue, not independently actionable. Recommend closing it as a meta-tracker now that all sub-issues #5-#12 already exist; the real work lives in those child issues. If you want to keep a roadmap view, promote it to a milestone rather than an open issue — it will otherwise linger as a perpetually-incomplete umbrella that obscures progress tracking. **Rationale:** The issue body explicitly lists 7 subsystems tracked elsewhere (#5-#12), with the text positioning this as a 'meta-problem tracker' from the original decomposition of #13. Scope is large because implementing all sub-items would be a multi-subsystem effort spanning 15+ files and new modules. Risk is high because several sub-items (distributed execution, recursive branches, LLM-driven discovery) involve core architectural changes with breaking potential. Spec alignment is full — this is exactly what the project's AGENTS.md states as its purpose, and the sub-issues were decomposed with spec awareness. Type is 'other' since it functions as an epic/tracker, not a feature, bug, or chore with independent work items. **To unblock:** Remove the `blocked:needs-decision` label. The triage will apply the appropriate outcome based on your choice above.
Mark commented 2026-06-08 13:20:19 +00:00
Author
Owner
Copy link

Closing as meta-tracker

This issue is a parent/coordination issue tracking 7 subsystems across #5-#12. All sub-issues already exist and the work is tracked there independently. Status:

  • ✅ #5 — Full playbook execution (closed)
  • ✅ #6 — Dynamic LLM-driven discovery (closed)
  • 🔄 #7 — Recursive investigation branches (open, tracked separately)
  • ✅ #8 — Person data model (closed)
  • ✅ #9 — Organization data model (closed)
  • ✅ #10 — Comprehensive tracking (closed)
  • ✅ #11 — Distributed execution (closed)
  • 🔄 #12 — Quality/confidence system (open, tracked separately)

6/8 closed, 2 remaining tracked in their own issues. The triage system recommended closing this as a meta-tracker (see comment #29909) since the real work lives in the child issues. Closing now as a completed decomposition.

## Closing as meta-tracker This issue is a parent/coordination issue tracking 7 subsystems across #5-#12. All sub-issues already exist and the work is tracked there independently. Status: - ✅ #5 — Full playbook execution (**closed**) - ✅ #6 — Dynamic LLM-driven discovery (**closed**) - 🔄 #7 — Recursive investigation branches (**open, tracked separately**) - ✅ #8 — Person data model (**closed**) - ✅ #9 — Organization data model (**closed**) - ✅ #10 — Comprehensive tracking (**closed**) - ✅ #11 — Distributed execution (**closed**) - 🔄 #12 — Quality/confidence system (**open, tracked separately**) **6/8 closed, 2 remaining tracked in their own issues.** The triage system recommended closing this as a meta-tracker (see comment #29909) since the real work lives in the child issues. Closing now as a completed decomposition.
Mark 2026-06-08 13:20:23 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
agentic-osint

Agentic OSINT features

  
audit

   
blocked:commit-ready-failed

   
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-plan

   
blocked:gate-research

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:no-changes

   
blocked:preflight

Repo has dirty lint; kilo-gsd preflight refuses to dispatch until lint-cleanup lands

  
blocked:verify-failed

   
bug

Something is not working

  
chore

Config/cleanup item

  
deferred

Deferred — will revisit later

  
enhancement

Enhancement request

  
feature-request

   
in-progress

   
lint-baseline

   
lint-cleanup

kilo-gsd preflight lint gate: repo has dirty ruff state, cleanup required before fixer dispatch

  
needs-decompose

Issue needs decompose processing

  
needs-triage

   
performance

   
quickfix

   
security/medium

Medium severity security issue

  
triage-approved

Approved by triage

No labels
agentic-osint
audit
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:preflight
blocked:verify-failed
bug
chore
deferred
enhancement
feature-request
in-progress
lint-baseline
lint-cleanup
needs-decompose
needs-triage
performance
quickfix
security/medium
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/osint-hub#82
No description provided.