Skip to content
aledgent by bloquealedgent by bloquealedgent

13. Non-goals

Commit
5ca6b8a
Version
0.4.27
Status
draft
Rendered
2026-10-17T19:30:18Z
Source
SPEC.md, last changed in 5ca6b8a
  • aledgent is not a blockchain. It does not aim for open participation, permissionless verification, or consensus among operators who distrust each other. It aims to be a private ledger whose claims can be checked. Where the two conflict, this specification chooses the second.
  • aledgent is not a product. It has no notion of a card, a wallet, a bank handle or a checkout. How an account is presented is the integrating party’s business (REQ-LA-5).
  • aledgent is not a workflow engine. Workflows call it. It never takes part in one. It does not pause, does not hold a resumption token, and does not call a caller back to decide anything (REQ-EV-5).
  • aledgent does not decide who a holder is, whether they may transact, or what anything costs. Identity verification, compliance and pricing belong to the integrating party. aledgent refuses an operation whose principal lacks authority. It records what it was told to move. It holds nothing in custody but value: no documents, no personal records, no product state.
  • aledgent does not convert between assets. A conversion is a redemption of one asset and an issuance of another, each an operation of its own, under its own authority (REQ-AS-6). aledgent offers no atomicity between them, and no rate (amendment 0012, OQ-17).
  • aledgent reaches exactly one settlement layer. Banks, card networks and other value networks sit on the far side of an integrating party or of the settlement layer. Value from them enters the book by issuance (REQ-AS-6) or through the settlement layer. It never enters through a second adapter.
  • aledgent will not offer an administrative path that moves value outside the ordinary command surface. No support-tier override, no direct storage repair, no “fix it with one write”. Every correction is an operation that is authorised, bounded and posted (REQ-AT-3, US-K4). Someone with a good reason will ask for this again. The answer stays the same. Once that path exists, INV-2, INV-20 and the whole trust model of §4.3 are false, and nobody outside the operator can tell.
  • aledgent does not claim that anchoring prevents the operator from cheating. It prevents the operator from revising what it committed to. That is a smaller claim, and a true one. The larger claim must not be made (REQ-PR-3).

© 2026 Pagos Cube LLC · Code: Apache-2.0 OR MIT · agents/: AGPL-3.0-or-later · Docs: CC-BY-4.0