Skip to main content

Knos

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: drexthealpha.github.io/Knos

pip install knos && knos shadow invoice.csv

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.

One comment

  1. A maintainer comments on an issue: /knos fund 20 checks: test. The terms are hashed into the order.
  2. Someone opens a pull request and she merges it. Had test failed at that commit, the merge would pay nothing.
  3. GitHub signs the workflow run, a Solana program checks that signature, and the author is paid in test USDC.

Two ledgers

  1. Buyer and supplier each keep their own ledger of the signed evaluations.
  2. Each runs knos meter reconcile on its own copy and rebuilds the same statement.
  3. A line is agreed, disputed, duplicate or insufficient evidence, and only an agreed line is billed (docs/METER.md).

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/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.0 until its upgrade proposal has executed; 2.1 was proposed through the multisig and runs at this address only once that proposal has executed (the live state is in web/upgrades.json); the 0.3.14 rehearsal ran it at a staging address of its own (docs/CAPABILITIES.md)
knos-pay, the escrow 5y7iWJ1VAMJjnnWbbdo2a2PsWJEwTExSNpzrvQSEnS8k runs 2.0 until its upgrade proposal has executed; 2.1 was proposed through the multisig and runs at this address only once that proposal has executed (the live state is in web/upgrades.json); the 0.3.14 rehearsal ran it at a staging address of its own (docs/CAPABILITIES.md)
knos-meter, the count FUMKkcE95x2kZUj1zZTCbgcYBmJ3WXPHL8pyA8J6anX runs 1.0 until its upgrade proposal has executed; 1.1 was proposed through the multisig and runs at this address only once that proposal has executed (the live state is in web/upgrades.json); the 0.3.14 rehearsal ran it at a staging address of its own (docs/CAPABILITIES.md)
knos-passkey, a wallet from a passkey FQPX9i5kQxLYKZyyPgM2fVK9am3w1LSk1Cuoer1sSY85 runs 1.0 until its upgrade proposal has executed; 1.1 was proposed through the multisig and runs at this address only once that proposal has executed (the live state is in web/upgrades.json); the 0.3.14 rehearsal ran it at a staging address of its own (docs/CAPABILITIES.md)

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: none recorded yet. Deployed on devnet: verify_github, verify_gitlab, key_guardian, fund_by_comment, fund_from_wallet, pay_on_merge, hold_and_bind, refund, 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.17

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.17
File Size Uploaded
knos-0.3.17.tar.gz 2.9 MB Details

Built distribution (wheel)

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

Total release size: 3.7 MB

Release files / knos-0.3.17.tar.gz

Download URL knos-0.3.17.tar.gz
Size 2.9 MB
Tags Source
SHA-256 checksum
How to use checksums
f44430cf6e2631418e68d7c40dc059073ef7500ff3107b72508c24d5500b7cf3
BLAKE2b-256 checksum
How to use checksums
454966234e33f08e4d1aa0a4ae53813088c2dc102d1eea641eb0bd1ba11f7664
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.17-py3-none-any.whl

Download URL knos-0.3.17-py3-none-any.whl
Size 779.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
53ca76312c76db2a2e2dd02b47473052a5dd2ec0d4d05a31c63b34f15ab245a8
BLAKE2b-256 checksum
How to use checksums
28823718a6bb8485d4241e6dd219496360bdb916272e8575fbf75a910051d84a
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