Argus
Verified written intelligence from open sources.
This is the system record of PureTensor's flagship: how a continuous stream of open-source documents becomes assessed, provenance-linked written intelligence, why most documents are discarded on purpose, and how the autonomous stack underneath keeps the whole pipeline alive.
The open web outruns any analyst
The signal an organisation needs is public: funding announcements, regulatory filings, hiring pages, procurement notices, technical reporting. The problem is volume and form. It arrives as thousands of documents in no particular order, and reading it is a full-time job nobody was hired to do.
Aggregators do not solve it. Forwarding two hundred headlines a day converts a reading problem into a bigger reading problem. What an analyst actually needs is the opposite of aggregation: assessment. Which of these documents says something new, matters to my watchlist, and survives being checked against its own sources?
There is a second, quieter problem: the questions themselves are sensitive. A watchlist reveals strategy. Argus is built so the watching happens inside a boundary the operator controls, and the output is finished, written intelligence rather than a feed.
From raw document to written brief
One auditable path. Every document that survives assessment carries its provenance with it, so every claim in a finished brief traces back to the sources that support it.
Judged in parallel, published on consensus
No single model decides what matters. Every document is scored independently by a council of models, across novelty, impact, and analytical depth, and only consensus survives. The drop lane is not a failure mode; it is the product working. A brief is valuable because of everything that was left out of it.
The flagship rides an autonomous stack
Argus does not run on a vendor's platform. Beneath it, Sentinel keeps the estate alive, pNexus routes the work, and pureMind remembers what every incident taught. Each layer keeps its own engineering record.
What a brief promises
Four commitments, each a construction fact of the system rather than a policy.
Assessed, not aggregated
Argus does not forward headlines. Every document is scored by a council of models and most are discarded; what survives is written into finished intelligence with an analytical position, not a link list.
Every claim has a source
Provenance is carried through the whole pipeline. A statement in a brief traces back to the documents that support it, so an analyst can check the work instead of trusting it.
A boundary you control
Watchlists, questions, and briefs live inside an operator-controlled boundary. Collection reaches out; nothing about what you are watching leaks back out.
In production, not in slides
Argus has delivered scheduled briefs to clients in the AI infrastructure sector since June 2026, running on the same autonomous stack documented on this site.
The flagship, on the record.
Argus is in production and taking a small number of new client conversations. A sample brief is the fastest way to judge it: ask, and one arrives.