Data Abyss Documentation
Platform Guide
This guide covers where key workflows live, when to use each surface, and how to run investigations from first query to validated output.
Core Capabilities
Primary capabilities exposed in the Capabilities navigation menu.
Elliot
AI workspace for query-driven analysis with chat, model selection, and intelligence dashboard modules.
Network Intelligence
Unified graph workspace that seeds and expands publication-centered networks across multiple modes.
MIL-CIV Fusion
Focused workflow for Military-Civil Fusion exploration with tree and force-graph analysis.
Mariana
Embedded capability experience delivered through the internal Mariana iframe endpoint.
DSTKL Tracker
Tabbed view that exposes both the DSTKL Table and the Global Research Tracker interfaces.
PLA Yellow Pages
Organization-focused capability for institution discovery, classification, and intelligence pivots.
Mentions
Mentions intelligence dashboard with timeline-driven entries and filterable categories/risk levels.
Primary Search Surfaces
Main entry points for entity search workflows and what each one is best for.
Publications
/search/publications
Source-level research outputs, citations, publication metadata, and trend discovery.
People
/search/people
Researcher profile analysis, affiliation tracing, and author-level investigation.
Organizations
/search/organizations
Institution discovery, organization intelligence, and network anchor validation.
Technologies
/search/technologies
Technology-signal lookups, capability tracking, and topic-focused intelligence pivots.
Field-Level Reference
Detailed field-level material for the core entities used throughout search, dossiers, and capability workflows.
Publication
doi
string
Canonical publication identifier.
title
string
Full publication title.
year
number
Publication year used for chronology and filtering.
risk
number
Dual-use risk score on a 0-100 scale.
topAuthors
string[]
Primary contributing authors.
topAffiliations
string[]
Lead associated institutions.
topKeywords
string[]
Dominant abstract/topic keywords.
People / Author
id
string
Platform author identifier.
name
string
Researcher display name.
string
Public or institutional contact email when available.
affiliations
string[]
Known institution affiliations.
publicationCount
number
Indexed publication total.
Organization / Affiliation
id
string
Platform affiliation identifier.
name
string
Organization display name.
country
string
Country or ISO country code.
type
string
Entity type (for example university, company, government).
keywords
string[]
Core research and technology focus areas.
Technology / Keyword
keyword
string
Primary technology term.
publicationCount
number
Number of matching publications.
relatedKeywords
string[]
Frequent co-occurring terms used for pivots.
Award / Funding
funder_award
string
Award identifier from the funder record.
funder_name
string
Primary funding agency name.
funders
string[]
All linked funders.
titles
string[]
Grant or project titles.
authors
string[]
Recipient researchers.
affiliations
string[]
Linked recipient organizations.
years
string[]
Associated award years.
publication_count
number
Count of linked publications.
dois
string[]
Linked publication DOI values.
keywords
string[]
Award-linked research topics.
Recommended Investigation Workflow
A reusable process for turning exploration into repeatable intelligence output.
1) Start with an objective
Define what you need to answer before selecting a search surface or capability route.
- Choose a person, organization, technology, or publication-centered question.
- Set a narrow first pass to reduce noise before broadening scope.
2) Use search to establish ground truth
Run a targeted query in the most appropriate search surface to build an initial evidence set.
- Cross-check names, aliases, and institution variants.
- Save high-signal entities to branch into capability workflows.
3) Pivot into capabilities
Move from raw discovery into relationship, timeline, or network analysis using capability modules.
- Use Network Intelligence or MIL-CIV Fusion when the question is relationship-heavy.
- Use Mariana or tracker surfaces when specialized filters are required.
4) Validate and operationalize
Reconcile key findings across multiple modules, then package output for sharing and follow-on analysis.
- Confirm high-impact claims in at least one additional surface.
- Document route links used so teammates can reproduce the workflow.
Operational Guidance
Working principles that help keep findings consistent, traceable, and production-ready.
Access and navigation
Most workflows begin from Home, Search, or Capabilities. Documentation is intended as the central route index and process guide.
Capability coverage model
Core capabilities listed above are actively surfaced in primary navigation, while extended routes remain available for teams using legacy or specialized flows.
Evidence hygiene
When moving quickly between modules, preserve route paths and query terms so findings stay reproducible and auditable.