Skip to main content

Knos

Knos: the neutral meter.

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

Of 241 merged agent pull requests that claimed passing tests, 30 had a failed check.

Check your own invoice

uvx knos shadow invoice.csv

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 is agreed, disputed, duplicate or insufficient evidence, and only an agreed line is billed (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.
  3. The smallest example is a bounty: a maintainer comments /knos fund 20 checks: test, and a merge with test passing pays the author.

The number

241 merged pull requests by AI coding agents said tests or CI pass; 30 had a failed check at the head commit (docs/backtest.json, 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.

What is real today

What Today Read from
Runs on the public devnet program ids token verification; a bounty funded by one comment, paid on merge, refunded at its deadline; one counted evaluation; a payee's passkey wallet docs/CAPABILITIES.md, the rows above "tested locally"
Tested here only work orders, the ledger and its statements, the invoice check, the console, the exports, and every other capability docs/CAPABILITIES.md, the rows "tested locally"
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

docs/STORY.md: the three-minute demonstration in six beats, 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.1
knos-pay, the escrow 5y7iWJ1VAMJjnnWbbdo2a2PsWJEwTExSNpzrvQSEnS8k runs 2.1
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, top_up, single_use_tokens, meter_batch, meter_seller_claim, passkey_funder, passkey_fund_relay, buyer_page, x402_knos_order, outcome_not_code. 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.18

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.18
File Size Uploaded
knos-0.3.18.tar.gz 3.3 MB Details

Built distribution (wheel)

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

Total release size: 4.2 MB

Release files / knos-0.3.18.tar.gz

Download URL knos-0.3.18.tar.gz
Size 3.3 MB
Tags Source
SHA-256 checksum
How to use checksums
080842e5f271a080f1ca1caebee0416257687d3487105dda938bc53558c798bc
BLAKE2b-256 checksum
How to use checksums
e838b891b004f29c1180df295d05660768529e4e3bb24c9c31b3930dd4218e00
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.18-py3-none-any.whl

Download URL knos-0.3.18-py3-none-any.whl
Size 871.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9bd9795cc17154edda6c1c712456c015d0f98a66bfa147c8c7ad9b0e03aa562e
BLAKE2b-256 checksum
How to use checksums
e6569a31a4c3ef7af8b2b9bc11362fe647c307b2210ba5989c91faf4a97a2d03
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