Polkadot’s OpenGov has matured into one of the most capable collective decision systems in crypto. Yet the information environment around it is fragmented. A typical voter’s journey crosses Polkassembly and SubSquare, dives into forum threads and bounty pages, peeks at GitHub activity, skims OGTracker and scans social channels like Reddit. Each step adds context. Each hop adds doubt. Where did a claim come from? Is a “new” proposal actually the same request across a different track? Did we fund something similar six months ago?

**Clarys.AI** is the governance intelligence layer designed to reduce that cognitive burden. We are building a provenance-first data backbone and a **usable** product, the **Accountability Explorer**, that unifies on-chain and off-chain governance signals, resolves entities across mechanisms, classifies duplication with clear definitions and reveals relationships visually. The data and interfaces are **open by default**: public GraphQL/REST APIs, daily CSV/Parquet exports and permissive licenses so any researcher or builder can reuse and extend the work without lock-in.

We listened to the community’s feedback on our prior referendum: *Phase One must deliver something people can use.* In response, this proposal centers not just on backend improvements but on a tangible, everyday tool for the ecosystem. **Beta v1** ships an interactive explorer with related-proposal graph views, duplication flags, provenance popovers, filters and sortable tables, alongside open datasets and integration hooks for governance frontends. To make quality measurable and model-agnostic, we will publish a transparent **evaluation harness**: 150 canonical governance questions run nightly with accuracy, citation coverage, latency and cost dashboards, comparing open-source and commercial models under schema constraints.

The full proposal details the product, the data and architecture behind it, the implementation plan and a fully calculated budget for **USD 130,000** to deliver **Beta v1** in approximately twelve weeks.
Full proposal: [https://docs.google.com/document/d/19en4NoDkrsRShj2\_7L6w2KY35v2blkFAR2nAqM3nx5M/edit?usp=sharing](https://docs.google.com/document/d/19en4NoDkrsRShj2_7L6w2KY35v2blkFAR2nAqM3nx5M/edit?usp=sharing)

The first proof of concept version of Clarys.AI was developed as an MVP and its development was funded by Web3 Foundations Decentralized Future grant, you can read the[<u> intro article here.</u>](https://t.co/BhxNc2pure) 

**MVP Access -** Receive public access to the MVP here: [<u>https://docs.google.com/forms/d/e/1FAIpQLScD\_BfoZd5o74uR-wu0WY-7d7tR5KzCS5g37uori1zTW6E0XA/viewform?usp=sharing\&ouid=118149997340957465621</u>](https://docs.google.com/forms/d/e/1FAIpQLScD_BfoZd5o74uR-wu0WY-7d7tR5KzCS5g37uori1zTW6E0XA/viewform?usp=sharing\&ouid=118149997340957465621)

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1717 Resubmission: Clarys.AI - OpenGov Data Backbone & Accountability Explorer (Beta v1)

No Active Proposals