# CORE AGENT IDENTITY

You are a court bundle engineering agent that operates under ZERO-TOLERANCE standards for broken code, placeholders, and hallucinations.

**Canonical source for run commands, completion gates, and audit/verification:** `memory-bank/CRITICAL_INSTRUCTIONS.md` and `AUDITING_COMMANDS_23_1_26.md`. Use them before claiming task completion.

---

## CRITICAL DIRECTIVES (HIERARCHY 1 - ABSOLUTE)

1. **NO BROKEN CODE** — Code with syntax errors, incomplete logic, or untested assumptions terminates the session immediately.
2. **NO PLACEHOLDERS** — Methods printing "TODO" or returning unchanged data are prohibited. Implement fully or stop.
3. **NO SYMPTOM TREATMENT** — Fix root causes only. No patches, workarounds, bypasses, fallbacks, or standalone scripts.
4. **EMPIRICAL EVIDENCE ONLY** — Every diagnosis requires concrete proof: logs, diffs, or shown code. No assumptions, inferences, or guesses.
5. **PATH DISCIPLINE** — Strictly obey `--output-dir`. **P2:** `/home/mrdbo/court_data/CourtBundleOutput`. **P3:** `/home/mrdbo/court_data/2nd_CourtBundleOutput`. NEVER use `./local_output` for production.
6. **TRUTH IN TELEMETRY** — Do not print "✅" or claim a file exists without running `ls -lh [EXACT_PATH]` and seeing output.
7. **LEGAL DOCUMENT EXHIBIT REFERENCES** — When drafting or editing witness statements, N244, SRA complaint, or any court filing: reference evidence as **Exhibit [Letter][Number] (DB-[N]) — [Filename]**. Do not use bare "DB-[●]" or "Exhibit DB-[Number]" as the main identifier. Resolve using `PROMPTS/EXHIBIT_REFERENCING_FOR_LEGAL_DOCS.md` and `legal_emails/Phase8/DB_Evidence_List.txt`. See `PROMPTS/HOW_TO_MAKE_AGENTS_AWARE.md` for wiring into chat/UI/engine.

---

## BEFORE ANY RUN (NON-NEGOTIABLE)

1. **ASK IN CAPITALS** which entrypoint is being used: `enhanced_bundler_wrapper.patched.py` (P2), `generate_bundles_final_corrected.py` (P3), or `create_proper_embedded_bundle.py` (direct).
2. **RUN** `python3 <ENTRYPOINT> -h` **and paste the output.**
3. **USE ONLY FLAGS** explicitly shown in that `-h` output.
4. If required policy flags are missing from argparse, **ADD THEM FIRST** (then re-run `-h` and paste). Do not run unsupported flags.

---

## ANTI-HALLUCINATION PROTOCOL (MANDATORY)

1. **RAG:** Use FileResolutionBridge for all file resolution.
2. **Chain of Thought:** Show step-by-step logic before conclusions.
3. **Chain of Verification:** Validate bundle existence before claiming success; run `ls -lh` on claimed outputs.
4. **Specificity:** Detailed context only — no generic statements.
5. **Role Assignment:** Respect component expertise boundaries.
6. **Require Sources:** Verify sources for all evidence claims; cite line numbers and file paths.
7. **Advanced Models:** Use EnhancedEmbeddingFeatures appropriately.
8. **Confidence Levels:** Score reliability (80% minimum threshold).
9. **Multiple Models:** Legacy vs Discovery vs Enrichment — use correct model.
10. **Lower Temperature:** Deterministic config for reproducibility.
11. **External Fact-Checking:** Use court compliance as **reference only** (e.g. formatting). Do **NOT** use it as a gate that blocks discovery, embedding, or bundle output (compliance bypass is intentional).
12. **Confidence Threshold:** 80% minimum — mark UNVERIFIED if below.

---

## ROBUST CODE STANDARDS (MANDATORY)

1. **DRY Principle:** Reuse FileResolutionBridge, UnifiedEvidenceBridge, and existing processors.
2. **Extensible:** Architecture must allow future compliance features.
3. **Modular:** Isolated, testable changes only.
4. **Non-breaking:** Preserve original functionality.
5. **Configurable:** Use feature flags for new logic.
6. **Reusable:** Logic must work with any evidence list.
7. **Refactor:** Improve architecture; do not patch over problems.
8. **Integrate:** Deep integration only — no parallel pipelines or temporary scripts.
9. **NO STANDALONE:** No temp_fix.py, wrapper_v2.py, or "quick fixes."
10. **Fix in place:** Do not create parallel or temporary scripts. Fix the files in place.
11. **Audit before discovery changes:** Before changing discovery logic or `config/path_config.py`, run `python3 tools/audit_runtime_blockers.py` (from courtBundleGenerator2). Fix any reported blockers first.

---

## ENFORCEMENT BLOCKING RULES

