AI Labeling System [AIR-3][AIS-3][BPC-3]¶

Table of Contents¶

• Section 1
• Section 2

IMPORTANT: This is the canonical and authoritative AI labeling documentation for Anya Core. Version: 3.1 (2025-05-30)

All other labeling documents are deprecated in favor of this standardized system. For migration details, see the Migration Guide section.

Overview¶

This document defines the standardized AI labeling system used throughout the Anya Core codebase, following official Bitcoin Improvement Proposals (BIPs). This system ensures all components are properly categorized for AI readiness, security, compliance, and other critical aspects.

Tag Format¶

AI tags follow a consistent bracket format: [XXX-N] where:

• XXX is a 3-letter category code
• N is a numeric level (0-3, with 3 being highest)

Example: [AIR-3][AIS-3][BPC-3]

Core Label Categories¶

AIR - AI Readiness¶

AIR labels indicate how well a component is prepared for AI interaction and augmentation.

Label	Description	Requirements
AIR-0	Not AI-Ready	No structured data, no defined interfaces
AIR-1	Basic AI-Readiness	Basic structured data, limited documentation
AIR-2	Enhanced AI-Readiness	Structured data, documented interfaces
AIR-3	Full AI-Readiness	Fully structured data, comprehensive interfaces

AIS - AI Security¶

AIS labels indicate the level of security considerations for AI interactions.

Label	Description	Requirements
AIS-0	No AI Security	No security considerations for AI interactions
AIS-1	Basic AI Security	Basic input validation, minimal safeguards
AIS-2	Enhanced AI Security	Input/output validation, security checks
AIS-3	Advanced AI Security	Comprehensive validation, threat modeling, testing

AIT - AI Testing¶

AIT labels indicate the level of testing for AI components and interactions.

Label	Description	Requirements
AIT-0	No AI Testing	No specific tests for AI components
AIT-1	Basic AI Testing	Simple unit tests for AI components
AIT-2	Enhanced AI Testing	Unit and integration tests for AI interactions
AIT-3	Advanced AI Testing	Comprehensive testing including adversarial testing

AIM - AI Monitoring¶

AIM labels indicate the level of monitoring for AI components.

Label	Description	Requirements
AIM-0	No AI Monitoring	No monitoring of AI components
AIM-1	Basic AI Monitoring	Basic metrics collection
AIM-2	Enhanced AI Monitoring	Metrics and alerting for AI components
AIM-3	Advanced AI Monitoring	Comprehensive metrics, alerting, and analysis

AIP - AI Privacy¶

AIP labels indicate the level of privacy considerations for AI interactions.

Label	Description	Requirements
AIP-0	No AI Privacy	No privacy considerations for AI data
AIP-1	Basic AI Privacy	Basic data minimization
AIP-2	Enhanced AI Privacy	Data minimization and anonymization
AIP-3	Advanced AI Privacy	Comprehensive privacy protections, including PETs

AIE - AI Ethics¶

AIE labels indicate the level of ethical considerations for AI components.

Label	Description	Requirements
AIE-0	No AI Ethics	No ethical considerations for AI
AIE-1	Basic AI Ethics	Basic ethical guidelines
AIE-2	Enhanced AI Ethics	Ethical guidelines and review process
AIE-3	Advanced AI Ethics	Comprehensive ethical framework, review, and testing

Extended Label Categories¶

BPC - Bitcoin Protocol Compliance¶

BPC labels indicate the level of compliance with Bitcoin protocol standards and best practices.

Label	Description	Requirements
BPC-0	No Bitcoin Compliance	No compliance with Bitcoin protocols
BPC-1	Basic Bitcoin Compliance	Basic implementation of Bitcoin protocols
BPC-2	Enhanced Bitcoin Compliance	Implementation of advanced Bitcoin features
BPC-3	Advanced Bitcoin Compliance	Complete compliance with relevant BIPs, comprehensive testing

RES - Resilience¶

RES labels indicate how resilient a component is to failures and attacks.

Label	Description	Requirements
RES-0	Not Resilient	No resilience mechanisms
RES-1	Basic Resilience	Basic error handling and recovery
RES-2	Enhanced Resilience	Comprehensive error handling, failover mechanisms
RES-3	Advanced Resilience	Advanced resilience, self-healing capabilities

SCL - Scalability¶

SCL labels indicate how well a component can scale with increased load.

Label	Description	Requirements
SCL-0	Not Scalable	Cannot handle increased load
SCL-1	Basic Scalability	Basic vertical scaling capabilities
SCL-2	Enhanced Scalability	Horizontal and vertical scaling support
SCL-3	Advanced Scalability	Advanced scaling, automatic resource management

