Skip to content
Portfolio/Capabilities

CAPABILITY 03 / 30

Find anything in seconds

One reorganization and a generated index, so people and agents both stop guessing which file is current.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

Most companies do not have a file problem, they have a findability problem: three logos called final, versions buried in someone’s folder, and no way to tell which one is live. The fix is a one-time reorganization into a documented scheme plus an index that gives every asset a canonical name, a status, and a stable link.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the sample asset tree and the generated index.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON
The shared drive as foundData · 237 files across 51 folders with the diseases flagged per file: 87 redundant copies, 70 filename versions, 19 unreferenced files, 25 parked on a desktop or in downloads, 117 images with no stated pixel size. Served at /assets/systems/find-anything/data/before.json.Open the file ↗
JSON
The reorganized indexData · 150 assets in a 26 folder taxonomy. Each carries a canonical name, stable url, status, owner, kind, format, dimensions or page count, color mode, usage note, allowed use, tags, named variants, and the before paths it came from.Open the file ↗
JSON
Apex Instruments logo kitData · Three lockups by three treatments, each as SVG plus three PNG sizes, with the clear space rule, three minimum sizes, three never-do rules, and the approved backgrounds.Open the file ↗
MJS
Data builderData · Node ESM. One catalogue of canonical assets with the messy paths each came from, from which before.json, after.json and logo-kit.json are all derived, so the mapping cannot drift.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Inventory

    Everything is listed, including the duplicates and the orphans.

  2. 02Decide

    One asset becomes canonical. The rest become superseded or archived, never deleted quietly.

  3. 03Rename

    A documented scheme replaces version suffixes and personal shorthand.

  4. 04Index

    A generated reference index carries name, kind, size, status, owner, usage, and a stable link.

  5. 05Cite

    People and agents link the index entry, so nobody hands out a path that will move.

WHAT IT READS

  • Every existing file, wherever it currently lives
  • A folder taxonomy and a naming scheme
  • An owner and a status for each asset

WHAT IT CHECKS BEFORE IT SHIPS

  • Every asset has exactly one current version
  • Every old path maps to where it went
  • A link in the index is stable across a reorganization
  • An agent asked for a logo gets the approved lockup, not a screenshot
In production: logo kits and URL reference indexes in both company systems, so the assistant cites the published link instead of inventing a path.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next