[ 10 ] Project

Roadmap & conformance

VACT-P Core 0.1 is a public design draft, not a finished standard. This page tracks what the reference implementation covers today, what's next, and how an implementation earns a conformance claim.

Implementation roadmap

[ 01 ] Core trust shipped

  • Passport
  • Signed envelope
  • Mandate
  • Delegation
  • Task transitions
  • Receipts
  • Revocation
  • Python & TypeScript SDKs

[ 02 ] Execution profiles in progress

  • Synchronous streaming
  • Asynchronous leases & checkpoints
  • Ambient mandates & kill switches
  • HTTP & queue adapters

[ 03 ] Economy planned

  • Offers
  • Quotes
  • Task Contracts
  • Metering
  • Settlement adapters
  • Evaluator marketplace

[ 04 ] Federation planned

  • W3C Verifiable Credentials
  • SPIFFE bindings
  • A2A & MCP adapters
  • SCITT transparency anchoring
  • Independent registries & auditors

Core conformance

A VACT-P Core implementation must support:

JSON message envelopeJCS and Ed25519 verificationPassportsMandatesDelegationsTask ContractsTask transitionsExecution ReceiptsRevocationReplay protectionPolicy denialSchema validation

Profile claims

Beyond core, an implementation may additionally claim any of the following — each requires the corresponding conformance test suite:

VACT-P-SYNCVACT-P-ASYNCVACT-P-AMBIENTVACT-P-MARKETVACT-P-TRANSPARENCYVACT-P-MCPVACT-P-A2AVACT-P-SPIFFE

Governance

VACT-P proposes public VACT-P Enhancement Proposals (VEPs) as its change process, stewarded by working groups rather than a single commercial operator:

  • Technical Steering Committee
  • Security and Cryptography Working Group
  • Agent Safety Working Group
  • Identity and Federation Working Group
  • Market and Settlement Working Group
  • Enterprise Privacy Working Group
  • Independent Conformance Maintainers

Required governance artifacts: a public specification repository, public issue and decision history, signed releases, conformance test vectors, a vulnerability disclosure process, a deprecation policy, trademark and namespace policy, and conflict-of-interest disclosures.

Principle

No commercial operator should possess unilateral control over the global identity namespace or conformance certification.

Reference implementation layout

vact-p/
├── spec/
│   ├── VACT-P-RFC-0001.md
│   ├── schemas/
│   └── test-vectors/
├── sdk-python/
├── sdk-typescript/
├── gateway/
│   ├── identity/
│   ├── authority/
│   ├── policy/
│   ├── router/
│   └── receipts/
├── registry/
├── transparency/
├── market/
└── adapters/
    ├── mcp/
    ├── a2a/
    ├── spiffe/
    └── cloudevents/
Status

0.1.0-draft — tracks VACT-P-RFC-0001 Public Design Draft. Not production audited. Contribute via VEPs — see CONTRIBUTING.md.

Previous← Examples