Tiny Tool Development

// AI Plugins / In Publishment

Unreal Integration Intelligence

Evidence export and integration planning for Unreal projects that need structured handoff material.

Unreal Integration Intelligence is in publishment for version 1.1.3 and prepares Unreal project evidence, System Dossiers, optional Translation Evidence, RAG-ready chunks, review packs, and bridge-ready handoff contracts.

Turn Unreal project analysis into structured evidence packages that downstream tools can retrieve, review, route, or act on through their own boundaries.

Ask on Discord Read GitHub documentation Back to catalogue
product slidesCommitted walkthrough media; documentation carries the detailed operating context.

// PRODUCT WALKTHROUGH

Visual orientation backed by the product facts below.

Use the gallery as quick orientation, then inspect mechanics, actions, outputs, integrations, and boundaries.

Overview Project evidence, System Dossier, optional Translation Evidence, and handoff contracts

Version 1.1.3 descriptor, facts, docs, and route manifests remain source-bound.

// THE PAIN

Before the plugin enters the chat.

Integration review produces useful knowledge, then loses shape before other tools can use it.

PAIN

Project analysis, migration notes, Blueprint observations, module structure, and asset relationships often live as screenshots, chat notes, or one-off files.

UII turns that material into structured evidence and handoff contracts so retrieval, planning, cleanup, and agent workflows can consume it without guessing.

What that feels like

  • Migration planning starts from scattered notes instead of reusable evidence packages.
  • Downstream tools cannot tell which project facts are current.
  • Agents receive broad instructions instead of structured analysis artifacts.
// WHAT YOU GET

After — in the editor, not in a slide deck.

Project evidence becomes exportable, routable, and usable by the rest of the Tiny Tool stack.

GAIN

Unreal Integration Intelligence focuses on evidence production: project analysis artifacts, migration packages, RAG-oriented handoffs, and UCM-first routing into IIS, PRS, Smart Content Diet, or local agents.

  • Evidence exports for assets, modules, symbols, reflection, network, and Blueprint-oriented analysis.
  • Optional Translation Evidence from validated UBI deep-export and compiler-diagnostic inputs plus source/target C++ and Reflection Surface indexes.
  • Migration and integration planning packages.
  • Handoff contracts for IIS retrieval, PRS execution planning, SCD migration findings, and agent workflows.

// HOW IT WORKS

The product architecture, inspected from the plugin surface.

These are the moving parts I would place on the page so buyers can understand what they are actually getting beyond the slide narrative.

01 / Extract

UII reads project structure and integration signals.

Analysis covers assets, modules, symbols, reflection, network, Blueprint-oriented context, and migration-relevant project facts.

02 / Package

Evidence becomes handoff material.

UII prepares analysis artifacts, migration packages, RAG-oriented exports, and bridge-ready contracts instead of leaving findings as loose notes.

03 / Route

Other tools consume the evidence without inheriting UII's job.

IIS indexes, PRS executes reviewed plans, SCD surfaces migration findings, and local agents receive structured context through UCM or bridge paths.

// FIT

Who actually reaches for this.

Teams preparing migrations, architecture reviews, integration audits, or AI-assisted workflows that need structured Unreal project evidence.

Unreal Integration Intelligence is an in-publishment evidence producer for Unreal projects: profile validation, project/source/asset evidence export, System Dossier generation, optional source/target Translation Evidence, review packs, RAG chunks, and IIS-ready handoff artifacts.

// SURFACE

Where it lives in Unreal.

Project analysis output, evidence packages, migration planning artifacts, handoff contracts, UCM route definitions, and bridge-ready export material.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

Grouped from plugin modules, public APIs, automation hooks, and documented workflow surfaces.

Evidence export

The core value is creating reusable project evidence for analysis and downstream tooling.

  • Export project evidence for architecture and integration review.
  • Build asset, module, symbol, reflection, network, and Blueprint-oriented artifacts.
  • Prepare RAG-oriented packages for retrieval systems.
  • Keep handoff contracts structured enough for other tools to validate.

