A task, carried through
From the first objective to a source-linked result, coordinate the work as a coherent programme.
YGG / YGGDRASIL · Flagship · In development
Complexity,
orchestrated.
YGG (Yggdrasil) is the third generation of Unified Analytics, and our flagship in development. It advances the lineage into sustained work across agents, models, tools, and teams.
CONNECTED INTELLIGENCEUA / 03
Move through the field. Follow the connections.
01 / THE FLAGSHIP
Designed to carry the entire task.
YGG turns an objective into a structured programme of work. Specialist branches pursue different questions, results converge through independent review, and knowledge remains available for the next task. Its development brings Neo’s governance foundation and Jianmu’s evidence-centred experience into a broader platform.
A system, growing wiser
Retain useful methods, verified tools, and relevant experience for the work ahead.
An institution, in control
Keep data, authority, and consequential decisions within the organization’s boundaries.
02 / TASK ARCHITECTURE
Depth where it matters.
Continuity throughout.
A shared task and knowledge foundation connects specialist work without forcing the whole project into one conversation.
EXPLORE THE TASK SYSTEMINTERACTIVE ARCHITECTURE
Durable state + selective knowledge↔
01 / Define the objective
Start with the question that matters.
Set the scope, sources, deliverables, and decision rights. A shared objective gives every specialist a clear purpose.
Objective → plan → acceptance criteria
02 / Organize the work
Give complexity a working structure.
Organize overall goals, specialist programmes, and bounded execution into a connected task tree. Independent work proceeds in parallel; shared dependencies converge at explicit review points.
Coordinator → specialist branches → bounded tasks
03 / Connect the evidence
Different disciplines. One connected account.
YGG’s investigative application brings financial records, contracts, messages, images, audio, video, and case files into one coordinated analysis. Each result links back to the material and method that support it.
Transactions + contracts + messages + media
04 / Review independently
Make the reasoning inspectable.
Combine data and calculation checks, separate reviewers, and cross-validation. Preserve criteria, findings, and evidence for consequential acceptance decisions.
Source checks → calculation checks → independent review
05 / Retain and continue
The next task starts with more knowledge.
Retain owners, dependencies, progress, results, and next actions in a versioned store. Recover interrupted work and continue across personnel, agents, and sessions. Record outcomes, failures, retries, and corrections. Distil useful methods and load relevant experience into later tasks.
Versioned results + reusable tools + relevant experience
A guided architecture illustration of the flagship in development.
03 / CONNECTED ANALYSIS
From scattered material
to a connected account.
YGG’s investigative application brings financial records, contracts, messages, images, audio, video, and case files into one coordinated analysis. Each result links back to the material and method that support it.
THE CONNECTED CASEFICTIONAL SCENARIO / ARCHITECTURE DEMONSTRATION
TOTAL INFLOW¥72m
TRACE EACH PATH
See where the money goes.
Four destinations account for the original inflow. Select a path to inspect its supporting record and calculation.
¥90m gross movement ≠ ¥90m new funds
¥72m original inflow + ¥18m repeated movement. Circulating transfers remain separately identified so the same funds are not counted twice.
COMMON DESTINATIONAC-0042Receiving account
COMPARE THE EXPLANATIONS
A connection is a starting point.
Company 01 shares a payment destination with two other entities. Match the account registry, contract scope, and payment instructions to understand the relationship.
Keep direct evidence, inferred connections, and competing explanations distinguishable.
FOLLOW THE SEQUENCE
Bring the context into view.
Select an event to inspect the relationship between communications, payment records, and supporting documents.
A shared timeline connects the material while preserving the original timestamps and source references.
MATERIALANALYSIS PURPOSEREFERENCE
Bank transactionsReconcile each allocation
TX-001 → TX-004Account registryConnect entities and accounts
REG-001Payment instructionAlign communications with events
MSG-001Contract & receiptCross-check purpose and execution
DOC-001Every finding travels with its sources, calculation scope, version, and review history. The records above are illustrative.
Illustrative source record · no real personal or customer data
Explore how the work connects. Figures illustrate the method; this is not a live product session.
Follow the money
Normalize transactions, distinguish internal transfers and returns, trace layered routes and circular flows, and preserve the calculation detail.
Connect the relationships
Link people, companies, accounts, contracts, events, and records. Compare competing explanations and identify the evidence behind each connection.
Reconstruct the sequence
Align messages, instructions, payments, project milestones, images, and video segments into a source-linked timeline.
Cross-check the evidence
Compare statements with objective records, surface contradictions and missing material, and update affected findings when new information arrives.
04 / THE SYSTEM IN DEPTH
The architecture behind
long-running intelligence.
01Hierarchical collaboration
Organize overall goals, specialist programmes, and bounded execution into a connected task tree. Independent work proceeds in parallel; shared dependencies converge at explicit review points.
02Durable task state
Retain owners, dependencies, progress, results, and next actions in a versioned store. Recover interrupted work and continue across personnel, agents, and sessions.
03Focused model context
Give each role the facts and sources its task needs. Select relevant knowledge rather than accumulating the entire project in every conversation.
04Independent verification
Combine data and calculation checks, separate reviewers, and cross-validation. Preserve criteria, findings, and evidence for consequential acceptance decisions.
05Enforced boundaries
Use scoped tool rights, protected resources, controlled writes, and version checks to connect authorization to execution. Human authority governs consequential decisions.
06Reusable tools & workflows
Discover, compose, execute, and retain tools. Build adapters for new material formats and preserve versions, operating scope, and execution history.
07Learning from actual work
Record outcomes, failures, retries, and corrections. Distil useful methods and load relevant experience into later tasks.
08Repair the defect class
Trace recurring errors to the rule or tool that caused them. Recheck related material and affected results, then retain the correction as a reusable control.
09System health & controlled improvement
Separate system diagnosis from optimization. Evaluate changes independently, preserve recoverable versions, and account for review, retry, and maintenance costs.
10Visible coordination
Bring progress, resource use, results, decisions, and outstanding work into a shared tracking surface. Keep the programme understandable as its branches grow.
11Multi-model execution
Assign models and tools to distinct analysis and review roles. Maintain task continuity while changing the model or execution session.
12Controlled deployment
Organize local inference, isolated case spaces, institutional access rules, backups, and recorded data movement within the deployment architecture.
05 / CONTROLLED DEPLOYMENT
Your environment.
Your authority.
YGG’s deployment architecture brings models, data, tools, and audit records into controlled institutional environments. Case-level permissions, isolated workspaces, recorded exports, and recoverable versions keep sensitive work within defined boundaries.
INSTITUTIONAL BOUNDARY
ModelsDataToolsAudit
Scoped access · isolated workspaces · recorded movement06 / DATA ARCHITECTURE
Scale the system.
Keep the context focused.
The architecture combines layered storage, batch ingestion, indexing, structured queries, relationship analysis, and targeted reading. Storage and compute expand independently, supporting a direction from TB-scale cases to PB-scale institutional collections without placing an entire collection inside a model context.
01Institutional collections
02Indexed and structured knowledge
03Task-relevant context
07 / PROFESSIONAL APPLICATIONS
Built around the questions
professionals need to answer.
Investigations
Trace funds, connect people and entities, organize leads, and retain source evidence.
Prosecution & courts
Align facts and materials, compare contradictions and calculation scopes, and locate original records.
Audit & compliance
Cross-check financial, contractual, and policy material around a defined review objective.
Enterprise & research
Coordinate procurement reviews, operations analysis, technical comparison, and sustained research.
08 / A CONNECTED FOUNDATION
A foundation that grows stronger.
YGG is developed alongside Neo’s working baseline. It carries forward operational knowledge, verification methods, and reusable tools while introducing a unified state store, hierarchical execution, selective memory, and machine-enforced boundaries. The development approach preserves the baseline and transfers individual controls through explicit verification.
ONE LINEAGE / NEO → JIANMU → YGG