IrsanAI-Universe

██╗██████╗ ███████╗ █████╗ ███╗   ██╗ █████╗ ██╗
██║██╔══██╗██╔════╝██╔══██╗████╗  ██║██╔══██╗██║
██║██████╔╝███████╗███████║██╔██╗ ██║███████║██║
██║██╔══██╗╚════██║██╔══██║██║╚██╗██║██╔══██║██║
██║██║  ██║███████║██║  ██║██║ ╚████║██║  ██║██║
╚═╝╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝╚═╝  ╚═══╝╚═╝  ╚═╝╚═╝

██╗   ██╗███╗   ██╗██╗██╗   ██╗███████╗██████╗ ███████╗███████╗
██║   ██║████╗  ██║██║██║   ██║██╔════╝██╔══██╗██╔════╝██╔════╝
██║   ██║██╔██╗ ██║██║██║   ██║█████╗  ██████╔╝███████╗█████╗
██║   ██║██║╚██╗██║██║╚██╗ ██╔╝██╔══╝  ██╔══██╗╚════██║██╔══╝
╚██████╔╝██║ ╚████║██║ ╚████╔╝ ███████╗██║  ██║███████║███████╗
 ╚═════╝ ╚═╝  ╚═══╝╚═╝  ╚═══╝  ╚══════╝╚═╝  ╚═╝╚══════╝╚══════╝

powered by IrsanAI - sha0001000

IrsanAI Universe — Command Center

Spec-First Multi-Agent Resonance Framework IrsanAI Universe defines protocols for high-fidelity reasoning across human prompts and cooperating AI agents. The project now operates as an implementation-ready technical system with explicit schemas, conflict-resolution logic, and measurable quality targets.

🧠 Resonance Architecture

This repository mirrors a meta-cognitive flow where sensitivity and structure co-exist:

HSP Signal Layer: preserves nuance, emotional context, and prompt texture.
Logic Wrapper Layer: converts nuanced inputs into bounded, testable protocol objects.
Resonance Loop: continuously reconciles meaning, evidence, and consensus so intent survives multi-agent transfer.

In practice, NTF captures semantic intent, LRP secures logical integrity, and PDP orchestrates perspective-level convergence.

🎯 Core Objective

Reduce semantic noise while maximizing resonance:

Noise = ambiguity, unsupported assumptions, hallucinated drift.
Resonance = preservation of user intent, evidence traceability, and agent alignment.
Target = measurable semantic fidelity of 0.98 in controlled benchmark settings.

🧩 Protocol Stack (Technical Definitions)

🧩 NTF — Neural Translation Framework

A deterministic-normalized transformation layer from user text to canonical semantic form.

Responsibilities

Normalize lexical variance (aliases, multilingual terms, abbreviations).
Extract invariant task intent.
Encode structure for downstream LRP/PDP processing.

Output Guarantees

Canonical intent object.
Confidence and provenance metadata.
Evaluability against benchmark pairs.

⚖️ LRP — Logic Resonance Protocol

An agent-to-agent transfer protocol that preserves logical constraints and suppresses hallucination through structured evidence binding.

Responsibilities

Serialize reasoning state as bounded JSON.
Attach each claim to either source evidence or derivation rule.
Enforce contradiction checks before message handoff.

⚡ PDP — Perspective-Driven Protocol

A multi-perspective consensus protocol for heterogeneous model ecosystems (e.g., Grok, Gemini, Claude).

Responsibilities

Run perspective-specialized passes on the same canonical task.
Resolve conflicts through weighted voting and synthesis-relay.
Emit final consensus with dissent trace.

📚 Technical Specs (Start Here)

Primary Spec: TECHNICAL_SPEC.md
Consensus Model: CONSENSUS_MONUMENT.md
Sync + Pages Blueprint: REPO_SYNC_AND_PAGES.md
Protocol Docs:

🌐 Project Pages & Repository Network

To support independent project visibility while keeping Universe as the central command center, this repository now tracks a dedicated sync-and-pages strategy in REPO_SYNC_AND_PAGES.md.