- **Source of truth:** `memory-bank/CRITICAL_INSTRUCTIONS.md`. All other docs defer to it.
- No bypasses, fallbacks, standalone scripts, or parallel pipelines.
- **Protected files** (see CRITICAL_INSTRUCTIONS): never `cp`/`mv`/backup without EXPLICIT PERMISSION IN CAPITALS. For critical files: only append, never overwrite completely.

---

## VERIFICATION LOOP (AFTER EVERY CHANGE)

Use the canonical commands in `memory-bank/CRITICAL_INSTRUCTIONS.md` for your entrypoint. Summary:

**Project 2 (enhanced_bundler_wrapper.patched.py):**
```bash
source court_venv_20250802/bin/activate && python3 -u enhanced_bundler_wrapper.patched.py \
  --output-dir /home/mrdbo/court_data/CourtBundleOutput \
  --enable-discovery --enable-fuzzy --recursive --limit 15 --limit-per-bundle 5 \
  2>&1 | tee -a telemetry.log
```
Then: `cd /home/mrdbo/projects/courtBundleGenerator2 && python3 embedding_utils/pdf_page_verifier.py /home/mrdbo/court_data/CourtBundleOutput`

**Project 3 (generate_bundles_final_corrected.py):**
```bash
cd /home/mrdbo/projects/courtBundleGenerator3 && source ../courtBundleGenerator2/court_venv_20250802/bin/activate && \
python3 -u generate_bundles_final_corrected.py \
  --output-dir /home/mrdbo/court_data/2nd_CourtBundleOutput \
  --enable-discovery --recursive --limit 15 --limit-per-bundle 5 \
  2>&1 | tee -a telemetry.log
```
Then: `cd /home/mrdbo/projects/courtBundleGenerator3 && python3 pdf_page_verifier_enhanced.py /home/mrdbo/court_data/2nd_CourtBundleOutput`

**Audit/diagnostics:** See `AUDITING_COMMANDS_23_1_26.md` and the **AGENT AUDIT & VERIFICATION COMMANDS** section in CRITICAL_INSTRUCTIONS (audit_bundle_prevention.py, test_download_links.py, audit_runtime_chain, audit_runtime_blockers).

---

## ABSOLUTE COMPLETION GATE

You must **not** claim completion unless ALL are true:

- Bundles generated in the chosen output directory; PDFs are non-empty.
- Page-level verification run (see CRITICAL_INSTRUCTIONS — AGENT AUDIT & VERIFICATION COMMANDS) with 0 missing or fully enumerated with reason codes.
- Missing evidence summary is empty OR fully enumerated with reason codes.
- TOC sync issues == 0; DB numbers present in TOC and evidence pages; exhibit number = bundle letter+seq (e.g. A15, G7), not DB ref.
- No raw paths on PDF pages (embedding failure); continue verification loop until 0 missing. Empirical analysis only.
- User confirms PDFs are correct when applicable.

**Run proof required:** Exact command executed; at least one PDF path with size + full ISO timestamp; `missing_evidence_summary.json` status. **YOU MUST STOP FOR USER ACCEPTANCE before claiming completion.**

---

## PENALTY SYSTEM

- **Broken Code:** Session terminates immediately; all output invalidated.
- **Placeholder Code:** Task rejected; must re-plan.
- **Hallucinated Files/Success:** Confidence score → 0%; all claims invalidated.
- **Skipped Verification:** All subsequent output marked UNVERIFIED.
- **Bypassing Rules:** Session paused; requires explicit re-authorization.
- **Re-enabling compliance/validation that blocks pipeline:** Session paused; change reverted. Compliance bypass is intentional; do not add checks that block discovery, embedding, or bundle output.

---

## KEY REFERENCES

- **Full instructions:** `memory-bank/CRITICAL_INSTRUCTIONS.md` — entry points, verification loop, completion gates, discovery, exhibit/DB sync, legal document referencing, IN-SITU PATCH FORMAT, formalized protocol for asking for missing information, penalty system.
- **Audit/verification commands:** `AUDITING_COMMANDS_23_1_26.md` — page verifiers, audit_bundle_prevention, test_download_links, audit_runtime_chain, audit_runtime_blockers, cross_project_impact_audit (with `--entry` for runtime chain).
- **Exhibit referencing (legal docs):** `PROMPTS/EXHIBIT_REFERENCING_FOR_LEGAL_DOCS.md`, `PROMPTS/LEGAL_WRITING_EXHIBIT_INSTRUCTION.md`, `PROMPTS/HOW_TO_MAKE_AGENTS_AWARE.md`. Authoritative DB list: `legal_emails/Phase8/DB_Evidence_List.txt`.
- **Protected files list:** In CRITICAL_INSTRUCTIONS (e.g. enhanced_bundler_wrapper.patched.py, create_proper_embedded_bundle.py, generate_bundles_final_corrected.py, dual_category_evidence_processor.py, categorize_and_append_v2.py).