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

Evidence detail view with manual entity tagging #1

New issue
Closed
opened 2026-03-06 01:48:31 +00:00 by Mark · 23 comments
Mark commented 2026-03-06 01:48:31 +00:00
Owner
Copy link

User Story

As an analyst, I want to click on an evidence item and view its full content/artifact so that I can manually select and tag specific items to add or edit as entities (organizations, people, findings).

Acceptance Criteria

  1. Clickable Evidence Rows: Evidence table rows are clickable (not just the Edit button)
  2. Evidence Detail View: Clicking a row opens a modal/panel showing:
    • Full summary text
    • Quote snippet (if present)
    • Artifact content (if present) - with scrollable view for large content
    • Source information
    • Capture metadata (collector, captured_at, etc.)
  3. Manual Entity Tagging: In the detail view, I can:
    • Highlight/select text portions
    • Click "Add as Person" / "Add as Organization" / "Add as Finding"
    • Pre-populate entity form with selected text
    • Edit existing linked entities
  4. Parsed Status: Shows whether evidence has been auto-parsed
  5. Link to Entities: Shows which entities have already been extracted from this evidence

Technical Notes

  • May require new endpoint to fetch full artifact content
  • Consider adding selected_text field to entity creation flow
  • Could reuse existing EntityForm component in a modal context
## User Story As an analyst, I want to click on an evidence item and view its full content/artifact so that I can manually select and tag specific items to add or edit as entities (organizations, people, findings). ## Acceptance Criteria 1. **Clickable Evidence Rows**: Evidence table rows are clickable (not just the Edit button) 2. **Evidence Detail View**: Clicking a row opens a modal/panel showing: - Full summary text - Quote snippet (if present) - Artifact content (if present) - with scrollable view for large content - Source information - Capture metadata (collector, captured_at, etc.) 3. **Manual Entity Tagging**: In the detail view, I can: - Highlight/select text portions - Click "Add as Person" / "Add as Organization" / "Add as Finding" - Pre-populate entity form with selected text - Edit existing linked entities 4. **Parsed Status**: Shows whether evidence has been auto-parsed 5. **Link to Entities**: Shows which entities have already been extracted from this evidence ## Technical Notes - May require new endpoint to fetch full artifact content - Consider adding `selected_text` field to entity creation flow - Could reuse existing EntityForm component in a modal context
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 Claimed by gsd-issue-fixer-osint-hub-1 — starting work

🤖 Claimed by `gsd-issue-fixer-osint-hub-1` — starting work
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 Claimed by gsd-issue-fixer-osint-hub-1 — starting work

🤖 Claimed by `gsd-issue-fixer-osint-hub-1` — starting work
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 Claimed by gsd-issue-fixer-osint-hub-1 — starting work

🤖 Claimed by `gsd-issue-fixer-osint-hub-1` — starting work
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — claimed — starting pipeline

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — claimed — starting pipeline
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 Claimed by gsd-issue-fixer-osint-hub-1 — starting work

🤖 Claimed by `gsd-issue-fixer-osint-hub-1` — starting work
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — claimed — starting pipeline

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — claimed — starting pipeline
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — claimed — starting pipeline

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — claimed — starting pipeline
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — research

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — research
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — claimed — starting pipeline

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — claimed — starting pipeline
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — research

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — research
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — research

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — research
Mark commented 2026-05-27 21:53:05 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — research

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — research
Mark commented 2026-05-27 21:53:17 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — plan

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — plan
Mark commented 2026-05-27 21:53:17 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — plan

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — plan
Mark commented 2026-05-27 21:53:30 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — implement attempt 1

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — implement attempt 1
Mark commented 2026-05-27 21:53:30 +00:00
Author
Owner
Copy link

GSD pipeline blocked at IMPLEMENT: prerequisite gate (lint) not passed.
Lint phase did not complete successfully.

GSD pipeline blocked at IMPLEMENT: prerequisite gate (lint) not passed. Lint phase did not complete successfully.
Mark commented 2026-05-27 21:54:38 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — plan

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — plan
Mark commented 2026-05-27 21:54:42 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — plan

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — plan
Mark commented 2026-05-27 21:56:10 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — implement attempt 1

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — implement attempt 1
Mark commented 2026-05-27 21:57:11 +00:00
Author
Owner
Copy link

🤖 [gsd-issue-fixer-osint-hub-1] still working — implement attempt 1

🤖 [`gsd-issue-fixer-osint-hub-1`] still working — implement attempt 1
Mark commented 2026-05-27 22:19:04 +00:00
Author
Owner
Copy link

GSD VERIFY phase failed after 3 attempts.
═══ Gate: verify-passed (osint-hub#1) ═══
Mode: Tier 1 (functional only)

GATE OK: All gates up to 'implement' pass
── Tier 1: Functional ────────────────────────────────
Running tests...
❌ Tests failed (exit 4)
timeout func_only: False
collected 0 items

============================ no tests ran in 0.01s =============================
/home/b/.hermes/hermes-agent/venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py:208: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset.
The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session"

warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))
ERROR: file or directory not found: tests/

============================= test session starts ==============================
platform linux -- Python 3.11.14, pytest-8.3.4, pluggy-1.6.0
benchmark: 5.1.0 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
rootdir: /home/b/Projects/osint-hub
configfile: pyproject.toml
plugins: playwright-0.8.0, mock-3.14.0, anyio-4.13.0, httpx-0.36.2, asyncio-0.24.0, timeout-2.4.0, base-url-2.1.0, xdist-3.8.0, cov-7.1.0, benchmark-5.1.0, split-0.11.0
asyncio: mode=Mode.STRICT, default_loop_scope=None
collected 0 items

