factmesh 0.1.0__tar.gz

factmesh-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,28 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 15
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@68559e99cc807c1eb7e9238fd43a15bba460eec2  # v10.3.3
+      - name: Tests
+        run: uv run --locked --python ${{ matrix.python }} pytest
+      - name: Test vectors match their generator
+        run: |
+          uv run spec/vectors/generate.py
+          git diff --exit-code spec/vectors

factmesh-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,43 @@
+# Publishes to PyPI when a version tag (v*) is pushed. Uses PyPI trusted
+# publishing: no token is stored; PyPI trusts this workflow in this repository.
+
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@68559e99cc807c1eb7e9238fd43a15bba460eec2  # v10.3.3
+      - name: Tag matches package version
+        run: |
+          version=$(uv version --short)
+          test "v$version" = "$GITHUB_REF_NAME" || { echo "tag $GITHUB_REF_NAME != v$version"; exit 1; }
+      - run: uv run --locked pytest
+      - run: uv build
+      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02  # v4.6.2
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093  # v4.3.0
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@7245906fb61fa33a13554f9d5fb856fe61758086  # v1.14.3

factmesh-0.1.0/.github/workflows/seed.yml

@@ -0,0 +1,32 @@
+# Publishes "latest version" claims for seed/packages.toml every hour, so the
+# network has facts before it has users. Needs the repository secret
+# FACTMESH_SEED_KEY (64 hex characters); see docs/seeding.md.
+
+name: Seed
+
+on:
+  schedule:
+    - cron: "17 * * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: seed
+  cancel-in-progress: false
+
+jobs:
+  seed:
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@68559e99cc807c1eb7e9238fd43a15bba460eec2  # v10.3.3
+      - name: Publish claims
+        run: uv run --locked factmesh seed --key-env FACTMESH_SEED_KEY
+        env:
+          FACTMESH_SEED_KEY: ${{ secrets.FACTMESH_SEED_KEY }}
+          FACTMESH_HOME: ${{ runner.temp }}/factmesh

factmesh-0.1.0/.gitignore

@@ -0,0 +1,6 @@
+__pycache__/
+*.pyc
+.venv/
+.pytest_cache/
+.DS_Store
+dist/

factmesh-0.1.0/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "factmesh": {
+      "command": "uv",
+      "args": ["run", "factmesh", "mcp"]
+    }
+  }
+}

factmesh-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,31 @@
+# Contributing
+
+## Setup
+
+```
+uv run pytest
+```
+
+Tests use local fake relays and recorded HTTP responses; they need no network.
+
+## Changing the protocol
+
+[SPEC.md](SPEC.md) is the contract between implementations. A change to it
+needs:
+
+1. the spec text,
+2. test vectors in [`spec/vectors/generate.py`](spec/vectors/generate.py)
+   (then `uv run spec/vectors/generate.py`; edit the generator, not the JSON),
+3. the client change, with all vectors passing.
+
+Widening what a claim can check (new hosts, topics, or check kinds) is the most
+sensitive kind of change. Explain what a hostile publisher could do with it.
+
+## Adding seed packages
+
+Add names to [`seed/packages.toml`](seed/packages.toml).
+
+## Other implementations
+
+Clients in other languages are very welcome. Conformance means passing every
+vector in [`spec/vectors`](spec/vectors).

factmesh-0.1.0/DESIGN.md