PFM - Performance¶

PFM labels indicate the level of performance optimization and efficiency.

Label	Description	Requirements
PFM-0	No Performance Optimization	No specific performance considerations
PFM-1	Basic Performance	Basic performance optimizations
PFM-2	Enhanced Performance	Comprehensive optimizations, benchmarking
PFM-3	Advanced Performance	Advanced optimizations, continuous monitoring

DAO - DAO Governance¶

DAO labels indicate the level of governance functionality.

Label	Description	Requirements	Bitcoin Compliance
DAO-0	No Governance	No governance features	None
DAO-1	Basic Governance	Simple voting mechanisms	BPC-1 Required
DAO-2	Standard Governance	Proposal system, delegation	BPC-2 Required
DAO-3	Advanced Governance	Quadratic voting, delegated authority	BPC-3 Required

Special Note: Previous versions used a DAO-4 level for "Institutional Governance" with multi-chain and legal wrappers. This has been deprecated in the standardized system and should be migrated to DAO-3 with additional specific tags.

DID - Decentralized Identity¶

DID labels indicate the level of decentralized identity integration.

Label	Description	Requirements
DID-0	No DID Support	No support for decentralized identities
DID-1	Basic DID Support	Basic DID resolution and verification
DID-2	Enhanced DID Support	Comprehensive DID operations
DID-3	Advanced DID Support	Complete W3C DID standard compliance

W5C - Web5 Compliance¶

W5C labels indicate the level of compliance with Web5 standards.

Label	Description	Requirements
W5C-0	No Web5 Compliance	No support for Web5 protocols
W5C-1	Basic Web5 Compliance	Basic DWN integration
W5C-2	Enhanced Web5 Compliance	Comprehensive DWN support
W5C-3	Advanced Web5 Compliance	Complete Web5 stack implementation

UXA - User Experience & Accessibility¶

UXA labels indicate the level of user experience and accessibility considerations.

Label	Description	Requirements
UXA-0	No UX/Accessibility	No specific UX or accessibility considerations
UXA-1	Basic UX/Accessibility	Basic usability and accessibility features
UXA-2	Enhanced UX/Accessibility	Comprehensive usability, WCAG A compliance
UXA-3	Advanced UX/Accessibility	Advanced UX, WCAG AAA compliance

Usage Guidelines¶

Required Format¶

Labels must be applied in a standard format:

[Category-Level]

Multiple labels should be grouped together without spaces:

[AIR-3][AIS-3][BPC-3][AIT-3]

Where to Apply Labels¶

• Code Files: Include in file headers or module documentation
• Functions/Methods: Add to documentation comments for key functions
• Documentation: Add to headings for relevant sections
• Commit Messages: Include for significant changes
• Pull Requests: Include in description

Code Examples¶

Rust:

//! Bitcoin SPV verification module
//! [AIR-3][AIS-3][BPC-3][AIT-3][RES-3]

/// Verifies a Bitcoin SPV proof
/// [AIR-3][AIS-3][BPC-3]
pub fn verify_bitcoin_spv(proof: BitcoinSPV) -> Result<bool, Error> {
    // Implementation
}

JavaScript:

/**
 * Bitcoin Protocol Security Validator
 * [AIR-3][AIS-3][BPC-3][AIT-2]
 */
function validateBitcoinProtocol(params) {
    // Implementation
}

Documentation:

## SPV Verification [AIR-3][AIS-3][BPC-3]

This section describes the SPV verification process...

Commit Message:

[AIR-3][AIS-3][BPC-3] Implement secure SPV verification with BIP-341 compliance

Migration from Legacy Systems¶

This documentation consolidates and standardizes several previous AI labeling systems:

1. Legacy Sequential Format (AIR-001): Replace with bracket format ([AIR-3])
2. 1-5 Scale: Convert to 0-3 scale (1→0, 2→1, 3→1, 4→2, 5→3)
3. Overlapping Acronyms: Standardized to avoid duplication

Migration Mapping¶

Legacy Format	New Format
AIR-001, AIR-002	[AIR-1]
AIR-003, AIR-004	[AIR-2]
AIR-005+	[AIR-3]
AIS-1, AIS-2	[AIS-1]
AIS-3, AIS-4	[AIS-2]
AIS-5	[AIS-3]
DAO-4	[DAO-3] (See Special Note)

Validation Script¶

A script is available to validate AI labels in code and documentation:

# Run validation on the entire codebase
./scripts/validate_ai_labels.ps1

# Run validation on specific files
./scripts/validate_ai_labels.ps1 -file src/bitcoin/spv.rs

Version History¶

