Tiny Tool Development

// Example Projects / Free companion

UII IIS Bridge

A handoff bridge from Unreal Integration Intelligence evidence exports into Internal Index Service.

Connects UII handoff artifacts with IIS import, catalog, retrieval, and context-pack workflows.

Dock UII evidence handoff contracts into IIS so extracted integration intelligence becomes searchable retrieval context.

Ask on Discord Read GitHub documentation Back to catalogue
UII IIS Bridge system overview
system artCanonical schematic media; status, proof, and roadmap remain data-driven in the page.
// THE PAIN

Before the plugin enters the chat.

UII extracts rich evidence — then it sits in a folder IIS never indexes.

PAIN

UII produces structured handoff contracts with useful project evidence — but on disk they are just files until something imports them. Manual copy steps get skipped. Indexes go stale. Agents ask questions the retrieval layer cannot answer.

The gap between extraction and search is where context dies: plenty of signal exported, none of it catalogued.

What that feels like

  • Handoff files pile up without a validated import into IIS.
  • Re-export and manual copying become the unofficial pipeline.
  • Agent workflows stall because retrieval never saw the exported evidence.
// WHAT YOU GET

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

Validate UII contracts, dock evidence, and continue in IIS search and agent workflows.

GAIN

The bridge validates contracts, docks prepared evidence, and chains catalog, embeddings, smoke search, and context packs — so UII keeps extracting while IIS owns what is searchable.

  • Contract validation before files touch the index.
  • Import through catalog, embeddings, and smoke search in one pipeline.
  • UII keeps extraction; IIS keeps retrieval and agent-facing surfaces.

// 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 / Find

The bridge locates the latest UII handoff.

Blueprint functions expose latest handoff path discovery and direct import entry points for prepared UII contracts.

02 / Validate

Contracts are checked before evidence docks into IIS.

The bridge validates handoff shape and prepared evidence so the indexer receives material in the form it expects.

03 / Pipeline

Import can chain into catalog, embeddings, and context checks.

Operators can import only, import and build catalog, or import plus catalog and embeddings depending on readiness.

// FIT

Who actually reaches for this.

Teams that already generate UII handoff contracts and want IIS import, catalog, retrieval, context-pack, and agent workflows.

The bridge connects systems without blurring the ownership boundaries of Unreal Integration Intelligence and Internal Index Service.

// SURFACE

Where it lives in Unreal.

Contract validation, file-level docking, import pipeline, smoke search, reports, Blueprint/Python/C++ entry points, and guardrail notes.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

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

Handoff docking

The product solves the gap between extraction and retrieval.

  • Find latest UII handoff path.
  • Import prepared UII handoff contracts.
  • Dock evidence into IIS-ready artifact locations.
  • Validate the handoff before it touches index workflows.

Index pipeline

After import, the bridge can keep the workflow moving inside IIS.

  • Import and build the IIS catalog.
  • Import, catalog, and run embedding preparation.
  • Support smoke search and context-pack readiness in the broader flow.
  • Keep IIS responsible for retrieval and agent-facing surfaces.

Product separation

The bridge is credible because it does not blur what UII and IIS are for.

  • UII extracts and packages integration evidence.
  • The bridge validates and docks handoff data.
  • IIS indexes, retrieves, and serves context packs.
  • Agents query IIS, not random export folders.

// 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

Latest handoff path

Why it matters
Finds the newest UII handoff contract on disk.
Operator result
Operators do not manually browse export folders.
Change surface
Read-only discovery.
// ACTION

Import handoff

Why it matters
Validates and imports prepared UII evidence.
Operator result
The material becomes available to IIS workflows.
Change surface
Writes IIS docking/import artifacts.
// ACTION

Import + build catalog

Why it matters
Chains handoff import into catalog build.
Operator result
Evidence becomes searchable sooner.
Change surface
Updates IIS catalog artifacts.
// ACTION

Import + catalog + embeddings

Why it matters
Runs the deeper indexing path after validation.
Operator result
Hybrid retrieval can use the imported UII evidence.
Change surface
Updates IIS catalog and embedding state.
// ACTION

Smoke search

Why it matters
Runs a bounded search after import/catalog work.
Operator result
Operators can confirm the docked evidence is actually retrievable.
Change surface
Read-only retrieval check after import.
// ACTION

Context-pack readiness

Why it matters
Checks whether imported handoff material can support agent context packs.
Operator result
The pipeline proves agent usefulness, not just file movement.
Change surface
Read-oriented readiness/export path.
// ACTION

