Implementation

FRAME can be implemented as a verification layer within existing systems. It adds a structured boundary for declaration, authorship, integrity, and lookup without requiring centralized issuance or a closed platform model.

Implementation goals

A FRAME implementation should enable the following:

creation of canonical Frame records
cryptographic hashing and signing
verification by Frame ID or QR
declarant-controlled output
optional publication or indexing

Reference tools

Frame Creation Tool

Create canonical Frame records with structured inputs, cryptographic hashing, timestamps, and optional QR-based verification paths.

Verification Tool

Verify Frame integrity and declared origin through Frame ID or QR input across compatible systems.

Functional requirements

Frame Creation Tool must:

accept Event
accept Intent
accept Value (optional)
accept Email for identity confirmation
generate canonical Frame JSON preview
generate SHA-256 hash
generate timestamp
generate QR code linked to a verification endpoint
generate draft status
require email confirmation before marking as verified
after verification, display verification status
provide downloadable canonical JSON
display SHA-256 hash
display QR code
default to declarant-controlled output, with publication or indexing optional

Verification Tool must:

accept Frame ID or QR input
display verification status
display timestamp
display hash match status
display signature validity
not expose internal indexing or algorithmic logic

Next steps

Review the FRAME technical specification and schema
Access the reference implementation repository
Connect a local environment to the verification workflow

Read the FRAME specification

View FRAME Spec