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 #13

New issue
Closed
opened 2026-04-03 18:18:06 +00:00 by Mark · 2 comments
Mark commented 2026-04-03 18:18:06 +00:00
Owner
Copy link

Problem

Current system is a proof-of-concept stub, not a real OSINT tool.

Evidence

  • Runs only 6 modules instead of 60+
  • Data model cannot store basic OSINT data (single email, single phone)
  • No dynamic spawning of investigations based on findings
  • No recursive sub-investigations for persons
  • Findings are generic summaries, not specific data points

Root Cause

System was built as a demo/prototype without considering real OSINT requirements.

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.

## Problem Current system is a proof-of-concept stub, not a real OSINT tool. ## Evidence - Runs only 6 modules instead of 60+ - Data model cannot store basic OSINT data (single email, single phone) - No dynamic spawning of investigations based on findings - No recursive sub-investigations for persons - Findings are generic summaries, not specific data points ## Root Cause System was built as a demo/prototype without considering real OSINT requirements. ## 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.
Mark commented 2026-05-18 09:39:05 +00:00
Author
Owner
Copy link

Feature Triage Assessment

Scope: large
Risk: high
Spec Alignment: misaligned
Summary: Meta-issue claiming the system is a non-functional stub running only 6 modules with an incomplete data model, but the codebase now demonstrates 75 EvidenceModule classes, a complete relational schema (Case, Person, Organization, EvidenceItem, Finding, Lead, RelationshipEdge, InvestigationRun), LLM-driven cascade investigation, and 1,671 tests.
Recommendation: Recommend closing as outdated — the original complaint is factually superseded by the current codebase. Before closing, verify referenced sub-issues (#5-#12) in Forgejo; if any remain open, reframe this issue to track only those specific residual gaps rather than the broad 'stub' claim.
Rationale: SCOPE=large: meta-issue referencing 8 sub-issues; closing or reframing it involves cross-checking all of them. RISK=high: closing could be contentious if the user still perceives gaps; the sweeping nature of the original complaint also makes a simple 'fixed' tag unreliable without verifying sub-issues. SPEC=misaligned: the spec describes 42+ modules, complete data model, and LLM-driven orchestration — the current codebase substantially implements all of those, making the core premise of the issue factually inaccurate.

Labeled blocked:needs-decision — unblock on Forgejo to dispatch to the fixer pipeline.

## Feature Triage Assessment **Scope:** large **Risk:** high **Spec Alignment:** misaligned **Summary:** Meta-issue claiming the system is a non-functional stub running only 6 modules with an incomplete data model, but the codebase now demonstrates 75 EvidenceModule classes, a complete relational schema (Case, Person, Organization, EvidenceItem, Finding, Lead, RelationshipEdge, InvestigationRun), LLM-driven cascade investigation, and 1,671 tests. **Recommendation:** Recommend closing as outdated — the original complaint is factually superseded by the current codebase. Before closing, verify referenced sub-issues (#5-#12) in Forgejo; if any remain open, reframe this issue to track only those specific residual gaps rather than the broad 'stub' claim. **Rationale:** SCOPE=large: meta-issue referencing 8 sub-issues; closing or reframing it involves cross-checking all of them. RISK=high: closing could be contentious if the user still perceives gaps; the sweeping nature of the original complaint also makes a simple 'fixed' tag unreliable without verifying sub-issues. SPEC=misaligned: the spec describes 42+ modules, complete data model, and LLM-driven orchestration — the current codebase substantially implements all of those, making the core premise of the issue factually inaccurate. Labeled `blocked:needs-decision` — unblock on Forgejo to dispatch to the fixer pipeline.
Mark commented 2026-05-28 00:37:02 +00:00
Author
Owner
Copy link

This issue has been decomposed into the following sub-issues:

# Title Phase Scope
#79 System is a non-functional stub - not a real OSINT investiga Current system is a proof-of-concept stub, not a real OSINT tool.
#80 System is a non-functional stub - not a real OSINT investiga - Runs only 6 modules instead of 60+ - Data model cannot store basic OSINT data
#81 System is a non-functional stub - not a real OSINT investiga System was built as a demo/prototype without considering real OSINT requirements
#82 System is a non-functional stub - not a real OSINT investiga 1. Complete data model (see issues #8, #9) 2. Full playbook execution (see issue

Each sub-issue has been labeled with needs-triage and will be evaluated by the triage pipeline before queue routing.

This issue has been decomposed into the following sub-issues: | # | Title | Phase Scope | |---|-------|-------------| | #79 | System is a non-functional stub - not a real OSINT investiga | Current system is a proof-of-concept stub, not a real OSINT tool. | | #80 | System is a non-functional stub - not a real OSINT investiga | - Runs only 6 modules instead of 60+ - Data model cannot store basic OSINT data | | #81 | System is a non-functional stub - not a real OSINT investiga | System was built as a demo/prototype without considering real OSINT requirements | | #82 | System is a non-functional stub - not a real OSINT investiga | 1. Complete data model (see issues #8, #9) 2. Full playbook execution (see issue | Each sub-issue has been labeled with `needs-triage` and will be evaluated by the triage pipeline before queue routing.
Mark closed this issue 2026-05-28 00:37:02 +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#13
No description provided.