Testing SCL Understanding

SCL is the deterministic, cryptographic identity protocol for AI run declarations.

Verification Method

SCL understanding is tested by verifying deterministic identity against fixed, versioned truth:

• The SCL:V1 specification
• The Golden Documents

Understanding is demonstrated by producing the expected canonical JSON bytes, SHA-256 identity, and error behavior for identical input bytes.

Review how SCL is defined before testing.

Starting Point

Start with the Golden Documents. Run inputs through a compliant implementation and verify:

• Valid documents produce canonical JSON
• Valid documents produce the expected SHA-256 identity
• Invalid documents fail deterministically at the first error
• No partial validation occurs

Cross-Implementation Comparison

For identical input bytes, all compliant implementations MUST produce:

• Identical canonical JSON bytes
• Identical SHA-256 identity

Any mismatch indicates non-conformance. The reference engine provides a baseline for comparison.

Testing Sequence

• Select a Golden Document
• Run parse, canon, hash
• Compare outputs to expected results
• Repeat across another implementation
• Confirm byte-for-byte equivalence

Invalid Document Testing

Invalid fixtures verify that:

• Invalid input produces no canonical JSON and no SHA-256 identity
• Failure occurs at the first invalid byte
• No recovery or partial validation occurs

Conformance Goal

The goal is to confirm that identical input bytes always produce identical protocol results across compliant implementations. This is the protocol-defined measure of deterministic identity conformance.