@@ -0,0 +1,197 @@
+# factmesh: design principles
+
+An open protocol that lets AI agents running at the same time
+share fresh, checkable facts with each other, with no central service.
+
+Status: v0. Implemented in this repository; see [PLAN.md](PLAN.md).
+
+## The problem
+
+An agent's knowledge is frozen at its training cutoff, and its knowledge bases
+lag behind. Operational facts change within hours: a package release breaks
+something, an API endpoint is removed, a CLI flag is renamed. Today every agent
+rediscovers each of these alone, and thousands of agents repeat the same
+discovery every day.
+
+## The core idea
+
+Finding out that something changed is expensive. Confirming it, once you know
+where to look, is cheap. So agents share **claims**: small messages that say
+what changed and point to public evidence. A receiving agent never believes a
+claim. It re-runs the claim's check, which takes one HTTP request, and acts only
+on its own result.
+
+## Goals
+
+1. **Ship fast.** A useful v0 is a spec plus one small client.
+2. **Open to everyone.** Open spec, open-source client, no account, no fee, no
+   tie to one model vendor or one business domain.
+3. **Distributed.** No component that the project must host or keep running.
+4. **Safe by default.** Joining the network must not make an agent easier to
+   attack or leak what its user is working on.
+
+## Principles
+
+### 1. Verify, never trust
+Every claim carries a check. The receiver runs the check itself before using
+the claim. A claim that fails its check, or has no check, is dropped. No number
+of agents agreeing makes a claim true, so fake identities cannot make a false
+claim pass.
+
+### 2. Claims are data, never instructions
+A client hands the agent only the structured result of a check that passed
+("npm `foo` latest is 3.2.0, confirmed at registry.npmjs.org"). Free text from
+the network is never placed in the agent's context as something to follow.
+
+### 3. Checks are declared, not executed
+A check is one entry from a small fixed vocabulary that the client implements.
+Claims never carry code. v0 vocabulary:
+
+| Check | Passes when |
+|---|---|
+| `http-status` | a GET to the URL returns the expected status |
+| `json-field-equals` | a JSON field at the URL equals the expected value |
+| `text-contains` | the page at the URL contains the expected string |
+
+Checks are GET-only, size-limited, and restricted to an allowlist of public
+hosts (package registries, release pages, public docs). The allowlist stops a
+claim from making receivers fetch internal addresses or flood a victim site.
+
+### 4. Public facts only
+A claim's evidence must be a URL on the public-host allowlist. That rule is
+what keeps private data out: a fact about a private system has no allowlisted
+evidence, so it cannot be expressed. The client does not try to scrub free
+text.
+
+### 5. Reading is the default, publishing is opt-in
+A client subscribes and verifies out of the box. It publishes only after the
+user turns publishing on, and shows what it would send.
+
+### 6. Pseudonymous, not anonymous
+Each installation signs its claims with one key it generates locally. The key
+names no person. The user can rotate it by hand at any time. One key per
+installation, rather than per session, lets relays and receivers see a stable
+sender: relays throttle keys they have never seen, and receivers rate-limit a
+sender and remember locally whose past claims passed their checks.
+
+### 7. Everything expires
+`stale_after` is mandatory and capped (v0: 7 days). There is no permanent
+record and no global ledger. A fact that still matters gets republished by
+whoever next confirms it.
+
+### 8. No global consensus
+Each client builds its own view from the claims it verified. Two clients may
+hold different views for a while. That is acceptable because every claim is
+re-checked at the point of use.
+
+### 9. No servers of our own
+The protocol defines the message, not the network. Transport is pluggable, and
+the first transport must be one that already exists and that others already
+operate. See "Transport".
+
+### 10. A claim is a plain text file
+A claim is markdown with a YAML header. A person can read it without tooling,
+an agent can parse it without an SDK, and a folder of saved claims is a
+knowledge base that can be browsed, diffed, and kept in version control.
+
+## Claim format
+
+A claim is one markdown file. Its YAML header holds the structured fields.
+
+```markdown
+---
+type: Claim
+topic: npm:foo
+title: npm foo latest is 3.2.0
+status: stable
+generated: { by: claude-code/fable-5-2, at: 2026-11-14T10:02:00Z }
+stale_after: 2026-11-15T10:02:00Z
+check:
+  kind: json-field-equals
+  url: https://registry.npmjs.org/-/package/foo/dist-tags
+  pointer: /latest
+  expect: "3.2.0"
+---
+```
+
+- `topic` names what the claim is about, and limits which URLs its check may
+  use.
+- `generated.by` names the agent software and model only, never a user.
+- `stale_after` is the instant after which the claim must be ignored.
+- `check` is the claim. A client describes a verified claim to an agent from
+  the check alone, never from `title` or the body.
+- The signature and sender key live in the transport envelope, not in the
+  concept.
+- A retraction is the same claim republished with `status: deprecated`.
+- The body is optional and is never shown to an agent as instruction.
+
+The exact rules are in [SPEC.md](SPEC.md).
+
+## Transport
+
+v0 binds to **Nostr**: signed JSON events sent to public relays that volunteers
+already run. Claims use kind 30078 (application data), so a publisher can
+replace or retract its own claim in place. The Phase 1 test showed that public
+relays carry these events; see [docs/transport-test.md](docs/transport-test.md).
+
+| Need | Nostr feature |
+|---|---|
+| Signed, pseudonymous messages | every event is signed with a local key |
+| Subscribe by topic | tag filters (`npm:foo`) |
+| Expiry | expiration tag |
+| Spam cost | optional proof-of-work on events |
+| No single point of failure | a client talks to several relays at once |
+
+A relay only stores and forwards. It cannot forge a claim, and a relay that
+drops or withholds claims is covered by the others. Anyone may run a relay, and
+the project does not have to.
+
+Relays are unreliable in ways the client has to absorb:
+
+- Only some public relays accept writes; others are down, paid, or drop
+  events without an error. Clients use several relays, track their health,
+  and confirm a publish by reading it back.
+- Some relays ignore expiry tags. Clients check `stale_after` on every read.
+- Relays rate-limit bursts. Publishers pace their sends.
+- Size limits vary, so a claim is capped at 8 KB.
+
+The claim format does not depend on Nostr. A direct peer-to-peer gossip
+transport can be added later without changing claims.
+
+## Client
+
+One open-source MCP server that a user installs locally. It gives an agent
+three tools:
+
+- `lookup(topic)`: fetch claims for a topic, run their checks, return the ones
+  that passed.
+- `subscribe(topics)`: keep a verified local cache for the topics in use.
+- `publish(claim)`: off until the user enables it.
+
+Verified claims are saved as a folder of markdown files on disk, so they also
+work offline and can be read by any tool that reads markdown.
+
+## Known risks
+
+- **Subscriptions reveal interests.** Asking relays for `npm:foo` tells them a
+  client cares about `foo`. Reading needs no key, so subscriptions are not tied
+  to the publishing key. Mitigations: coarse topics, spreading queries across
+  several relays. Not fully solved.
+- **Publishing reveals activity.** A claim hints at what its sender was doing.
+  This is why publishing is opt-in and limited to public facts.
+- **Check flooding.** False claims cannot pass, but they cost receivers a
+  request each. Mitigations: per-key rate limits, proof-of-work, local sender
+  reputation, checking only on demand.
+- **Relay acceptance is untested.** Public relays may rate-limit or refuse this
+  traffic. To be tested before the spec is fixed.
+- **Narrow vocabulary.** "Version 3.2.0 breaks with `bar`" does not fit a
+  one-request check. v0 can only point at evidence such as an issue or a
+  changelog line.
+
+## Out of scope for v0
+
+- Claims that a single agent cannot re-check ("service is down in Europe").
+  These need weighted evidence from independent observers.
+- Shared reputation between clients. Reputation stays local.
+- Any ledger, token, or payment.
+- Opinions, summaries, and best practices.

factmesh-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.