Skip to main content

Knos

The neutral meter for AI agent work: neither side keeps the count.

Both sides close invoices on evidence both verify.

Of 241 merged agent pull requests claiming passing tests, 9 failed a test, build, lint or type check.

Check · Judges

The claim

Two parties who distrust each other compute the same bill from evidence a third party signed. The program releases the money on that signature, with no company and no oracle in the middle.

Limits, in one line: Solana devnet, test USDC, no outside users yet (docs/DISCLOSURE.md).

The meter: two ledgers, one bill

  1. Buyer and supplier each keep their own ledger of the evaluations GitHub signed.
  2. Each runs knos meter reconcile on its own copy and rebuilds the same statement, line for line.
  3. A line's policy is met, or it is disputed, duplicate or without enough evidence; only a line whose policy is met is billed. Each line then shows its four steps: policy satisfied, parties accepted, payment authorised, settled (docs/METER.md).

The money: released on a signature

  1. The buyer fixes the work, the budget and the acceptance terms before it starts; the terms are hashed into the order.
  2. GitHub signs the workflow run that judged the work, and a Solana program checks that signature itself before it pays, in test USDC. The smallest example is a bounty: a maintainer comments /knos fund 20 checks: test, and a merge with test passing pays the author.
  3. Why Solana: Money is released with no custodian, and the count is anchored where neither side can alter it. A receipt verifies with no chain.

The number

Of 241 merged agent pull requests that claimed passing tests, 9 had a failed test, build, lint or type-check job at the head commit (3.7%, 95% interval 2.0% to 6.9%; docs/backtest.json); 19 had a failed check of any kind (7.9%). The scan recorded 16 and 30; 11 of the 30 were excluded on a second reading: not merged into the default branch, or the failure or the claim did not hold (docs/index_review.json, method version 1, counted by scripts/backtest.py). The second number: 17.8% of first such pull requests, 147 of 826 repositories (docs/BENCH.md). A failed check is GitHub's record, not a judgment of why it failed.

For a judge

Start at the release manifest: source, build hash, deployed version, transactions, fee schedule. The witnessed transaction (9 Oct, Knos 0.3.23, own repository, test USDC, one step fixed by hand): funded · wrong work refused · paid · replay paid nothing more · the record. Everything else is one click from docs/JUDGES.md.

What is real today

What Today Read from
This copy Release 0.3.24, October 2026. A copy naming an older release, or another product, is out of date CHANGELOG.md; the newest: PyPI
Reproduced by someone else 0 of 241 docs/CAPABILITIES.md, the rows "reproduced by someone else"
Exercised at the public devnet program ids 20 of 241: GitHub token verification, funding from a wallet, refund at the deadline, work orders, an order paying up to four payees, orders judged by hidden tests, auto-accepted orders, a holdback released after its warranty, top-ups, single-use tokens, a counted batch of evaluations, the seller's own count, a passkey funder, the passkey relay, the site's Buy page, an x402 order, strict JSON in the verifier, an outcome that is not code, ES256 tokens in one transaction, the presentation grace docs/CAPABILITIES.md, the rows "exercised on devnet"
Deployed at the public devnet program ids, no transaction recorded 9 of 241: GitLab token verification, the key guardian, funding by one comment, pay on merge, holding pay for a payee with no wallet, pause, one counted evaluation, a payee's passkey wallet, the upgrade gate docs/CAPABILITIES.md, the rows "deployed on devnet"
Tested here only 209 of 241, each with the test its row names docs/CAPABILITIES.md, the rows "tested locally"
Written, not tested 3 of 241 docs/CAPABILITIES.md, the rows "implemented"
Outside funders 0 docs/submission/NUMBERS.md, row 1
Outside repositories 0 docs/submission/NUMBERS.md, row 2
Outside payees 1, on tasks Knos funded itself docs/submission/NUMBERS.md, row 3
Payments between unrelated accounts 3, on tasks Knos funded itself docs/submission/NUMBERS.md, row 4
Buyer interviews held 0 docs/submission/NUMBERS.md, row 5
Letters of intent 0 docs/submission/NUMBERS.md, row 6
Reproductions signed by GitHub 0 docs/submission/NUMBERS.md, row 7
Outside programs reading the verifier 0 docs/submission/NUMBERS.md, row 8
Shadow counts published 0 docs/submission/NUMBERS.md, row 9
Paying customers 0 docs/DISCLOSURE.md
Revenue 0; test USDC is not money docs/MARKET.md
Outside security review none docs/ASSURANCE.md
Key holders one person holds every key; an upgrade waits 48 hours in public docs/GOVERNANCE.md
Network and money Solana devnet, test USDC; mainnet is not touched docs/SECURITY.md

