# AI Cyber Security Research — Project Rules

This project is **fully self-contained**. Treat it as an isolated workspace with no inherited context.

## Isolation

- Do **not** import, reference, or assume knowledge from other projects, repositories, or prior sessions.
- Do **not** use cross-session memory. All context lives inside this repository.
- When uncertain, read files in this repo — never guess from outside experience.
- Participant identities, expertise, and deliberation history are defined only under `participants/` and `sessions/`.

## Primary Workflow

1. **Record participants** — add or update profiles in `participants/` using `_template.md` as the schema.
2. **Update the roster** — register each participant in `roster.yaml`.
3. **Convene the boardroom** — run `/boardroom` with a research question or topic.
4. **Verify evidence** — capture every cited source in `output/references/articles/` (MD/LaTeX/PDF).
5. **Record votes** — formal ballots with per-dissenter rationale in `sessions/VOTE-RECORD.md`.
6. **Regenerate outputs** — full pipeline in `PROJECT.md`; commit after each step.

## Category Layout

| Category | Path |
|----------|------|
| Participants | `participants/` |
| Sessions | `sessions/` |
| Specifications | `mvap/` |
| Reports | `output/` |
| Reference archive | `output/references/` |
| Methodology | `output/How-The-Research-Was-Done.md` |
| Materials index | `output/RESEARCH-MATERIALS-INDEX.md` |
| Governance | `PROJECT.md`, `roster.yaml`, `sessions/verification-ledger.md` |

## Conventions

- Participant profile files: `participants/<slug>.md` (lowercase, hyphenated slug).
- Session transcripts: `sessions/YYYY-MM-DD-<topic-slug>.md`.
- Formal vote record: `sessions/VOTE-RECORD.md`.
- Keep profiles factual and role-specific; avoid duplicating the same expertise across participants.
- Git: `git add -A` and commit after each logical change with a descriptive message.