Migration planning

UII supports the planning phase before a restructure executor or cleanup tool acts.

  • Prepare migration planning packages.
  • Surface integration risks and project relationships.
  • Feed PRS with reviewed implementation intent rather than raw guesses.
  • Feed SCD with migration-specific advisory findings where the bridge path is used.

Stack handoff

UII is intentionally a producer, so the rest of the stack can do the work it owns.

  • IIS can dock prepared evidence and make it searchable.
  • PRS can execute approved restructure plans.
  • SCD can consume migration evidence for cleanup review.
  • UCM can publish routes while no-UCM bridges remain reference adapters.

// OPERATOR TOOLS

Concrete actions, expected result, and mutation boundary.

This is the part that keeps product marketing honest: buyers can see which buttons, APIs, or MCP tools matter and what they change.

// ACTION

Export evidence

Why it matters
Collects project facts into structured artifacts.
Operator result
Downstream tools receive a package instead of scattered notes.
Change surface
Read-oriented export.
// ACTION

Build handoff contract

Why it matters
Shapes evidence for a target consumer such as IIS, PRS, or SCD.
Operator result
The receiving tool can validate and import the material.
Change surface
Writes handoff artifacts.
// ACTION

Prepare migration package

Why it matters
Collects migration-relevant signals and review context.
Operator result
Migration work starts from evidence rather than memory.
Change surface
Read-oriented planning output.
// ACTION

Route through UCM

Why it matters
Publishes or invokes handoff paths through capability declarations.
Operator result
Evidence flow is visible as project setup.
Change surface
Depends on the declared route.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Run project analysis and export evidence artifacts.

02

When Blueprint translation is in scope, validate UBI deep-export and compiler diagnostics before building the optional Translation Evidence bundle.

03

Use UCM routes or bridge contracts to hand evidence to IIS, PRS, SCD, or agent-facing workflows.

04

Review the generated planning package before downstream tools act on it.

// PROOF AND BOUNDARIES

Signals that make the product specific, plus the limits worth saying out loud.

Each card turns implementation facts into buyer-facing proof without pretending the tool solves the wrong problem.

Status Advanced preview, not listed on Fab yet
Boundary Evidence producer, not indexer or executor
Consumers IIS, PRS, SCD, local agents
Route model UCM-first with reference bridge options
Outputs Evidence exports, migration packages, handoff contracts

Outputs

What the plugin leaves behind when the workflow is doing useful work.

  • Evidence package

    Structured project facts for review and downstream tools.

  • Migration package

    Planning material for migration and integration work.

  • Handoff contract

    Consumer-specific artifact for IIS, PRS, SCD, or agent workflows.

  • RAG-ready material

    Evidence that can become retrieval context through IIS.

Integrations

Where the product connects without losing ownership of its own domain.

  • Internal Index Service

    Indexes prepared UII evidence for search, context packs, and agent workflows.

  • Project Restructure Service

    Uses reviewed UII planning material while keeping mutation in PRS.

  • Smart Content Diet

    Can surface UII migration handoff evidence as advisory cleanup findings.

  • Unreal Capability Mesh

    Preferred route layer for handoff visibility and policy.

  • Unified MCP Server

    Can expose routed evidence workflows to local clients through provider tools.

Safety model

The boundaries that make the tool understandable before automation enters.

  • Producer boundary

    UII exports and packages evidence; it does not replace IIS or PRS.

  • Structured handoff

    Consumers receive validated contracts instead of loosely copied notes.

  • Route visibility

    UCM makes handoff paths inspectable in setup.

  • Optional bridges

    No-UCM bridges are reference adapters, not the preferred default path.

Not for

The cases where the product promise would be the wrong expectation.

  • Teams looking for the local retrieval index itself.

  • Workflows where evidence export should directly mutate the project.

  • Projects that do not need structured migration or integration handoff material.

// PRODUCT MEDIA

Tutorial and platform embeds stay attached to product context.

