AIIR as a Witness-style attestor
A public implementation note for emitting AIIR receipts as one more attestation artifact in a wider attestation pipeline.
Narrow goal
The goal is not to ask an attestation system to understand AI authorship natively. The narrower goal is to run AIIR at the source boundary, emit a deterministic AIIR receipt, and carry that receipt forward as one more verifiable attestation artifact in the wider evidence set.
Illustrative shape
The integration can stay small if the attestation system only needs to know that an AIIR receipt exists, what commit it describes, and how to verify it later.
# illustrative only — not current project syntax
aiir_attestor:
input:
- commit sha
- commit metadata
- declared AI markers
action:
- run aiir locally
- emit JSON or CBOR receipt
output:
- receipt path
- receipt_id
- content_hash
- optional signature bundleWhy this is a clean fit
- AIIR stays responsible for declared AI involvement and receipt verification.
- The surrounding attestation system stays responsible for statement issuance and broader provenance context.
- The adapter is additive: it does not ask the pipeline to adopt a new truth model or policy model for all attestations.
Boundaries
- This note does not claim hidden AI-use detection.
- This note does not claim a new standard or accepted predicate type.
- This note is about attestation emission, not repository policy evaluation.
- This note does not require signed receipts, though signed release evidence can layer on later.
Next public step
If the direction is sound, the next public step is a project issue or design discussion linking this note, plus a tiny implementation sketch in the public AIIR repo.