foliant-protocol 0.1.0__tar.gz

foliant_protocol-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.

foliant_protocol-0.1.0/NOTICE

@@ -0,0 +1,14 @@
+Foliant reference implementation
+Copyright 2026 Machine Quotient Ltd
+
+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.

foliant_protocol-0.1.0/PKG-INFO

@@ -0,0 +1,120 @@
+Metadata-Version: 2.4
+Name: foliant-protocol
+Version: 0.1.0
+Summary: Foliant reference implementation: agent accounts with hierarchical spending policies, payment channels, pooled settlement and HTTP 402 metering in the x402 wire format
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://foliant.network
+Project-URL: Source, https://github.com/gazoy/concord
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: cryptography>=42
+Requires-Dist: fastapi>=0.110
+Requires-Dist: httpx>=0.27
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: hypothesis>=6; extra == "test"
+Dynamic: license-file
+
+# Foliant — reference implementation (Python)
+
+Executable specification of the Foliant protocol: budgets and settlement for
+AI agent crews. Agent accounts with spending policies the agent's code cannot
+bypass, arranged in a tree so a whole crew shares one bound, TEE-style attestation, payment channels and streams, Ark-style pooled
+channels a whole crew pays through, HTTP 402 metering in the x402 wire format,
+and the compute-and-data market objects (whitepaper §6).
+
+Foliant is a protocol, not a chain: on-chain contracts, an x402 payment scheme
+and an SDK, deployable on chains agents already use. First targets are Base and
+Avalanche. The whitepaper also describes a sovereign chain the protocol could
+grow into if adoption warrants it; that is a direction, not the product. §11a
+of the whitepaper records the prior art (Tempo, the x402 batch-settlement
+scheme and others) and what Foliant adds.
+
+This is a **spec plus demo**, not a deployment. It runs in one process with an
+in-memory ledger so the state machines and their invariants can be read,
+changed and tested quickly. The Solidity port implements the same state
+machines as contracts; the tests here become its conformance suite.
+
+## Name
+
+The project was called Concord until 28 September 2026; the name was changed to Foliant after a UK trade-mark search. Older links, issues and messages that say Concord refer to this project.
+
+## Documents
+
+- Website: [foliant.network](https://foliant.network) (served from `docs/` via GitHub Pages)
+- [Whitepaper v0.1](docs/whitepaper.md) — the full design (§6 is what this repo implements)
+- [Design, feasibility and cost study](docs/study.md) — chain survey, build routes, costs, risks
+
+## Demo
+
+![Foliant demo](demo/video/foliant-demo.gif)
+
+[Two-minute narrated walkthrough (MP4)](demo/video/foliant-demo-voiced.mp4) of the first four scenarios, by the author (scenario E, the crew, was added afterwards and is not in the recording).
+
+`python demo/make_video.py` regenerates the captioned video, GIF and voiceover script in `demo/video/`; pass the voiceover's section boundaries in seconds to re-time the captions.
+
+## Run
+
+```bash
+pip install -r requirements.txt
+python demo/run_demo.py     # five scenarios: channel, pool, policy, exit, crew; ~1 s
+python demo/run_uses.py     # six further uses: containment, insurable agent, abuse control,
+                            # cross-company trade, delegated money, device fleet
+pytest                      # 34 tests incl. property-based invariants
+python sim/crosschain.py --quick   # cross-ledger budget-tree simulation, smoke run
+```
+
+## Layout
+
+| Path | Whitepaper | What it holds |
+| --- | --- | --- |
+| `foliant/crypto.py` | §2 principle 9 | Ed25519 keys, canonical hashing, `Signed` messages with a `scheme` tag for signature agility |
+| `foliant/accounts.py` | §6.1-6.3a | `AgentAccount` (with `parent`), `Policy` (with `within`), `Attestation`, `AgentSigner` (the enclave side that refuses to sign outside policy) |
+| `foliant/channels.py` | §6.4, §6.6 | `Channel`: monotonic signed updates, settle, close with timeout, streams |
+| `foliant/pools.py` | §6.10 | `Pool`: shared deposit, per-member claims, batch settlement, unilateral exit, contest |
+| `foliant/market.py` | §6.7, §6.11 | `ServiceOffer`, `Receipt`, `Contribution` and royalty cascade |
+| `foliant/ledger.py` | §5 (state only) | In-memory ledger: envelopes, nonces, policy enforcement up the account tree, delegation and recall, escrow accounting |
+| `foliant/agent.py` | SDK | Agent-side helper: builds envelopes and off-chain updates |
+| `foliant/x402.py` | §6.5, §6.9 | `PaymentGate` (provider middleware, FastAPI) and `AgentHttpClient` (pays on 402) |
+| `demo/` | | A metered API, the four-scenario demo and six further use-case scenarios |
+| `tests/` | §10 | Invariants: conservation, bounds, replay, stale/forged updates, unilateral exit, policy windows, the budget tree |
+| `sim/` | §12 open problems | Cross-ledger budget tree study: specification, simulation, results, two independent audits |
+
+## The rule that matters
+
+The spending policy bounds **committed** value. A deposit into a channel or
+pool is the spend that the policy sees, on both the signer (enclave) side and
+the ledger side, using the same `Policy.check`. Off-chain updates are bounded
+by the deposit they draw on, so they need no further budget check; the signer
+still enforces allow/deny lists, expiry and monotonic balances on every update.
+This is what makes "the enclave refuses to sign" and "the chain refuses to
+apply" the same decision.
+
+Accounts form a tree. A signer may **delegate** a child account with a policy
+no wider than its own and fund it; value leaving the tree is checked against,
+and recorded in, every ancestor's policy, all or nothing, so no branch can
+commit more than any ancestor allows even after a parent is tightened. Moves
+inside the tree are not spends. Any ancestor's signer can set a descendant's
+policy, rotate its signer or recall its funds. That is how an orchestrator
+gives its crew a budget and takes it away without a human.
+
+## What is not here
+
+Fees, the paymaster and the zero-fee lane (§5); consensus, data availability
+and checkpoints (§4-5); IBC (§7); governance and token issuance (§8-9). Those
+are borrowed components and are specified in the whitepaper, not prototyped.
+
+## Invariants tested
+
+- Channel: payee receives exactly the highest signed balance; payer gets back the rest; escrow ends at zero; stale, forged and tampered updates are rejected; a close finalises after the timeout regardless of the payee; a payee beats a dishonest close with a newer update.
+- Pool: coordinator receives exactly the sum of highest signed balances; every member can exit unilaterally with or without the coordinator; a stale exit is contested; a stale update in a batch is skipped, not fatal; supply is conserved.
+- Policy: for any sequence of attempted spends, committed value in any window never exceeds `per_window_max`, and signer and ledger agree at every step; escalation co-signature lifts `per_tx_max`; nonces prevent replay; the owner rotates the signer and the old key is dead.
+- Tree: a child policy wider than its parent is refused; over random trees and random spends, no subtree ever commits more than its root's cap and every ancestor's window equals its subtree's total; a tightened parent binds existing children at once; funding and recall are not spends; only the owner or an ancestor's signer administers a descendant.
+- Attestation: only quotes from a trusted vendor, for the account's own signer key, are accepted; an offer can require a code hash.
+- 402: terms are x402-shaped; replay and underpayment get a 402 with a reason; receipts are provider-signed; one `settle()` pays out many calls.
+
+## Licence
+
+Copyright 2026 Machine Quotient Ltd. Licensed under the [Apache License 2.0](LICENSE).

foliant_protocol-0.1.0/README.md

@@ -0,0 +1,101 @@
+# Foliant — reference implementation (Python)
+
+Executable specification of the Foliant protocol: budgets and settlement for
+AI agent crews. Agent accounts with spending policies the agent's code cannot
+bypass, arranged in a tree so a whole crew shares one bound, TEE-style attestation, payment channels and streams, Ark-style pooled
+channels a whole crew pays through, HTTP 402 metering in the x402 wire format,
+and the compute-and-data market objects (whitepaper §6).
+
+Foliant is a protocol, not a chain: on-chain contracts, an x402 payment scheme
+and an SDK, deployable on chains agents already use. First targets are Base and
+Avalanche. The whitepaper also describes a sovereign chain the protocol could
+grow into if adoption warrants it; that is a direction, not the product. §11a
+of the whitepaper records the prior art (Tempo, the x402 batch-settlement
+scheme and others) and what Foliant adds.
+
+This is a **spec plus demo**, not a deployment. It runs in one process with an
+in-memory ledger so the state machines and their invariants can be read,
+changed and tested quickly. The Solidity port implements the same state
+machines as contracts; the tests here become its conformance suite.
+
+## Name
+
+The project was called Concord until 28 September 2026; the name was changed to Foliant after a UK trade-mark search. Older links, issues and messages that say Concord refer to this project.
+
+## Documents
+
+- Website: [foliant.network](https://foliant.network) (served from `docs/` via GitHub Pages)
+- [Whitepaper v0.1](docs/whitepaper.md) — the full design (§6 is what this repo implements)
+- [Design, feasibility and cost study](docs/study.md) — chain survey, build routes, costs, risks
+
+## Demo
+
+![Foliant demo](demo/video/foliant-demo.gif)
+
+[Two-minute narrated walkthrough (MP4)](demo/video/foliant-demo-voiced.mp4) of the first four scenarios, by the author (scenario E, the crew, was added afterwards and is not in the recording).
+
+`python demo/make_video.py` regenerates the captioned video, GIF and voiceover script in `demo/video/`; pass the voiceover's section boundaries in seconds to re-time the captions.
+
+## Run
+
+```bash
+pip install -r requirements.txt
+python demo/run_demo.py     # five scenarios: channel, pool, policy, exit, crew; ~1 s
+python demo/run_uses.py     # six further uses: containment, insurable agent, abuse control,
+                            # cross-company trade, delegated money, device fleet
+pytest                      # 34 tests incl. property-based invariants
+python sim/crosschain.py --quick   # cross-ledger budget-tree simulation, smoke run
+```
+
+## Layout
+
+| Path | Whitepaper | What it holds |
+| --- | --- | --- |
+| `foliant/crypto.py` | §2 principle 9 | Ed25519 keys, canonical hashing, `Signed` messages with a `scheme` tag for signature agility |
+| `foliant/accounts.py` | §6.1-6.3a | `AgentAccount` (with `parent`), `Policy` (with `within`), `Attestation`, `AgentSigner` (the enclave side that refuses to sign outside policy) |
+| `foliant/channels.py` | §6.4, §6.6 | `Channel`: monotonic signed updates, settle, close with timeout, streams |
+| `foliant/pools.py` | §6.10 | `Pool`: shared deposit, per-member claims, batch settlement, unilateral exit, contest |
+| `foliant/market.py` | §6.7, §6.11 | `ServiceOffer`, `Receipt`, `Contribution` and royalty cascade |
+| `foliant/ledger.py` | §5 (state only) | In-memory ledger: envelopes, nonces, policy enforcement up the account tree, delegation and recall, escrow accounting |
+| `foliant/agent.py` | SDK | Agent-side helper: builds envelopes and off-chain updates |
+| `foliant/x402.py` | §6.5, §6.9 | `PaymentGate` (provider middleware, FastAPI) and `AgentHttpClient` (pays on 402) |
+| `demo/` | | A metered API, the four-scenario demo and six further use-case scenarios |
+| `tests/` | §10 | Invariants: conservation, bounds, replay, stale/forged updates, unilateral exit, policy windows, the budget tree |
+| `sim/` | §12 open problems | Cross-ledger budget tree study: specification, simulation, results, two independent audits |
+
+## The rule that matters
+
+The spending policy bounds **committed** value. A deposit into a channel or
+pool is the spend that the policy sees, on both the signer (enclave) side and
+the ledger side, using the same `Policy.check`. Off-chain updates are bounded
+by the deposit they draw on, so they need no further budget check; the signer
+still enforces allow/deny lists, expiry and monotonic balances on every update.
+This is what makes "the enclave refuses to sign" and "the chain refuses to
+apply" the same decision.
+
+Accounts form a tree. A signer may **delegate** a child account with a policy
+no wider than its own and fund it; value leaving the tree is checked against,
+and recorded in, every ancestor's policy, all or nothing, so no branch can
+commit more than any ancestor allows even after a parent is tightened. Moves
+inside the tree are not spends. Any ancestor's signer can set a descendant's
+policy, rotate its signer or recall its funds. That is how an orchestrator
+gives its crew a budget and takes it away without a human.
+
+## What is not here
+
+Fees, the paymaster and the zero-fee lane (§5); consensus, data availability
+and checkpoints (§4-5); IBC (§7); governance and token issuance (§8-9). Those
+are borrowed components and are specified in the whitepaper, not prototyped.
+
+## Invariants tested
+
+- Channel: payee receives exactly the highest signed balance; payer gets back the rest; escrow ends at zero; stale, forged and tampered updates are rejected; a close finalises after the timeout regardless of the payee; a payee beats a dishonest close with a newer update.
+- Pool: coordinator receives exactly the sum of highest signed balances; every member can exit unilaterally with or without the coordinator; a stale exit is contested; a stale update in a batch is skipped, not fatal; supply is conserved.
+- Policy: for any sequence of attempted spends, committed value in any window never exceeds `per_window_max`, and signer and ledger agree at every step; escalation co-signature lifts `per_tx_max`; nonces prevent replay; the owner rotates the signer and the old key is dead.
+- Tree: a child policy wider than its parent is refused; over random trees and random spends, no subtree ever commits more than its root's cap and every ancestor's window equals its subtree's total; a tightened parent binds existing children at once; funding and recall are not spends; only the owner or an ancestor's signer administers a descendant.
+- Attestation: only quotes from a trusted vendor, for the account's own signer key, are accepted; an offer can require a code hash.
+- 402: terms are x402-shaped; replay and underpayment get a 402 with a reason; receipts are provider-signed; one `settle()` pays out many calls.
+
+## Licence
+
+Copyright 2026 Machine Quotient Ltd. Licensed under the [Apache License 2.0](LICENSE).

foliant_protocol-0.1.0/foliant/__init__.py

@@ -0,0 +1,18 @@
+"""Foliant reference implementation (Python) — agent accounts, policies, channels, pools.
+
+Executable specification for whitepaper §6; the Cosmos SDK port follows these
+state machines one-to-one and reuses the tests in `tests/` as a conformance suite.
+"""
+from .accounts import AgentAccount, AgentSigner, Attestation, Policy
+from .agent import Agent
+from .channels import Channel
+from .crypto import KeyPair, PublicKey, Signed, sign
+from .ledger import Ledger
+from .market import Contribution, Receipt, ServiceOffer, royalty_split
+from .pools import Pool
+
+__all__ = [
+    "Agent", "AgentAccount", "AgentSigner", "Attestation", "Channel", "Contribution",
+    "KeyPair", "Ledger", "Policy", "Pool", "PublicKey", "Receipt", "ServiceOffer",
+    "Signed", "royalty_split", "sign",
+]