Agent Archie

The file management agent.

Archie discovers every file across your drives, sites and shares, works out what each one is, names it to your convention and files it where it belongs. Then it keeps the estate that way. It never deletes a file, never widens access, and asks a person whenever it is unsure.

Optional add-on to the Corporate BrainOff by defaultOne instance per client
What Archie does

From a pile of files to an estate you can trust.

  1. 01

    Discover

    Copies every connected source into your own storage, checking for changes so nothing is fetched twice.

  2. 02

    Classify

    Tags each file with its sensitivity, subject, audience and a summary. Fixed rules run first, AI second, and each file lands in one of the Seven Levers or general operations.

  3. 03

    De-duplicate

    Finds exact duplicates and files that have been superseded by a newer version.

  4. 04

    Review

    Decides whether each document still matters, is stale, should be archived, who should own it, and whether it belongs in the Brain. Anything uncertain is left out and raised with a person.

  5. 05

    Name and file

    Works out names that fit your naming convention and where each file should live. Every move is planned as a dry run first, with a summary of how much it touches.

  6. 06

    Index and publish

    Keeps a live index of the whole estate. Only reviewed files are fed into the Corporate Brain.

  7. 07

    Groom

    Keeps checking new and changed files against the agreed rules. Within the autonomy you set, it fixes names and locations itself. Everything else becomes a one-click proposal for a person.

Guardrails

Cautious by design, and not configurable out of it.

It cannot delete

Archie has no delete operation. Disposing of a file always needs a person’s approval, and a legal hold blocks it outright.

It never widens access

Archie will not give more people access to anything. No setting changes that.

Verified after every write

After each change it re-reads the file to confirm the change actually happened, and stops at the first thing it cannot verify.

Approval that cannot time out

Proposals go to the file’s owner, then to a document controller. Nothing is approved because nobody answered.

A saved state before any change

Permission changes start by saving the current state. A restore gives people back the access they had.

A cap on every run

Each run can change only so many items. Access is added first and removed later, each step approved separately.

Where it can write

Reading everywhere. Writing only where you say.

Archie reads every connected source. It changes files in exactly one place: SharePoint libraries an administrator has granted one at a time. Everywhere else, its recommendations are yours to act on.

SourceReadMove and renameChange permissions
SharePointYesIn libraries granted one by oneIn those libraries, with the guardrails above
OneDriveYesRecommendationsRecommendations
Google DriveYesRecommendationsRecommendations
NAS and SMB sharesYes, through the collectorRecommendationsNot supported
SynologyYes, through its own API, with nothing to installRecommendationsRecommendations
Hygiene

Scheduled checks that can only report.

Alongside grooming, Archie runs scheduled hygiene checks for stale files, owners who have left, permission drift, new duplicates and empty folders. These checks report; they cannot change anything.

Staff who want their own files in the Brain need a named person to approve them first. A new client starts with nothing auto-approved.

Get the estate in order.

Archie is switched on per client, after the Corporate Brain. Tell us where your files live and we will show you what the first pass would look like.