We loaded our own company into AOS Cloud, the same way we load a client’s
Our own company · 2026 Q2
The situation
Arcanian’s own working knowledge lives in one internal folder. It holds briefs, strategy, audits, pitches, meeting notes and correspondence, written as Markdown documents, among 8,608 files in all.
What it looked like
A copy of the folder also sat in a shared hand-off drive, so the same material could be loaded from two places.
What was actually true
None of it was in AOS Cloud yet. Of the 8,608 files, 1,159 were Markdown. Leaving out hidden and archive folders, the instruction files written for our AI tools and anything over 900 KB left 1,143 documents.
How we found it
We counted the folder on disk first. Then we loaded from that working copy and skipped the drive copy, so nothing went in twice. The load checks each file’s path and content before writing, so running it again adds nothing new.
What changed
All 1,143 documents went into our own folder in AOS Cloud with the folder structure kept. 1,142 were read in, meaning split into passages and made searchable. The one left out had fewer than 50 characters. Extraction found 12,227 new connections for the knowledge graph in 1,094 of the documents.
Where it ended
Done and verified: no failures, and nothing waiting to be processed. Two gaps were written down. Only the Markdown was loaded. And the folder is not in the automatic sync, so later changes need another run.
What we did not claim
That the 12,227 connections are confirmed. A machine extracted them, and they start unconfirmed. They are promoted only when a second, different document says the same thing. We did not report how many of ours have been promoted.
Why it matters beyond this case
A connection to a system is worth exactly what the ordered material underneath it is worth. Every link in the graph carries a status, so a machine-proposed link and a human-confirmed one are never read as the same strength of claim.