============================ no tests ran in 0.01s =============================
Running linter...
✅ Lint clean
Running type checker...
✅ Types check clean
Previous test count: unknown

❌ GATE FAIL: verify-passed
- Tests failed with exit code 4
GATE FAIL: verify — blocked at 2026-05-27T22:19:04Z
Class: test-failure
Evidence: Verification failed: 1 failures
Git tag: osint-hub#1-gate-verify-fail-be748bb94ab6 (use gate-retry after fixing)

GSD VERIFY phase failed after 3 attempts. ═══ Gate: verify-passed (osint-hub#1) ═══ Mode: Tier 1 (functional only) GATE OK: All gates up to 'implement' pass ── Tier 1: Functional ──────────────────────────────── Running tests... ❌ Tests failed (exit 4) timeout func_only: False collected 0 items ============================ no tests ran in 0.01s ============================= /home/b/.hermes/hermes-agent/venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py:208: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset. The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session" warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET)) ERROR: file or directory not found: tests/ ============================= test session starts ============================== platform linux -- Python 3.11.14, pytest-8.3.4, pluggy-1.6.0 benchmark: 5.1.0 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000) rootdir: /home/b/Projects/osint-hub configfile: pyproject.toml plugins: playwright-0.8.0, mock-3.14.0, anyio-4.13.0, httpx-0.36.2, asyncio-0.24.0, timeout-2.4.0, base-url-2.1.0, xdist-3.8.0, cov-7.1.0, benchmark-5.1.0, split-0.11.0 asyncio: mode=Mode.STRICT, default_loop_scope=None collected 0 items ============================ no tests ran in 0.01s ============================= Running linter... ✅ Lint clean Running type checker... ✅ Types check clean Previous test count: unknown ❌ GATE FAIL: verify-passed - Tests failed with exit code 4 GATE FAIL: verify — blocked at 2026-05-27T22:19:04Z Class: test-failure Evidence: Verification failed: 1 failures Git tag: osint-hub#1-gate-verify-fail-be748bb94ab6 (use gate-retry after fixing)
Mark commented 2026-05-27 22:24:02 +00:00
Author
Owner
Copy link

Fixed in commit. Closing.

Fixed in commit. Closing.
Mark closed this issue 2026-05-27 22:24:02 +00:00
Mark commented 2026-05-27 22:25:39 +00:00
Author
Owner
Copy link

GSD VERIFY phase failed after 3 attempts.
═══ Gate: verify-passed (osint-hub#1) ═══
Mode: Tier 1 (functional only)

GATE OK: All gates up to 'implement' pass
── Tier 1: Functional ────────────────────────────────
Running tests...
❌ Tests failed (exit 4)
timeout func_only: False
collected 0 items

============================ no tests ran in 0.01s =============================
/home/b/.hermes/hermes-agent/venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py:208: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset.
The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session"

warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))
ERROR: file or directory not found: tests/

============================= test session starts ==============================
platform linux -- Python 3.11.14, pytest-8.3.4, pluggy-1.6.0
benchmark: 5.1.0 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
rootdir: /home/b/Projects/osint-hub
configfile: pyproject.toml
plugins: playwright-0.8.0, mock-3.14.0, anyio-4.13.0, httpx-0.36.2, asyncio-0.24.0, timeout-2.4.0, base-url-2.1.0, xdist-3.8.0, cov-7.1.0, benchmark-5.1.0, split-0.11.0
asyncio: mode=Mode.STRICT, default_loop_scope=None
collected 0 items

============================ no tests ran in 0.01s =============================
Running linter...
✅ Lint clean
Running type checker...
✅ Types check clean
Previous test count: unknown

❌ GATE FAIL: verify-passed
- Tests failed with exit code 4
GATE FAIL: verify — blocked at 2026-05-27T22:25:39Z
Class: test-failure
Evidence: Verification failed: 1 failures
Git tag: osint-hub#1-gate-verify-fail-be748bb94ab6 (use gate-retry after fixing)

GSD VERIFY phase failed after 3 attempts. ═══ Gate: verify-passed (osint-hub#1) ═══ Mode: Tier 1 (functional only) GATE OK: All gates up to 'implement' pass ── Tier 1: Functional ──────────────────────────────── Running tests... ❌ Tests failed (exit 4) timeout func_only: False collected 0 items ============================ no tests ran in 0.01s ============================= /home/b/.hermes/hermes-agent/venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py:208: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset. The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session" warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET)) ERROR: file or directory not found: tests/ ============================= test session starts ============================== platform linux -- Python 3.11.14, pytest-8.3.4, pluggy-1.6.0 benchmark: 5.1.0 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000) rootdir: /home/b/Projects/osint-hub configfile: pyproject.toml plugins: playwright-0.8.0, mock-3.14.0, anyio-4.13.0, httpx-0.36.2, asyncio-0.24.0, timeout-2.4.0, base-url-2.1.0, xdist-3.8.0, cov-7.1.0, benchmark-5.1.0, split-0.11.0 asyncio: mode=Mode.STRICT, default_loop_scope=None collected 0 items ============================ no tests ran in 0.01s ============================= Running linter... ✅ Lint clean Running type checker... ✅ Types check clean Previous test count: unknown ❌ GATE FAIL: verify-passed - Tests failed with exit code 4 GATE FAIL: verify — blocked at 2026-05-27T22:25:39Z Class: test-failure Evidence: Verification failed: 1 failures Git tag: osint-hub#1-gate-verify-fail-be748bb94ab6 (use gate-retry after fixing)
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#1
No description provided.