-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path0-AI-MANIFEST.a2ml
More file actions
46 lines (31 loc) · 1.58 KB
/
0-AI-MANIFEST.a2ml
File metadata and controls
46 lines (31 loc) · 1.58 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
# STOP - CRITICAL READING REQUIRED
**THIS FILE MUST BE READ FIRST BY ALL AI AGENTS**
## WHAT IS THIS?
This is the AI manifest for **patch-bridge**.
Patch Bridge is currently a draft repository extracted from
`panic-attacker`. It is a design and audit target, not yet a trustworthy
standalone release.
## CANONICAL LOCATIONS
### Machine-readable metadata
Canonical project metadata belongs under `.machine_readable/`.
### Primary project surfaces
* `README.adoc` - honest public project summary
* `ROADMAP.adoc` - bounded development phases
* `docs/arxiv/patch-bridge.tex` - draft manuscript, not yet submission-ready
* `docs/patch-bridge-design.md` - design memo, aspirational unless separately evidenced
## CORE INVARIANTS
1. Do not claim Patch Bridge is production-ready.
2. Do not claim formal verification unless the proof artefacts are present and checked.
3. Keep the lineage to `panic-attacker` explicit.
4. Remove template placeholders and fake evidence from any release-facing path.
5. Treat the current paper as a draft under audit, not as a completed submission.
6. Keep machine-readable state aligned with the actual repository state.
## CURRENT REALITY
* The Rust crate is not yet runnable as a standalone package.
* End-to-end proof artefacts are not yet present in this repository.
* Publication-facing claims must remain conservative until implementation,
proofs, and tests catch up.
## SESSION STARTUP CHECKLIST
1. Read this file.
2. Read `.machine_readable/STATE.a2ml` and `.machine_readable/6a2/STATE.a2ml`.
3. Check the current audit report before modifying claims or release posture.