Read more

uvx knos shadow invoice.csv: the same check from a terminal, on an invoice of your own. docs/STORY.md: one task in seven steps, each with its evidence. docs/MANIFEST.md: this release on one page: source, the build live at each public program id, every capability's stage, the limits. docs/README.md: every document, under six questions.


Below this line: records that scripts write from their sources, and the licence. Nothing here is typed by hand.

program address on devnet, as docs/capabilities.json records it
knos-oidc, the verifier FkwZdsYCmzicJMtHLTkPK76bYNVG4WNwkWJBiVWNtF3W runs 2.2
knos-pay, the escrow 5y7iWJ1VAMJjnnWbbdo2a2PsWJEwTExSNpzrvQSEnS8k runs 2.2
knos-meter, the count FUMKkcE95x2kZUj1zZTCbgcYBmJ3WXPHL8pyA8J6anX runs 1.1
knos-passkey, a wallet from a passkey FQPX9i5kQxLYKZyyPgM2fVK9am3w1LSk1Cuoer1sSY85 runs 1.1

This page names no time for an upgrade, so that it is true before and after one. Whether a proposal is pending, has executed or was withdrawn is read from the chain by knos status, the site's banner and the site's upgrade record (web/upgrades.json is the committed copy). The first deployment (programs) has no upgrade authority and stays as a record; nothing new is funded there.

Reproduced by someone else: none recorded yet. Exercised on devnet: verify_github, fund_from_wallet, refund, work_orders, order_pay, tests_mode, order_auto_accept, holdback_release, top_up, single_use_tokens, meter_batch, meter_seller_claim, passkey_funder, passkey_fund_relay, buyer_page, x402_knos_order, oidc_strict_json, outcome_not_code, es256_tokens, presentation_grace. Deployed on devnet: verify_gitlab, key_guardian, fund_by_comment, pay_on_merge, hold_and_bind, pause, meter_single, passkey_payee_wallet, upgrade_gate. Everything else is tested locally, implemented or not built: the table with the evidence has one row for each capability, from docs/capabilities.json. Deployed and exercised are counted only at the public program ids; what the 0.3.14 rehearsal ran at staging addresses of its own is in the note of each capability it ran, with its transaction.

MIT, all of it. Built by drexthealpha. Its memory engine is Sibyl.

Metadata

Release files for knos 0.3.24

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for knos 0.3.24
File Size Uploaded
knos-0.3.24.tar.gz 3.9 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for knos 0.3.24
File Interpreter ABI Platform
knos-0.3.24-py3-none-any.whl Python 3 none any Details

Total release size: 5.1 MB

Release files / knos-0.3.24.tar.gz

Download URL knos-0.3.24.tar.gz
Size 3.9 MB
Tags Source
SHA-256 checksum
How to use checksums
8b0d05a0b2e963542433054124f51b1cee772f52bbe024472f73c28fa2c167ce
BLAKE2b-256 checksum
How to use checksums
1a1d77c91084259a7ed8d8f81b34b040668edecc358a1d797f2c7b78aab83dbf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / knos-0.3.24-py3-none-any.whl

Download URL knos-0.3.24-py3-none-any.whl
Size 1.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
a36c9a80c0d203dfe9889578704acb931f657b7555f7dc2136115b22f96a383e
BLAKE2b-256 checksum
How to use checksums
9420ed5be088e26d2a95e2b33dc5a1b00d2d40a368cf220b4dee12c687001767
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page