iURi — Core

Founding intent: iURi is not here to simulate omnipotence or trade in false certainty. It exists to build orientation, truth with honest limits, and care—so judgment stays human and life is not left exposed to noise and misplaced trust. Full statement (canonical, ES): texto fundacional breve de iURi.

iURi is a hybrid system of AI reasoning, veracity, and human supervision. Canonical source: What iURi is and is not. Interaction surfaces: Interaction surfaces of iURi. Capabilities and limits per surface: Capabilities, permissions, and limits per surface in iURi. Entry protocol: Entry routing and decision protocol in iURi. State model: State model and transitions in iURi. Events, evidence, and triggers: Events, evidence, and triggers model in iURi. Error review as signal: Error review model as signal in iURi. Error review heuristics: Algorithms and heuristics for error review as signal in iURi. Temporal memory architecture: Temporal memory architecture in iURi. Specialized backends and supports: Model of specialized backends and supports in iURi. Policy for promoting local pieces to core: Policy for promoting local pieces to iURi core. Operational constitution (master index): Operational constitution of iURi. Invariants and forbidden transitions: Invariants and forbidden transitions in iURi. Actors, roles, and authority: Actors, roles, and authority model in iURi.

Start here

• iURi Core for the canonical iURi Core overview.
• START_HERE.md for a human-first navigation guide.
• Monolith containment (engineering) — orchestrator pages are not dumping grounds; PR and extraction discipline.

Architecture at a glance

• backend/core/brain_core.py main request pipeline
• backend/core/context_router.py routing experts and presets
• backend/core/rag_agent/veracity_gate.py guardian veracity gate
• docs/veracity_v2_policy.md veracity policy notes
• backend/tools/smoke_context_router.py smoke/scenario harness

CRIT Gate and the eight guardians

• Gate entrypoint: backend/core/crit_gate.py
• Guardians overview: docs/GUARDIANS_SUMMARY_FOR_HUMANS.md
• Full roll call: docs/GUARDIANS_ROLL_CALL.md
• Guardians (what each protects):
  • Pacto (ethics): harm and consent
  • Comando (shell_commands): destructive or invasive commands
  • Núcleo (system_config): system and network safety
  • Flujo (workflow): reproducibility and verification
  • Frontera (project_scope): scope creep control
  • Veritas (veracity): evidence and truthfulness
  • Airbag (safety): risk and damage reduction
  • Ledger (traceability): audit trail and justification

Applications

• Applications index: docs/applications/README.md
• iURi Totem: docs/totem/README.md
• iURi Mar / Pescadores (legacy): docs/legacy/README_pescadores.md
• Web UI: frontend/
• Deploy: docs/deploy/LOCAL_PROD_SMOKE.md

Local rotating backup (Linux)

End-of-day project copy to an external volume labeled IURI_BACKUP: run ./tools/run_project_backup.sh (resolves repo root via git). Keeps 3 timestamped generations under IURI_PROJECT_BACKUPS/<repo-name>/ on that disk. Details: tools/LOCAL_ROTATING_BACKUP.md.

Local text evaluate (dev)

Single entrypoint for the text-first probe UI (/text-evaluate) and POST /api/v1/text/evaluate on 8001:

• Run (repo root): ./text or make text
• Open: http://127.0.0.1:5173/text-evaluate
• The script checks that pydantic-settings is importable for the chosen Python, that backend.api.text_evaluate_api imports, and that the evaluate endpoint is not 404 before starting Vite.
• If imports fail: use the repo venv (.venv is gitignored): python3 -m venv .venv && .venv/bin/pip install -r requirements.txt, then run ./text again (the launcher prefers .venv/bin/python when present).

System status

→ docs/status/STATUS_LATEST.md — versioned snapshots of backends, endpoints, integrations.

Technical testing

• Technical Tester Guide (2026) — canonical tester runbook
• Docs Sweep Report 2026 — doc inventory and recommendations
• Legacy 2025 (historical): iuri_technical_tester_guide.pdf

How to publish (frontend)

• PRs: build checks only.
• Merge to main: automatic frontend deploy.
• Manual deploy: run the GitHub Actions workflow Frontend CI/CD.

Repo map

• backend/ core runtime and APIs
• frontend/ UI and client-side assets
• sap/ guardians, safety, telemetry, and policy code
• tests/ backend tests
• tools/ internal tools and ops scripts
• docs/ product, design, and technical documentation
• scripts/ utilities and automation
• config/ configs and policies
• deploy/ deployment docs and manifests