YouTube, Discord, LinkedIn, and Fab widgets are reserved for product presentation, explanation, support context, or tutorials. No third-party widget loads automatically.

Tutorial video

YouTube

Product walkthroughs, setup explanations, and tutorial material.

Embed source pending. No third-party widget is loaded here.

Open platform
Primary support context

Discord

Discord-first product support, quick questions, setup discussion, and community context.

Embed source pending. No third-party widget is loaded here.

Open platform
Professional context

LinkedIn

Company background, provider identity, project credibility, and listing context.

Embed source pending. No third-party widget is loaded here.

Open platform
Marketplace context

Fab

Product listing context, license details, purchase route, and marketplace availability.

Embed source pending. No third-party widget is loaded here.

Open platform

// INFORMATION

All essential product signals in one place.

Status In Publishment
Category AI Plugins
Unreal Engine 5.4; current descriptor/build line UE 5.8
Source state Descriptor, package docs, UCM manifests, dossier core tests, Translation-Evidence input validation, and public projections reconciled; a full dual-index Translation-Evidence happy-path test and real Slot 01/02 product-image captures remain tracked follow-ups.
Primary surface Project analysis output, evidence packages, migration planning artifacts, handoff contracts, UCM route definitions, and bridge-ready export material.
Marketplace No product checkout linked
Direct sales None on this website
Support route Discord first; product context lives on this page
Listing context Fab for marketplace, LinkedIn for public provider identity
Fact surface 4 functions / 3 settings / 3 failure modes / 1 bridge
Boundary Evidence producer for Unreal project truth, review packs, RAG-ready chunks, handoff contracts, and optional Translation Evidence without owning retrieval, embeddings, model routes, or mutation.
Primary workflow Validate a profile, export local Unreal evidence, build review or handoff artifacts, and let downstream owners index or consume them after review.
Publication boundary In Publishment is a Fab handoff state, not a live listing claim.
Proof state Descriptor, package docs, UCM manifests, dossier core tests, Translation-Evidence input validation, and public projections reconciled; a full dual-index Translation-Evidence happy-path test and real Slot 01/02 product-image captures remain tracked follow-ups.

// NOTES

Practical boundaries.

UII 1.1.3 is in publishment and is not linked to a Fab checkout yet.

The common implementation supports Unreal Engine 5.4+; the current descriptor and build line target UE 5.8.

The product boundary is evidence and planning infrastructure, not retrieval or mutation.

The UII to IIS bridge shows the direct-adapter path when UCM is not used.

// LEGAL / PRIVACY

Static information page.

Purchases, downloads, marketplace accounts, and platform-specific license details are handled outside this website. Product or tutorial widgets are loaded only after activation, where configured.

Provider details are listed in the legal notice. The current site template does not set first-party cookies and does not load analytics scripts.

Legal Notice Privacy Policy

// RESOURCES

Open the channel that matches the next question.

Fab seller profile

No product-specific Fab listing is linked yet. The public seller profile remains available.

Open

GitHub documentation

Manuals, quickstarts, settings references, troubleshooting, technical notes, and release material live in GitHub.

Open

Discord support (primary)

Start quick questions, setup help, support context, and product-fit discussion on Discord.

Open

Plugin support email

Formal plugin support requests can be sent to the dedicated support mailbox.

Open

LinkedIn company context

Company background, public provider identity, and listing context are available on LinkedIn; support still starts on Discord.

Open

// RELATED

Nearby tools in the catalogue.

AI Plugins

Internal Index Service

Local indexes, retrieval, context packs, embedding jobs, and agent-facing search.

View page
AI Plugins

LLM Store

Central management for AI providers, models, routes, policies, costs, and secrets.

View page
AI Plugins

Unified MCP Server

Editor-only loopback MCP host with provider registry, bearer-token auth, and modular tool aggregation.

View page

// TOOL NAVIGATION

Continue through the catalogue.

Each tool page keeps the product overview here and routes deep technical material to GitHub.

Previous: Project Restructure Service Next: Unreal Capability Mesh