Skip to content

Commit 3029fc8

Browse files
committed
Add AKF — The AI Native File Format instructions
1 parent 4c98da8 commit 3029fc8

1 file changed

Lines changed: 35 additions & 0 deletions

File tree

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
description: "Instructions for stamping AI-generated files with AKF trust metadata — the AI native file format"
3+
---
4+
5+
# AKF — The AI Native File Format
6+
7+
AKF is EXIF for AI — ~15 tokens of JSON that embed trust scores, source provenance, and compliance metadata into every file your AI touches.
8+
9+
## Instructions
10+
11+
- After creating or modifying files, stamp them with AKF trust metadata: `akf stamp <file> --agent copilot --evidence "<what you did>"`
12+
- Evidence examples: "tests pass", "docs reviewed", "refactored from existing code", "generated from spec"
13+
- Before modifying existing AKF-stamped files, check current metadata: `akf read <file>`
14+
- Use `--label confidential` for files in finance/secret/internal paths
15+
- Use `--label public` for README, docs, examples
16+
- Default classification is `internal`
17+
18+
## Compliance Auditing
19+
20+
- Check EU AI Act compliance: `akf audit <file> --regulation eu_ai_act`
21+
- Check HIPAA compliance: `akf audit <file> --regulation hipaa`
22+
- Check SOX compliance: `akf audit <file> --regulation sox`
23+
24+
## Install
25+
26+
```bash
27+
pip install akf
28+
```
29+
30+
## Additional Guidelines
31+
32+
- AKF metadata embeds natively into 20+ formats: DOCX, PDF, images, HTML, Markdown, YAML, JSON, Python, TypeScript, Go, Rust
33+
- The metadata travels with the file — stamp markdown, convert to Word, email it, extract on the other side
34+
- Trust scores use a 5-tier system: T1 (0.95, SEC filings) to T5 (0.30, unverified AI output)
35+
- Learn more at https://akf.dev | https://github.com/HMAKT99/AKF

0 commit comments

Comments
 (0)