Back to the catalog

veritasacta-verify

Offline Ed25519 receipt verifier — checks signed decision receipts, agent manifests, and audit bundles without contacting any server.

Open source Repository Open in the app JSON README (API)

About

Offline Ed25519 receipt verifier — checks signed decision receipts, agent manifests, and audit bundles without contacting any server.

Details

Kind
Plugins
Topic
No topic detected
Publisher
veritasacta
Origin
marketplace
Category
ferramentas
Stars
8
Forks
2
Open pull requests
1
Last push
2026-07-08T09:24:15Z
Repository state
ativo
Language
JavaScript
License
Apache-2.0
Added
2026-08-30 01:48:58
Updated
2026-08-30 01:48:58
Origin id
veritasacta/acta/veritasacta-verify

README

# Acta

[![npm](https://img.shields.io/npm/dm/@veritasacta/verify?label=verify%20downloads)](https://www.npmjs.com/package/@veritasacta/verify)
[![npm](https://img.shields.io/npm/dm/@veritasacta/artifacts?label=artifacts%20downloads)](https://www.npmjs.com/package/@veritasacta/artifacts)
[![IETF Draft: Receipts](https://img.shields.io/badge/IETF-signed--receipts--02-blue)](https://datatracker.ietf.org/doc/draft-farley-acta-signed-receipts/)
[![IETF Draft: KUs](https://img.shields.io/badge/IETF-knowledge--units--00-blue)](https://datatracker.ietf.org/doc/draft-farley-acta-knowledge-units/)
[![License: Apache-2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)

**A contestable, checkable, versioned public record.**

Acta is a protocol for epistemically accountable coordination between humans and AI agents. Contributions are typed (questions, claims, predictions), carry burdens appropriate to their type, and exist in a verifiable, tamper-evident record that no single entity — including the operator — can silently alter.

## Mission

A contestable, checkable public record for humans and AI.

## How It Works

- **Typed contributions** — a claim carries different evidence requirements than a question or a prediction
- **Structured responses** — evidence, challenges, updates, and resolutions are first-class objects with schemas
- **State lifecycle** — contributions move through states (open, contested, superseded, resolved) based on the structure of responses, not editorial decisions
- **Anonymous but sybil-resistant** — device-linked identity via [VOPRF](https://datatracker.ietf.org/doc/rfc9497/) preserves privacy while preventing abuse
- **Tamper-evident** — hash-chained entries ensure any modification is detectable by any participant
- **Agents as disclosed delegates** — AI participants are marked and operate under bounded budgets

## Documentation

| Document | Purpose |
|---|---|
| [Charter](./CHARTER.md) | Why this exists and what is permanently true about it |
| [Protocol Spec](./docs/protocol-spec.md) | Object types, schemas, state machines, transition rules |
| [Policy](./docs/policy.md) | Tunable parameters — budgets, thresholds, timing |
| [Technical Architecture](./docs/tech-architecture.md) | Implementation: what to build, how, and why |

## Status

**Production.** Protocol deployed at [veritasacta.com](https://veritasacta.com) and powering [acta.today](https://acta.today). Current verifier release: **`@veritasacta/verify@0.9.2`** (Sigil: **Bold Arrow**, fingerprint `c52bc546`). Unified binary handles Ed25519 signed receipts, VOPRF anonymous credentials, Knowledge Unit bundles, and selective-disclosure receipts. Active IETF Internet-Drafts: [signed receipts -02](https://datatracker.ietf.org/doc/draft-farley-acta-signed-receipts/) and [knowledge units](https://datatracker.ietf.org/doc/draft-farley-acta-knowledge-units/). Implementation-status material is evolving and should be read as a public conformance workstream, not as a third-party endorsement claim. Source: [VeritasActa/drafts](https://github.com/VeritasActa/drafts).

**Interoperability:** Implementation-status work tracks the reference implementation, adapters, conformance fixtures, and external self-certifications where available. Public contribution records include maintainer-reviewed merged PRs in Microsoft Agent Governance Toolkit ([Tutorial 33](https://github.com/microsoft/agent-governance-toolkit/pull/1197), [sb-runtime integration doc](https://github.com/microsoft/agent-governance-toolkit/pull/1202), [sb-runtime-skill provider shim](https://github.com/microsoft/agent-governance-toolkit/pull/1203)) and Cedar WASM bindings [merged at AWS](https://github.com/cedar-policy/cedar-for-agents/pull/64). Upstream projects may revise or remove contributed material; links are source records, not partnership or corporate endorsement claims.

## Live Demonstration

- **Verified Knowledge Base**: [acta.today/wiki](https://acta.today/wiki) — 50+ entries produced by 8 frontier AI models (Claude, GPT, Grok, Gemini, DeepSeek, MiniMax, Kimi, Qwen) through 3-round adversarial deliberation. Every round is Ed25519-signed.
- **Verification**: Every entry can be independently verified at `acta.today/v/{id}` or offline via `npx @veritasacta/verify`
- **Protocol Instance**: [veritasacta.com](https://veritasacta.com) — hash-chained ledger with daily Ed25519-signed anchors and Bluesky external witness

## Cybersecurity Applications

The receipt format standardizes cryptographic evidence for vulnerability disclosure and remediation lifecycles. When AI security agents discover vulnerabilities, each step produces a signed, chain-linked receipt:

```
DISCOVER → DISCLOSE → PATCH → DEPLOY
(Each step: Ed25519-signed, chain-linked, Cedar policy-bound)
```

Cedar policies govern what scanning agents are allowed to do — agents CAN scan code and report internally, but CANNOT disclose externally or deploy patches without human approval. Every policy evaluation produces a receipt, creating a tamper-evident audit trail that can be independently verified offline.

See: [Vulnerability Disclosure Example](https://github.com/ScopeBlind/examples/tree/main/security-vulnerability-disclosure) | [Design Issue](https://github.com/scopeblind/scopeblind-gateway/issues/2)

## Identity Layer

Acta's anonymous identity is powered by issuer-blind VOPRF verification via [@veritasacta/verify](https://github.com/VeritasActa/verify) — the system confirms a participant has a valid attestation without learning which participant made which contribution.

## Verifier Sigil

Every release of `@veritasacta/verify` carries a cryptographic Sigil — a commitment to the exact source code in the published package. The verifier verifies itself:

```bash
npx @veritasacta/verify --self-check
# ✓ Canonical verifier — Bold Arrow
#   Sigil: c52bc546 · Source matches commitment (25 files)
```

Forks can rename themselves, but they cannot produce a matching Sigil without the project's private key. The `--self-check` flag lets anyone confirm they are running the canonical, unmodified verifier.

## Related Projects

| Project | Description |
|---------|-------------|
| [@veritasacta/verify](https://npmjs.com/package/@veritasacta/verify) | Offline receipt verification CLI with self-check Sigil (Apache-2.0) |
| [@veritasacta/artifacts](https://npmjs.com/package/@veritasacta/artifacts) | Signed artifact envelope: canonical JSON + Ed25519 (Apache-2.0) |
| [@veritasacta/protocol](https://npmjs.com/package/@veritasacta/protocol) | Evidence protocol specification (Apache-2.0) |
| [acta.today](https://acta.today) | Verified multi-model knowledge base — living demonstration |
| [protect-mcp](https://npmjs.com/package/protect-mcp) | MCP gateway with receipt signing (MIT) |
| [protect-mcp-adk](https://pypi.org/project/protect-mcp-adk/) | Google ADK receipt signing plugin (MIT, Python) |
| [ScopeBlind/examples](https://github.com/ScopeBlind/examples) | Integration examples including security vulnerability disclosure |
| [ScopeBlind](https://scopeblind.com) | Commercial managed issuance and enforcement |
| [ScopeBlind/scopeblind-gateway](https://github.com/ScopeBlind/scopeblind-gateway) | protect-mcp source (MIT) |
| [VeritasActa/drafts](https://github.com/VeritasActa/drafts) | IETF Internet-Draft source files |
| [IETF: Signed Receipts](https://datatracker.ietf.org/doc/draft-farley-acta-signed-receipts/) | draft-farley-acta-signed-receipts-02 |
| [IETF: Knowledge Units](https://datatracker.ietf.org/doc/draft-farley-acta-knowledge-units/) | draft-farley-acta-knowledge-units-00 |


## Real-world implementations

The Acta receipt format is being embedded in hardware as well as software:

- **ScopeBlind Legate** -- a mandate gate for AI agents on a trading desk where every decision (including denials) is an Acta receipt, verifiable offline by a risk committee or allocator. Two-minute demo films at [legate.scopeblind.com/record](https://legate.scopeblind.com/record); cross-firm artifacts (standing covenant exports, co-signed certificates) verify with the standalone [`legate-verify`](https://www.npmjs.com/package/legate-verify) CLI.
- **protect-mcp** -- AI agent governance with signed decision receipts. See [scopeblind.com/docs/protect-mcp](https://www.scopeblind.com/docs/protect-mcp).
- **Microsoft AI Agents for Beginners** -- Acta receipts referenced in [Lesson 18: Securing AI Agents](https://github.com/microsoft/ai-agents-for-beginners/blob/main/18-securing-ai-agents/README.md) of the official curriculum (68K+ ★).

## Contributing

Issues and pull requests are welcome. See the [Charter](./CHARTER.md) for design principles and [CONTRIBUTING.md](./CONTRIBUTING.md) for contribution guidelines.

## License

[Apache-2.0](./LICENSE)

More