On 4 November 2026, RC365 Holding plc (LSE: RCGH) gave its beta product RC AI Brain an official authority layer, a mark that says which company record wins, with its version, effective date and scope attached. The update was published through RNS, the London Stock Exchange announcement service.

RC AI Brain is at beta stage and is still being developed and assessed. RC365, a payments and fintech group listed in London, is not selling a finished system. It is publishing a design, and it names a problem retrieval alone does not solve: two versions of the same record can both be found, and only one of them should govern.

What the official authority layer actually marks

RC365 describes RC AI Brain as a company controlled knowledge and authority layer, built to help existing AI systems read corporate information with clearer context. It structures company information and relationships, associates records with sources and evidence, and makes knowledge available in AI readable formats.

The product has three parts: tools to organise, search, link, publish and maintain company information; memory, an organised record of that information with its earlier versions and sources; and the official authority layer, which marks the records the company treats as authoritative and links them to their source evidence. Each record can carry its version, the date it takes effect, what it covers and where it applies.

It is not a new AI model, large language model or chatbot. Compatibility with specific AI systems is still subject to technical validation, and no partnership with any AI provider is implied. Official authority means the company's own control over its information, not regulator approval, government endorsement or independent certification. The applications RC365 lists are potential uses, not customer deployments, and the update carries no revenue, profit or earnings guidance.

Chief executive Chi Kit (Michael) Law stated the aim in one line: "Our objective is to help companies give existing AI systems the right context, not just more information."

RC365 was not alone that week. On 4 November, the University of St. Gallen reported that Qontext, founded at the end of 2025 by HSG graduate Lorenz Hieber with Nikita Kowalski, is building a platform that consolidates corporate knowledge for AI applications. Companies connect existing tools and specify how knowledge is structured. Qontext hosts its data and infrastructure in Europe, and its team is 13 strong. Two entrants in one week, one listed and one at seed stage, point at the same gap: a signal about where vendors think the problem sits, not proof of adoption.

Authority is a field, not a verdict

Retrieval ranks by resemblance. Given two versions of a policy, search returns the one that looks most like the question. Authority is different in kind: a decision a company makes, attaches to a record, and has to maintain as the record changes. A mark that travels without its version, effective date, scope and approver is only a label.

2toLead's analysis of Microsoft's SharePoint team knowledge base notes that anyone who can read a knowledge base can see what was added to it, even if they cannot open the original source, and that its pages change only when someone asks Copilot to update them. An authority layer without a permission scope can widen exposure the same way. One without an update path can freeze a record at the version that happened to be marked.

Jilu's own writing has covered this ground from the record side: the pillar on how Jilu works sets out a record that keeps source, reasoning and approval attached; the post on evolving workplace records covers versions in conflict over time; and the post on the trusted knowledge layer covers why a layer is only as good as the permissions and skills data under it.

The counter argument is real. Marking a record authoritative can entrench an error, because agents and readers trust the marked record first and check it last. A wrong record with a mark does more damage than a wrong record without one. RC365's own caveats set the right discount: beta stage, compatibility unvalidated, no deployments announced, and authority defined as company control rather than independent certification. Read with those caveats, the update is a design position, not production evidence.

The Authority Test

A company can test any authority layer, its own or a vendor's, with five checks.

First, a named approver. The mark names a person, not a team, who decided that this record governs. Second, the fields are attached: version, effective date and scope sit on the record itself, not elsewhere. Third, the superseded version is linked, not deleted, so what it replaced stays visible.

Fourth, the correction path propagates. When the governing record changes, the change travels to the summaries, skills and queued actions derived from it, rather than leaving them running on a retired version. Fifth, permission scope follows the mark. Authoritative for one group does not mean visible to every reader or every agent.

A company brain fails not mainly because it cannot find a document. It fails because it cannot say which document governs, for whom, and from when. A record carrying its source, its effective date, its superseded version and its approver is the unit that lets a correction travel. Whether a beta product maintains it under real use is next year's question.