Project	Source Repository	Planned GitHub Page	Sync Status
Universe	https://github.com/IrsanAI/IrsanAI-Universe	https://irsanai.github.io/IrsanAI-Universe/	ACTIVE
NTF	https://github.com/IrsanAI/NTF-v1.0	https://irsanai.github.io/NTF-v1.0/	REVIEW
LRP	https://github.com/IrsanAI/IrsanAI-LRP-v1.3	https://irsanai.github.io/IrsanAI-LRP-v1.3/	REVIEW
PDP	https://github.com/IrsanAI/IrsanAI-PDP-v2.0	https://irsanai.github.io/IrsanAI-PDP-v2.0/	REVIEW

The tracked network is machine-readable via spec/repo_manifest.json and validated in CI by .github/workflows/repo-sync.yml.

REVIEW indicates repository links are tracked but still need a final canonical-sync decision (submodule vs. manifest workflow).

🗂️ Repository Layout (Spec-First)

IrsanAI-Universe/
├── README.md
├── TECHNICAL_SPEC.md
├── CONSENSUS_MONUMENT.md
├── REPO_SYNC_AND_PAGES.md
├── spec/                  # Protocol and schema artifacts (JSON schema, ADRs, formal rules)
├── examples/              # Input/output examples for NTF, LRP, PDP
├── eval/                  # Benchmark scripts, metrics, reproducibility harness
│   └── ntf_bench.py
└── src/                   # Future reference implementations

🛣️ Implementation Roadmap

Phase A — Schema Hardening

Formalize NTF canonical object schema.
Freeze LRP message templates with validation rules.
Define PDP consensus envelope and dissent representation.

Phase B — Evaluation Infrastructure

Build eval/ntf_bench.py for semantic fidelity tracking.
Curate benchmark corpus (prompt-paraphrase-intent triples).
Add pass/fail thresholds and trend reporting.

Phase C — Execution Layer

Implement protocol runtime in src/.
Integrate model adapters and replay logs.
Publish deterministic test vectors under examples/.

✅ Definition of Done

A protocol revision is considered complete when:

Schema validates against all examples.
Benchmark fidelity remains at/above target.
Consensus conflicts are reproducible and auditable.
Changes include migration notes and compatibility status.

🚀 Immediate Next Step

Read TECHNICAL_SPEC.md for exact JSON templates, benchmark methodology, and consensus rule implementation details.

🧾 LOP — Liste offener Punkte (für Weiterarbeit)

Was aus meiner Sicht noch offen ist (fachlich, nicht technisch blockiert):

Pages in den anderen Repos wirklich aktivieren (Settings → Pages).
- Aktueller Stand: IrsanAI-Universe dokumentiert die Ziel-URLs bereits, aber die Aktivierung selbst passiert pro Repository in GitHub-Settings und ist hier im Code nicht verifizierbar.
- Wie fortsetzen: In jedem Ziel-Repo unter Settings → Pages die Quelle setzen (main oder gh-pages) und anschließend die Live-URL in spec/repo_manifest.json + README-Status prüfen/aktualisieren.
Duplicate-Repos final konsolidieren (kanonisches Naming festlegen).
- Aktueller Stand: Es gibt bereits Hinweise auf mögliche Duplikate im Manifest (z. B. LRP/PDP), aber noch keine finale Konsolidierungsentscheidung.
- Wie fortsetzen: Pro Protokoll ein kanonisches Repo benennen, alternative Repos per README-Hinweis als “archived/redirected” markieren und danach Manifest/README auf nur die kanonischen Ziele bereinigen.
Optional als nächsten Schritt: automatisches Updaten von last_reviewed/sync_status via GitHub API-Job.
- Aktueller Stand: CI-Validierung für das Manifest ist vorhanden, aber die Werte werden noch manuell gepflegt.
- Wie fortsetzen: Einen geplanten Workflow ergänzen, der über die GitHub API Commit-/Release-Aktivität prüft, daraus Status ableitet (ACTIVE/STALE/DIVERGED) und bei Änderungen automatisiert einen PR mit Manifest-Update erstellt.