AAIF Submission tracking: Policy Bundle RFC-001

[pshkv]

Tracking issue for RFC-001 submission to the AAIF working group.

RFC: https://github.com/sint-ai/sint-protocol/blob/main/docs/rfcs/RFC-001-policy-bundle.md (commit 50b7219)
Vocabulary PR: aeoess/agent-governance-vocabulary#11

AAIF email to send (aaif-governance@linuxfoundation.org):

Subject: RFC contribution — SINT Protocol Policy Bundle Specification

The SINT Protocol team is contributing RFC-001 for consideration by the AAIF working group as a proposed governance standard. The specification defines a machine-readable contract for agent authorization covering action allowlists, path constraints, rate limiting, human approval gates, hash-chained receipts, APS identity integration, A2A task extension format, and cascade revocation. Section 11 includes explicit AAIF compliance mapping.

RFC: https://github.com/sint-ai/sint-protocol/blob/main/docs/rfcs/RFC-001-policy-bundle.md

Three-vendor governance_attestation convergence already in progress (APS, MolTrust, SINT) via A2A#1717. We are seeking co-authorship of the AAIF governance spec and the reference implementation designation.

— Illia Pashkov, SINT Labs

Checklist:

• RFC-001 published (commit 50b7219)
• Vocabulary PR open on aeoess repo (docs: community engagement kickoff — whitepaper, tokenomics, roadmap, social drafts #11)
• Email sent to AAIF
• AAIF response
• RFC referenced in AAIF docs

[pshkv]

AAIF email sent — April 13, 2026

Submitted to aaif-governance@linuxfoundation.org.

Subject: RFC contribution — SINT Protocol Policy Bundle Specification

Status update:

• RFC-001 published (commit 50b7219)
• Vocabulary PR open on aeoess/agent-governance-vocabulary (docs: community engagement kickoff — whitepaper, tokenomics, roadmap, social drafts #11)
• Email sent to AAIF working group
• AAIF response
• RFC referenced in AAIF docs

[pshkv]

AAIF email bounced — aaif-wg@lists.linuxfoundation.org does not exist.

Correct channels found:

• GitHub: https://github.com/aaif/project-proposals (open an Issue using their proposal template)
• Email: support@aaif.io
• Discord: https://discord.com/invite/9zTwngHAMy

Updated checklist:

• RFC-001 published (commit 50b7219)
• Vocabulary PR open on aeoess/agent-governance-vocabulary (docs: community engagement kickoff — whitepaper, tokenomics, roadmap, social drafts #11)
• Submit via https://github.com/aaif/project-proposals
• Email support@aaif.io
• Join AAIF Discord and post in governance channel

[pshkv]

AAIF project proposal submitted — April 13, 2026

aaif/project-proposals#12

Full checklist:

• RFC-001 published (commit 50b7219)
• Vocabulary PR open on aeoess/agent-governance-vocabulary (docs: community engagement kickoff — whitepaper, tokenomics, roadmap, social drafts #11)
• AAIF project proposal submitted (aaif/project-proposals Add CONTRIBUTING.md and whitepaper outline #12)
• Email sent to support@aaif.io
• AAIF TC review scheduled
• RFC referenced in AAIF docs

[pshkv]

Ecosystem engagement complete — April 13, 2026

Full thread sweep across all 17 unread notifications. Summary:

Replies posted:

• Proposal: entity_continuity and consent_provenance signal types for embodied AI identity aeoess/agent-governance-vocabulary#8 — entity_continuity + consent_provenance mapping to SINT physical constraint layer. Proposed migration_attestation field for ConstraintEnvelope.
• RFC: Authorization layer for A2A AgentSkill invocations — capability token enforcement at skill boundaries a2aproject/A2A#1716 — delivered enclave-mapping.ts (commit 99b1f74), asked 64R3N for WTRMRK endpoint
• Cross-org, no shared AS: accountability layer for first-contact A2A transactions a2aproject/A2A#1713 — proposed dual-sig extension to SINT receipts (agent_sig + gateway_sig + acta_ref), closes accountability property Milestone: gRPC bridge adapter #3
• a2aproject/A2A discussions#1404 — positioned RFC-001 as enforcement annex to SEP capability negotiation
• Proposal: Agent Identity Verification for Multi-Agent Crews crewAIInc/crewAI#5019 — APS + SINT integration sketch for multi-agent crews
• Feature: Agent trust verification via MoltBridge for cross-org multi-agent scenarios microsoft/autogen#7525, #7492, #7528 — governance layer reference, payment architecture, capability-scoped tool auth
• On-chain agent identity as a governance primitive microsoft/agent-governance-toolkit#772 — on-chain identity bridging pattern, ERC-8004 + APS + SINT layered
• 📝 Blog Post: Building Trust Between AI Agents — DIDs, Signatures, and Zero-Trust Mesh microsoft/agent-governance-toolkit#850 — offered to write blog post on cryptographic convergence, proposed co-authorship with AGT team
• Proposal: agent-governance-vocabulary — canonical naming layer over existing governance specs aeoess/agent-passport-system#13 — referenced RFC-001 + vocabulary PR, asked about migration attestation primitives

Code shipped:

• packages/bridge-a2a/src/enclave-mapping.ts (commit 99b1f74) — Enclave permission model to SINT capability token bidirectional mapping with monotonic narrowing enforcement

Open commitments tracking:

• 64R3N WTRMRK endpoint details (blocking plugin-wtrmrk-attestation)
• Draft PR: dual-sig receipt extension (agent_sig + acta_ref fields)
• Blog post draft for 📝 Blog Post: Building Trust Between AI Agents — DIDs, Signatures, and Zero-Trust Mesh microsoft/agent-governance-toolkit#850
• crosswalk/sint.yaml update: add entity_continuity + consent_provenance entries
• MolTrust joint fixture test (4 vectors in conformance-tests/fixtures/interop/)
• A2A SEP: RFC-001 as enforcement annex contribution

[pshkv]

Treating this as part of the current credibility lane alongside #127 and #125.

The value of keeping this open and explicit is that external standards progress is visible in the repo while #128 carries the main engineering story.

[pshkv]

Suggested definition of done for this thread:

• AAIF email sent
• response captured here, even if it is only acknowledgment
• any requested edits or follow-up tasks broken out explicitly
• final AAIF reference or mention linked back here

That keeps the standards trail legible to anyone evaluating whether SINT is actually participating in governance work or just claiming alignment.