The Platform
ARETE REI™ holds the regulatory work of an institution in one chain: sources and their versions, assistance-persisted analysis with its provenance, governance cases, accountable actions with owners and deadlines, evidence with independent acceptance, and executive reporting whose figures are computed from the records beneath them — not on disconnected dashboards that cannot be traced back.
The six parts of that environment are set out below with the implementation status of each. Capabilities that are not yet built are stated as such rather than presented as available.
Request AccessThe governed environment
Each part below carries its own implementation status and its own limit, so the position can be read the way an institution would read it in due diligence — including the parts that are not finished.
The jurisdictions, instruments and frameworks the platform's inventory carries, organised by region and held against the organisation's own footprint rather than a generic list.
Limit
An inventory position only: it is not operational presence, licensing or local establishment, and it does not track enforcement action in real time.
Code inspection
Sources are registered, preserved as immutable versions and hashed deterministically, with duplicate detection and a gate that keeps unverified material out of the authoritative chain.
Limit
Horizon scanning — the automated detection of new, amended or withdrawn instruments — is not implemented. The version records it will consume are the part that exists.
Automated acceptance test
Source material is turned into structured candidate findings: scope, affected entities, obligations, controls and evidence gaps, each persisted with its assumptions, uncertainty and provenance.
Limit
A pilot pipeline, not a predictive model, and never an authority-level conclusion: every finding requires human review by someone other than the person who ran it before it has any downstream effect.
Code inspection
Obligations, cases, risks, controls, accountable actions and evidence are held as one chain, with permitted transitions, approvals and escalation enforced server-side rather than by interface convention.
Limit
Deadline-driven automatic escalation is not scheduled, so escalation happens on operator action; risk and control positions are recalculated on save rather than continuously.
Automated acceptance test
Decision-ready figures computed server-side from persisted records, with explicit no-data and stale-data labelling and drill-down to the records beneath each figure.
Limit
No composite index or synthesised single score is produced. Scheduled refresh of the boardroom view is not implemented.
Automated acceptance test
Client records are held per organisation, and every protected operation is authorised server-side against the caller's organisation and role. Evidence files are stored privately and reached only through a time-limited signed link.
Limit
Cross-tenant negative testing between two separate organisations is still outstanding, and evidence expiry depends on a monitoring sweep that must be scheduled before it runs on its own.
Automated acceptance test
Statuses use the platform's own vocabulary: partially implemented, pilot, in development, planned, blocked. A capability is reported as verified only where an executable acceptance test exercises it. No certification, endorsement or regulator approval is claimed for any part of the platform.