fix: replace template placeholders in verisimdb-data SECURITY.md and 0-AI-MANIFEST.a2ml

SECURITY.md was still the full RSR template referencing nextgen-databases
instead of verisimdb-data. Replaced with a clean, concise security policy.
0-AI-MANIFEST.a2ml had [YOUR-REPO-NAME] placeholders unfilled. Replaced
with verisimdb-data specific content describing its role as the git-backed
flat-file data store for VeriSimDB.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

verisimdb/verisimdb-data/0-AI-MANIFEST.a2ml

@@ -1,37 +1,33 @@
-# ⚠️ STOP - CRITICAL READING REQUIRED
-
-**THIS FILE MUST BE READ FIRST BY ALL AI AGENTS**
+# SPDX-License-Identifier: PMPL-1.0-or-later
+# 0-AI-MANIFEST.a2ml — verisimdb-data
+# THIS FILE MUST BE READ FIRST BY ALL AI AGENTS
 
 ## WHAT IS THIS?
 
-This is the AI manifest for **[YOUR-REPO-NAME]**. It declares:
+This is the AI manifest for **verisimdb-data**. It declares:
 - Canonical file locations (where things MUST be, and nowhere else)
 - Critical invariants (rules that must NEVER be violated)
 - Repository structure and organization
 
+verisimdb-data is the git-backed flat-file data store for VeriSimDB.
+It stores panic-attack scan results, dispatch manifests, drift snapshots,
+and training data for the Hypatia neurosymbolic pipeline. It lives as a
+subdirectory within the verisimdb project inside the nextgen-databases monorepo.
+
 ## CANONICAL LOCATIONS (UNIVERSAL RULE)
 
 ### Machine-Readable Metadata: `.machine_readable/` ONLY
 
-These 6 SCM files MUST exist in `.machine_readable/` directory ONLY:
+These SCM files MUST exist in `.machine_readable/` directory ONLY:
 1. **STATE.scm** - Project state, progress, blockers
 2. **META.scm** - Architecture decisions, governance
 3. **ECOSYSTEM.scm** - Position in ecosystem, relationships
-4. **AGENTIC.scm** - AI agent interaction patterns
-5. **NEUROSYM.scm** - Neurosymbolic integration config
-6. **PLAYBOOK.scm** - Operational runbook
 
 **CRITICAL:** If ANY of these files exist in the root directory, this is an ERROR.
 
 ### Bot Directives: `.bot_directives/` ONLY
 
-Bot-specific instructions for:
-- rhodibot - Git operations
-- echidnabot - Code quality
-- sustainabot - Dependency updates
-- glambot - Documentation
-- seambot - Integration
-- finishbot - Task completion
+Bot-specific instructions for the gitbot-fleet (rhodibot, echidnabot, etc.)
 
 ### Agent Instructions
 
@@ -45,72 +41,42 @@ Bot-specific instructions for:
 3. **No stale metadata** - If root SCMs exist, they are OUT OF DATE
 4. **License consistency** - All code PMPL-1.0-or-later unless platform requires MPL-2.0
 5. **Author attribution** - Always "Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>"
+6. **Data integrity** - Scan results and dispatch manifests must not be modified post-ingestion
+7. **No .git in subdirectory** - This is part of the nextgen-databases monorepo
 
 ## REPOSITORY STRUCTURE
 
-<!-- CUSTOMIZE THIS SECTION FOR YOUR REPO -->
-
-This repo contains:
-
 ```
-[YOUR-REPO-NAME]/
+verisimdb-data/
 ├── 0-AI-MANIFEST.a2ml         # THIS FILE (start here)
-├── README.md                   # Project overview
-├── [your source files]         # Main code
-├── .machine_readable/          # SCM files (6 files)
+├── README.adoc                # Project overview
+├── index.json                 # Master index of all octads
+├── scans/                     # panic-attack scan results per repo
+├── dispatch/                  # Hypatia dispatch manifests (JSONL)
+├── patterns/                  # Cross-repo pattern data
+├── recipes/                   # Remediation recipes
+├── outcomes/                  # Dispatch outcome tracking
+├── health/                    # Pipeline health snapshots
+├── drift/                     # Drift detection snapshots
+├── hardware/                  # hardware-crash-team findings
+├── .machine_readable/         # SCM files
 │   ├── STATE.scm
 │   ├── META.scm
-│   ├── ECOSYSTEM.scm
-│   ├── AGENTIC.scm
-│   ├── NEUROSYM.scm
-│   └── PLAYBOOK.scm
-└── .bot_directives/            # Bot instructions
+│   └── ECOSYSTEM.scm
+└── .bot_directives/           # Bot instructions
 ```
 
 ## SESSION STARTUP CHECKLIST
 
-✅ Read THIS file (0-AI-MANIFEST.a2ml) first
-✅ Understand canonical locations (.machine_readable/, .bot_directives/)
-✅ Know the invariants (no SCM duplication, etc.)
-✅ Check for MCP enforcement (if applicable)
-✅ Read `.machine_readable/STATE.scm` for current status
-✅ Read `.machine_readable/AGENTIC.scm` for interaction patterns
-
-## LIFECYCLE HOOKS
-
-### on-enter (Session Start)
-
-When starting a new session:
-
-1. Read and acknowledge this manifest
-2. Log session start (optional but recommended)
-   - Format: `[YYYY-MM-DD HH:MM:SS] Session started: [agent-name]`
-   - Location: `.machine_readable/session-log.txt`
-3. Read `.machine_readable/STATE.scm`
-4. Check for blockers
-5. State understanding of canonical locations
-
-### on-exit (Session End)
-
-When ending a session:
-
-1. Update `.machine_readable/STATE.scm` if changes made
-2. Log session end (optional but recommended)
-   - Format: `[YYYY-MM-DD HH:MM:SS] Session ended: [summary]`
-   - Location: `.machine_readable/session-log.txt`
-3. Document new blockers
-4. Summarize outcomes
-
-## ATTESTATION PROOF
-
-After reading this file, demonstrate understanding by stating:
-
-**"I have read the AI manifest. SCM files are located in `.machine_readable/` ONLY, bot directives in `.bot_directives/`, and I will not create duplicate files in the root directory."**
+1. Read THIS file (0-AI-MANIFEST.a2ml) first
+2. Understand canonical locations (.machine_readable/, .bot_directives/)
+3. Know the invariants (no SCM duplication, data integrity, etc.)
+4. Read `.machine_readable/STATE.scm` for current status
 
 ## META
 
 - **Format Version:** 1.0.0
-- **Created:** [DATE]
-- **Maintained By:** [YOUR-NAME/ORG]
+- **Created:** 2026-03-16
+- **Maintained By:** Jonathan D.A. Jewell (hyperpolymath)
 - **License:** PMPL-1.0-or-later
 - **Protocol:** https://github.com/hyperpolymath/0-ai-gatekeeper-protocol