Agent-contract export

Why it matters
Publishes IIS-facing agent contracts after handoff import is ready.
Operator result
Local agents can discover the retrieval surface that includes UII evidence.
Change surface
Writes agent contract output.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Generate or provide a compatible UII handoff contract.

02

Run the bridge pipeline to validate and import prepared evidence.

03

Review IIS reports, context packs, smoke search, and docking readiness output.

// 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.

Type Runtime plus editor bridge
Source UII handoff contract files
Target Internal Index Service public APIs
Pipeline Import, catalog, embeddings, smoke/context readiness
Validation Handoff shape is checked before docking into IIS artifacts
Ownership UII extracts, bridge docks, IIS indexes and serves retrieval
Automation Blueprint/Python/C++ entry points plus pipeline-style actions

Outputs

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

  • Docked evidence

    Prepared material placed where IIS can index it.

  • Catalog updates

    Imported handoff content becomes queryable.

  • Readiness reports

    Validation, smoke search, and context-pack-oriented status.

  • Embedding updates

    Optional vector preparation for imported UII material.

  • Agent contracts

    Exported retrieval contracts that include the docked evidence path.

  • Import diagnostics

    File-level feedback when handoff contracts cannot be used as-is.

Inspection basis

The concrete code, API, and tool surfaces used to shape this product page.

  • Blueprint functions

    Latest handoff path, import handoff, import+build catalog, and import+catalog+embeddings are exposed.

  • Pipeline review

    Validation, docking, catalog, embeddings, smoke search, context packs, and agent-contract export define the story.

  • Dependency boundary

    The bridge reads UII handoff files from disk and calls IIS public APIs for indexing/retrieval.

  • Location note

    The inspected bridge source is under Documentation, not the Git BridgePlugins folder used by the other bridge.

Integrations

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

  • Unreal Integration Intelligence

    Provides structured handoff contracts and extracted evidence.

  • Internal Index Service

    Owns catalog, search, context packs, and agent access.

  • Unreal Capability Mesh

    Bridge operations can be represented as routeable workflow steps.

  • Agent workflows

    Imported UII material becomes part of the IIS retrieval and context-pack surface.

Safety model

The boundaries that make the tool understandable before automation enters.

  • Validate before import

    Malformed handoffs are caught before index artifacts change.

  • Pipeline choices

    Operators can stop at import or continue into heavier indexing.

  • Ownership boundary

    The bridge docks data; IIS remains the retrieval authority.

  • Staged cost

    Catalog and embedding work can be separated so heavy steps only run when needed.

  • Retrieval proof

    Smoke search and context readiness show that the pipeline produced useful evidence, not just files.

Not for

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

  • Teams not producing UII handoff contracts.

  • Workflows that want to query export folders directly instead of indexing them.

  • Pipelines where handoff files are not stable enough to validate before import.

// 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 Free companion
Category Example Projects
Unreal Engine 5.4
Source state Mixed State - implemented free companion bridge outside active buyer-doc gate scope
Primary surface Contract validation, file-level docking, import pipeline, smoke search, reports, Blueprint/Python/C++ entry points, and guardrail notes.
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 1 bridge
Boundary Free companion bridge that reads UII handoff contracts from disk and docks prepared evidence into IIS through IIS public APIs without moving import ownership into UII.
Primary workflow Enable UII, IIS, and the bridge, generate the UII iis_import_contract.json handoff, then run the bridge pipeline for import, catalog, bounded embedding jobs, smoke search, and context packs.
Publication boundary Free companion example project lives under ../Documentation/bridge-plugins and is parked outside the active Fab publication framework until the Example Projects track is fully integrated.

// NOTES

Practical boundaries.

The bridge depends on IIS public APIs and reads UII handoff files from disk.

It is a companion integration, not a replacement for either core system.

// 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.

Example Projects

Tiny Tool Execution Integration Bridge

Connects Tiny Tool Execution with Unified MCP Server and Unreal Capability Mesh.

View page
Example Projects

SCD IIS Similarity Bridge

Connects SCD similarity requests and health evidence with IIS retrieval contracts.

View page
Example Projects

SCD PRS Bridge

Connects reviewed SCD placement moves with guarded PRS restructure workflows.

View page

// TOOL NAVIGATION

Continue through the catalogue.

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

Previous: IIS LLM Store Bridge Next: Visual Fidelity Director