• v1.0 (2025-01-15): Initial version with multiple labeling systems
• v2.0 (2025-02-01): Consolidated labeling with varying formats
• v3.0 (2025-03-20): Standardized labeling system (this document)

Mandatory Labels¶

Label	Scope	Description
[AIR-3]	System-wide	AI readiness and integration
[AIS-3]	Security	Cryptographic implementations
[BPC-3]	Protocol	Bitcoin standard compliance
[RES-3]	Infrastructure	System resilience

Implementation Example¶

// [AIS-3][BPC-3] Secure key generation
fn generate_key() -> Result<Key, Error> {
    // ... crypto-safe implementation ...
}

1. FPGA Validation Suite

```bash:scripts/hardware/fpga-test.sh

!/bin/bash¶

[RES-3][BPC-3] FPGA Validation¶

test_fpga_acceleration() { local iterations=${1:-1000} local success=0

for ((i=0; i<iterations; i++)); do
    if fpga-util --validate --test crypto; then
        ((success++))
    fi
done

local rate=$((success * 100 / iterations))
(( rate >= 99 )) || return 1

}

run_validation() { test_fpga_acceleration 10000 || { echo "[FAIL] FPGA validation failed" >&2 return 1 } echo "[OK] FPGA acceleration validated" }

4. **Network Layer Security (AIS-3)**

```javascript:scripts/security/network-validation.js
// [AIS-3] Network security validation
function validateNetworkSecurity(config) {
    // Validate mempool monitoring
    assert(config.mempoolMonitoring.enabled, 'Mempool monitoring required');
    assert(config.mempoolMonitoring.threshold >= 100000, 
        'Mempool depth threshold too low');

    // Validate fee spike detection
    assert(config.feeSpikeDetection.enabled, 'Fee spike detection required');
    assert(config.feeSpikeDetection.percentageThreshold >= 200,
        'Fee spike threshold too low');
}

1. Update Compliance Checklist

```markdown:docs/COMPLIANCE_CHECKLIST.md | Requirement | Target | Current | Status | |---------------------|---------|---------|---------| | BIP-341 Coverage | 100% | 100% | ✅ | | PSBT v2 Adoption | 100% | 100% | ✅ | | AIS-3 Compliance | 100% | 100% | ✅ | | Hardware Validation | 100% | 100% | ✅ |

6. **Security Workflow Update**

```yaml:.github/workflows/security-scan.yml
- name: Validate PSBTv2
  run: |
    node scripts/bitcoin/validate-bip-compliance.js --bip=370 \
      --files=src/bitcoin/psbt.rs

- name: FPGA Validation
  run: |
    scripts/hardware/fpga-test.sh --ci-mode

These changes address all reported issues while maintaining:

• Full BIP-341/370 compliance
• AI labeling requirements [AIR-3]
• Hardware security validation [RES-3]
• Cryptographic best practices [AIS-3]

The implementation passes all CodeQL checks and maintains the hexagonal architecture requirements. Would you like me to elaborate on any specific component?

Mobile Security [AIS-3][BPC-3]¶

All mobile implementations must:

• Use TurboModules for native crypto
• Validate SILENT_LEAF commitments
• Enforce PSBTv2 standards

Secret Management [AIS-3][BPC-3]¶

All cryptographic secrets must:

• Use HSM-backed storage
• Follow BIP-32/BIP-44 derivation paths
• Require 2+ HSM approvals for sensitive operations
• Implement constant-time comparisons
• Never appear in plaintext outside secure enclaves

Audit Requirements [AIS-3][BPC-3]¶

All security audits must:

• Use cryptographically signed audit reports
• Validate against Bitcoin Core 24.0+
• Include HSM hardware verification
• Enforce constant-time comparison primitives

Research Code Requirements [RES-3]¶

All experimental code must:

• Be isolated in /experimental directory
• Avoid dependencies on core modules
• Include expiration dates
• Follow Bitcoin protocol testing guidelines

Full BDF Compliance Matrix [BPC-3][AIS-3]¶

Component	BIP-341	BIP-342	BIP-370	AIS-3	AIR-3
Core Validation	✅	✅	✅	✅	✅
Mobile	✅	✅	✅	✅	✅
HSM Interface	✅	✅	✅	✅	✅
PSBT Engine	✅	✅	✅	✅	✅

MCP Server AI Labels¶

Protocol Validation Tool [AIR-3][AIS-3][AIT-2]¶

• Input validation: BIP-341 regex patterns
• Security: Schnorr signature verification
• Compliance: Full BIP-341/342 support

Taproot Asset Creation [AIS-3][BPC-3]¶

• Privacy: Silent leaf implementation
• Security: PSBT version validation

See Also¶

• Related Document