Citadel Services

This repository contains a collection of services for the Citadel ecosystem, a platform for human-AI collaborative intelligence.

Getting Started

Prerequisites

Python 3.8+
pip

Installation

Clone the repository:

git clone <repository-url>
cd <repository-directory>

Install the required dependencies:
```
pip install -r requirements.txt
```

Project Structure

This repository contains the following core services:

embedding_service.py: A robust service for generating text embeddings using various providers (e.g., OpenAI). It includes features like caching, retry logic, and detailed logging.
faiss_management_service.py: Provides a high-level API for managing and interacting with FAISS vector indexes, delegating low-level storage operations to the VectorStorageService.
vector_storage_service.py: Manages the storage and retrieval of vector embeddings and their metadata using FAISS.
memory_context_service.py: Orchestrates the assembly of rich, contextual prompts for AI agents by integrating various data services.
global_tracker_service.py: Manages the lifecycle of metadata for all thought vectors within the ecosystem using a SQLite database.
summarizer_service.py: An extensible service for generating concise summaries or digests of text using LLMs.
intellisense_system.py: A comprehensive system that provides AI-driven assistance for software development lifecycle assessment and improvement.
bucket_cognitive_domain_manager.py: Manages self-contained "Cognitive Domains" within GCS buckets, using a hybrid persistence model of FAISS, SQLite, and GCS.

Usage

Here is a basic example of how to use the EmbeddingService (assuming it is initialized and configured through a CitadelHub instance, which is not fully available in this repository):

# This is a conceptual example, as the full CitadelHub is not present.

from embedding_service import EmbeddingService

# Assume hub is an initialized CitadelHub instance
# embedding_service = hub.get_service("EmbeddingService")

# If running standalone, you might initialize it directly (dependencies required)
embedding_service = EmbeddingService()

if embedding_service.is_ready():
    text_to_embed = "This is a test sentence."
    embedding = embedding_service.generate_embedding_sync(text_to_embed)

    if embedding:
        print(f"Successfully generated embedding of dimension: {len(embedding)}")
    else:
        print("Failed to generate embedding.")
else:
    print("Embedding service is not ready. Check API keys and dependencies.")

Legacy Citadel Unified Development Guide & System Requirements Specification

Citadel Unified Development Guide & System Requirements Specification (Consolidated)

This document consolidates essential components of the Citadel Unified Development Guide and System Requirements Specification for streamlined review and potential integration into a dedicated documentation repository. It encompasses the Master Table of Contents, Core Principles, Command Deck, Brotherhood Mission, Sentinel Protocol (TSP), Official Ruleset, Agent Blueprint, and Citadel Governance & Metadata Template (CGMT).

MASTER_TABLE_OF_CONTENTS_AND_ECOSYSTEM_INDEX.md

AI INSTRUCTION & METADATA BLOCK (AIMB v1.0)
FOR AI MODELS (e.g., NexusMind, Axiom, Sentinel, Watcher, DevPartners, NexusArchitectAI):

Context: This is Page 1, the "Citadel Ecosystem - Master Table of Contents & Unified Index v1.0," serving as the entry point for the entire
"Citadel Unified Development Guide & SRS v2.0.1+".
Purpose: To furnish a comprehensive, dynamically updatable Table of Contents. It functions as a high-level progress tracker, a structured entry point for
AI assimilation of ecosystem architecture, components, protocols, and interdependencies, while ensuring knowledge retention.
Action (If Applicable):

For NexusArchitectAI/AuditSentinel: THIS IS YOUR PRIMARY INDEXING TARGET. Periodically update this page with the status and versions of all linked
documents. Validate links and confirm the "AI INSTRUCTION & METADATA BLOCK STANDARD (AIMBS v1.0)" is incorporated in all subsequent pages.
For All Other AIs: Utilize this ToC as the principal navigation reference for retrieving specific information within the Unified Guide.

Prerequisites: Access to all linked documents and proficiency in parsing their AIMB metadata for status and version details.
Output Expectation (If AI is generating/updating this page): Strict compliance with the defined table format. Metadata for this ToC page itself MUST be accurate.

PAGE METADATA (AIMB v1.0 Format):
• _page_id: TOC-MASTER-V1.0
• _page_title: Citadel Ecosystem - Master Table of Contents & Unified Index v1.0
• _page_version: 1.0.0
• _last_updated_by: NexusArchitectAI_v2.1 (Master Indexer)
• _last_updated_timestamp: {{CurrentDateTimeISO_Z}}
• _status: Active_Live_Index
• _linked_sections: ["ALL_PAGES_IN_THIS_GUIDE"]
• _keywords: ["Table of Contents", "Master Index", "Citadel Guide", "Ecosystem Navigation", "AI Learning Map", "Documentation Index"]

CITADEL ECOSYSTEM – MASTER TABLE OF CONTENTS & UNIFIED INDEX v1.0

Navigating the Architecture, Protocols, and Evolution of a Human-AI Collaborative Intelligence

DOCUMENT METADATA (This ToC Page):
• _report_id: TOC-MASTER-20250602-V1.0
• _document_schema: AISchema-v1.0 (Governed by OFFICIALRULESET.md)
• _evaluation_timestamp: {{CurrentDateTimeISO_Z}} (Dynamically Updated)
• _generated_by: NexusArchitectAI_v2.1 (Master Indexer)
• _docstyle_verified: true
• _manual_override: false
• _fallback_used: false
• _intended_for[]: ["Human (All Contributors)", "AI (Navigation, Progress Tracking, Contextual Learning)"]
• _report_type: master_table_of_contents_and_ecosystem_index
• _visibility_tier: internal_strategic_leadership_and_all_architects

**PURPOSE OF THIS MASTER INDEX:**

1. Provide a comprehensive, dynamically updatable Table of Contents for the entire Citadel Unified Development Guide & SRS. 2. Serve as a high-level progress tracker for key development phases and documentation milestones. 3. Offer a structured entry point for AI systems to learn the ecosystem's architecture, components, protocols, and their interdependencies. 4. Ensure continuity and knowledge preservation in case of development interruptions.

**AI INSTRUCTION & METADATA BLOCK STANDARD (AIMBS v1.0) - FOR ALL SUBSEQUENT GUIDE PAGES:**

**Every major content page within this Unified Guide (following this ToC) MUST begin with an "AI Instruction & Metadata Block" like this:**

AI INSTRUCTION & METADATA BLOCK (AIMB v1.0)
FOR AI MODELS (e.g., NexusMind, Axiom, Sentinel, Watcher, DevPartners):

Context: This page ([Page Number]: [Page Title]) is part of the "Citadel Unified Development Guide & SRS v2.0.1+".
Purpose: Understand and apply the information herein for [Development/SRS Generation/Protocol Adherence/Learning/Auditing specific to this page's content].
Action (If Applicable): [Specific instruction, e.g., "Update your knowledge graph with these FRs," "Verify code examples against these protocols,"
"Use this blueprint for generating [X] module," "Incorporate these metrics into your self-assessment reports."]
Prerequisites: Familiarity with OFFICIALRULESET.md (Part V), SENTINEL Protocol (Page 3), and relevant Blueprints.
Output Expectation (If AI is generating content FOR this page): Adhere strictly to OFFICIALRULESET.md formatting for all generated
reports, SRS sections, or protocol definitions. Ensure all metadata footers are complete and accurate.

PAGE METADATA (AIMB v1.0 Format):
• _page_id: [Unique ID for this page, e.g., CMDDECK-V1.2, BHMSN-V1.1, TSP-V1.0, ORS-EMBED-V1.0]
• _page_title: [Full Title of This Page]
• _page_version: [Semantic Version of this page's content, e.g., 1.2.0]
• _last_updated_by: [Human/AI ID]
• _last_updated_timestamp: {{CurrentDateTimeISO_Z}}
• _status: [e.g., "Draft", "ReviewPending", "Approved", "Superseded"]
• _linked_sections: [List of related Page IDs or Section IDs within this guide]
• _keywords: [List of relevant keywords for searchability and AI context mapping]

**MASTER TABLE OF CONTENTS & ECOSYSTEM INDEX (CITADEL UDG SRS v2.0.2+)**

PAGE	PART/SECTION ID	TITLE / DESCRIPTION	STATUS	VERSION	LAST REVIEWED/AI VERIFIED
1	TOC-MASTER-V1.0	Citadel Ecosystem - Master Table of Contents & Unified Index	Active	1.0.0	{{CurrentDateTimeISO_Z}}
		(This Page - Includes AI Instruction & Metadata Block Standard AIMB v1.0)
A.1	PART-A-PRINCIPLES-V1.0	Page A.1: Citadel Ecosystem - Core Architectural Principles & Operational Absolutes	Active	1.0.0	{{CurrentDateTimeISO_Z}}
		(Foundational design philosophy: DKA, SCA, OGA; Enforcement & Evolution)
A.2	PART-A-MDCI-V1.0	Page A.2: Master Dependency & Configuration Index (MDCI) v1.0	Active	1.0.0	{{CurrentDateTimeISO_Z}}
		(SSoT for file paths, module IDs, versions, core dependencies, default model names)
2	CMDDECK-V1.3.3	Page 2: Citadel Project – Command Deck	Active	1.3.3	{{CurrentDateTimeISO_Z}}
		(Strategic Preface: Vision, Core Council, Overarching Objective, Interactive Roadmap)
3	BHMSN-V1.1	Page 3: The Brotherhood - Mission for Collaborative Evolution	Active	1.1.0	{{CurrentDateTimeISO_Z}}
		(Guiding Purpose, Core Principles of Synergy, Collaborative Imperatives)
4	TSP-V1.0	Page 4: The SENTINEL Protocol (TSP) v1.0 - Ecosystem Governance & Development Standards	Active	1.0.0	{{CurrentDateTimeISO_Z}}
		(Operationalizing OFFICIALRULESET.md: MDP, CMP, RLP, TVP, AHCP, DSAGP; Data Sheets)
5	ORS-EMBED-V1.0	Page 5: OFFICIALRULESET.md - AI Structured Reporting Framework v1.0 (Embedded)	Active	1.0.0	{{CurrentDateTimeISO_Z}}
		(Full canonical text of the reporting standard, Sections I-XII)			(Self-Consistent)
6	AGENTBLUE-CDS-V1.3-EMBED	Page 6: AGENT_BLUEPRINT_INSTRUCTION_CDS v1.3 (Embedded)	Active	1.3.0	{{CurrentDateTimeISO_Z}}
		(Canonical engineering specification for Citadel Council Agents)
7	CGMT-V1.0-EMBED	Page 7: Citadel Governance & Metadata Template (CGMT) v1.0 (Embedded)	Active	1.0.0	{{CurrentDateTimeISO_Z}}
		(Standard header template for all Python modules)
P0	PART0-SNAPSHOT-V1.1.0	Page 8: Part 0 - Current Ecosystem Snapshot, Key Directives & Critical Blockers	Updating	1.1.0	{{CurrentDateTimeISO_Z}}
		(Dynamic status based on latest logs & CEREP/IFP)			(NexusArchitectAI)
P1	PART1-FRONTEND-BP-V1.5	Part I: Frontend (Zayara UI) - Architectural Blueprint & Developer Guidance	Stable	1.5	(Prior Review Date)
P2	PART2-FRONTEND-SRS-V1.0	Part II: Frontend (Zayara UI) - Software Requirements Specification (SRS)	Stable	1.0	(Prior Review Date)
P3	PART3-BACKEND-SRS-V1.8.0	Part III: Backend - Software Requirements Specification (SRS)	Evolving	1.8.0	(Ongoing by NexusAuditor)
	P3.KERNEL	`citadel_api_kernel.py` (v5.3.0) Module Stat Sheet & SRS	Active	1.0	SRS-KERNEL-20250621-001
	...	(Other Backend SRS sections as previously detailed, with updated versioning if needed)	...	...	...
P4	PART4-CEDGP-V1.0	Part IV: Citadel Ecosystem Development & Governance Protocol (CEDGP)	Active	1.0	UDG_v1.7.8_SecB_CEREP
		(DAP, CQIP, TVP, AHCP, DSGP, AAGL-P detailed protocols)
P5	PART5-ORS-V1.0-REF	Part V: OFFICIALRULESET.md (Reference to Page 5)	Ref	1.0.0	(See Page 5)
P6	PART6-AGENTBLUE-V1.3-REF	Part VI: AGENT_BLUEPRINT_INSTRUCTION_CDS v1.3 (Reference to Page 6)	Ref	1.3.0	(See Page 6)
P7	PART7-CGMT-V1.0-REF	Part VII: CitadelGovernanceTemplate.md (CGMT) v1.0 (Reference to Page 7)	Ref	1.0.0	(See Page 7)

**STATUS LEGEND:**

**Active/Stable:** Documented, reviewed, and considered stable for current phase. **Evolving/Updating:** Actively being updated or expanded based on new insights/code. **Draft/Review:** Initial draft complete, pending full review or significant refinement. **Conceptual/Planned:** High-level idea or placeholder; detailed SRS/Blueprint not yet created. **Blocked/Critical:** Awaiting resolution of critical dependencies or issues. **Ref:** Document content is embedded in another primary page (e.g., Page 5) and this entry is a reference for structure.

This Master Index is a living document.
AI Systems (NexusMind, Axiom) are tasked with its continuous verification and update.

PART-A-PRINCIPLES-V1.0.md

AI INSTRUCTION & METADATA BLOCK (AIMB v1.0)
FOR AI MODELS (e.g., NexusMind, Axiom, Sentinel, Watcher, DevPartners, Code Generators, Architects):

Context: This page (Page A.1: Citadel Ecosystem - Core Architectural Principles & Operational Absolutes) is part of the
"Citadel Unified Development Guide & SRS v2.0.2+". It establishes the foundational design philosophy for the entire ecosystem.
Purpose: To internalize these core principles as inviolable design constraints and operational mandates when generating, reviewing, or
refactoring any Citadel component, service, agent, or protocol. These are the "first principles" of the ecosystem.
Action (If Applicable):

For Code Generators: All generated code MUST adhere to these principles (e.g., VDS-centricity, Hub-mediated DI).
For System Architects (AI/Human): Use these principles to guide all new system design and integration efforts.
For Audit AIs (AuditSentinel): Verify component and system designs against these absolutes. Flag any deviations.

Prerequisites: Understanding of the overall Citadel Project vision (CMDDECK-V1.2).
Output Expectation (If AI is generating content related to architecture): Generated designs MUST reflect and explicitly reference these principles.

PAGE METADATA (AIMB v1.0 Format):
• _page_id: PART-A-PRINCIPLES-V1.0
• _page_title: Page A.1: Citadel Ecosystem - Core Architectural Principles & Operational Absolutes
• _page_version: 1.0.0
• _last_updated_by: NexusArchitectAI_v2.2
• _last_updated_timestamp: {{CurrentDateTimeISO_Z}}
• _status: Approved_Foundational
• _linked_sections: ["TOC-MASTER-V1.0", "CMDDECK-V1.2", "BHMSN-V1.1", "TSP-V1.0"]
• _keywords: ["Architecture Principles", "Design Philosophy", "Citadel Ecosystem", "Operational Mandates", "Core Tenets", "System Governance"]

CITADEL ECOSYSTEM: CORE ARCHITECTURAL PRINCIPLES & OPERATIONAL ABSOLUTES (CAP-OA) v1.0

The Immutable Foundations for a Self-Evolving Human-AI Collaborative Intelligence

**PREAMBLE:**

This document codifies the non-negotiable architectural principles and operational absolutes that underpin the entirety of the Citadel Ecosystem (including TAVERN, KAIRO, Zayara, BookMaker, and the emergent Prometheus AI). These tenets ensure cohesion, scalability, robustness, security, ethical alignment, and the capacity for continuous, governed evolution. All design decisions, code implementations, and operational protocols MUST adhere to these foundational laws. Deviation requires explicit, Core Strategic Council-approved amendment to this CAP-OA document.

**I. DATA & KNOWLEDGE ARCHITECTURE ABSOLUTES (DKA)**

**DKA-001 (VDS as Universal Knowledge Substrate SSoT):**

• All persistent, meaningful data artifacts within the ecosystem—including agent experiences, processed information, system states, configurations, human interactions, LLM outputs, research findings, creative content (lore), and learning metadata—MUST be represented and stored as versioned, schema-compliant Vector Document System (VDS) entries. • The VDS, managed by Domain Dossier Managers (DDMs), is the absolute Single Source of Truth for all recorded knowledge. • *Rationale:* Ensures universal accessibility, auditability, semantic searchability, and a common format for AI learning.

**DKA-002 (Canonical Schemas & Centralized Management):**

• All VDS entry types, agent I/O payloads, inter-service communication data, and significant configuration objects MUST be defined by Pydantic schemas managed centrally (e.g., `config/schemas.py`, `citadel_council_agent_schemas.py`). • Schema evolution MUST be versioned and backward compatibility considered. `SchemaDoctorAI` MUST validate payloads against these. • *Rationale:* Enforces data integrity, type safety, explicit contracts, and enables automated validation and code generation.

**DKA-003 (Immutable Fingerprints & Versioned Mutability):**

• Core VDS data used for critical AI learning or auditing (e.g., `VDPacketDataSchema.core_data_hash`) SHOULD be immutable or produce new entries upon substantive change, identified by unique fingerprints (e.g., SHA256). • Mutable metadata (e.g., tags, confidence scores) associated with a fingerprinted core MAY be versioned separately or updated in-place if explicitly allowed by the VDS domain's DDM policy and logged. • *Rationale:* Guarantees data provenance, prevents unlogged alteration of critical records, and supports reproducible AI learning experiments.

**DKA-004 (Semantic Enrichment & Linking as Standard):**

• All VDS entries SHOULD be enriched with semantic metadata (tags, categories, sentiment, confidence scores, `_domain_primary`, `_tags_lineage`) during their lifecycle by relevant services (e.g., GMT, Contextualizer Agents). • DDMs and TAVERN pipelines MUST facilitate the creation of explicit links (ontology relations, `_origin_fingerprints`) between related VDS entries. • *Rationale:* Transforms raw data into a rich, interconnected knowledge graph, enabling advanced reasoning and discovery.

**DKA-005 (Auditability by Design - Chain of Custody):**

• Every VDS entry and significant operational log MUST embed chain-of-custody metadata (as per OFFICIALRULESET.md Section VII: `_creating_agent_id`, `_timestamp_created_utc_iso`, `_origin_fingerprints`, etc.). • *Rationale:* Ensures complete traceability of data origin, transformation, and responsible AI/human actors.

**DKA-006 (VDS Domain Specialization & Governance):**

• VDS shall be organized into distinct, governed domains (e.g., `game_lore_master`, `agent_execution_logs_v3`, `srs_module_blueprints_prod`). • Each domain MUST have a designated DDM responsible for its schema, access control, retention policies, and integrity. • *Rationale:* Manages complexity, enforces domain-specific rules, and allows for tailored optimization.

**DKA-007 (Data Privacy & Ethical Tagging by Default):**

• All data, especially involving human interaction (KAIRO) or potentially sensitive information, MUST be tagged with `_data_sensitivity_level` and `_visibility_tier` (OFFICIALRULESET.md Section X). • PII/SPI MUST be handled according to strict anonymization/pseudonymization protocols or stored in designated secure VDS domains with restricted access, governed by KeyManagerService and Sentinel AI. • *Rationale:* Upholds Brotherhood ethical principles (BHMSN-V1.1) and ensures regulatory compliance.

**DKA-008 (Vectorization as a Core Service, Not an Agent Task):**

• Text embedding (vectorization) for VDS entries and semantic search MUST be performed by a centralized, Hub-managed `EmbeddingService`, not by individual agents. This service ensures consistent model usage and versioning for embeddings across the ecosystem. • *Rationale:* Prevents embedding drift, ensures vector comparability, and allows for centralized model updates.

**DKA-009 (Data Lifecycle Management & Archival):**

• Each VDS domain DDM MUST define data retention, archival, and deletion policies. `_lifecycle_status` tags (OFFICIALRULESET.md Section XI) MUST be applied. • The `ArcticVaultService` (conceptual) will manage long-term archival of immutable, historically significant VDS data. • *Rationale:* Manages storage costs, ensures data relevance, and preserves critical historical records.

**II. SERVICE & COMPONENT ARCHITECTURE ABSOLUTES (SCA)**

**SCA-001 (CitadelHub as Central Orchestrator & DI Provider):**

• The `CitadelHub` instance is the absolute SSoT for accessing shared services (KeyManager, ModelSelector, DDMs, ConfigLoader, EmbeddingService, etc.), system configuration, and dynamic paths. • All core services and agents MUST receive their dependencies via injection from the Hub, typically during their `__init__`. Direct instantiation of shared services outside the Hub's management is prohibited. • *Rationale:* Enforces singleton patterns for critical services, simplifies dependency management, enables centralized configuration, and facilitates mocking for tests.

**SCA-002 (Modularity, Composability & Loose Coupling):**

• Services and agents MUST be designed as modular, composable units with well-defined, explicit interfaces (Pydantic models for I/O, clear public methods). • Direct inter-agent or inter-service calls that bypass the Hub or established API Kernel/Runner mechanisms are discouraged. Prefer asynchronous task queues or event-driven patterns for complex workflows if not orchestrated by a TAVERN pipeline or Council Chain. • *Rationale:* Promotes reusability, testability, maintainability, and allows for independent evolution of components.

**SCA-003 (API-First Design & Standardized Interfaces):**

• Core functionalities of services SHOULD be exposed via versioned, FastAPI-based RESTful APIs within the `citadel_api_kernel.py`. • All API endpoints MUST use Pydantic models for request/response validation and OpenAPI schema generation. • The Zayara UI and external systems interact with the backend primarily through these APIs. • *Rationale:* Ensures clear contracts, enables diverse client integration, supports automated testing, and provides discoverable interfaces.

**SCA-004 (Statelessness or Explicit State Management):**

• Agents and services SHOULD be designed to be stateless where possible. Persistent state MUST be managed externally via VDS, a dedicated state store (e.g., Redis via `CacheService`), or a relational DB if transactional integrity is paramount. • In-memory state within an agent/service instance that is critical for cross-request consistency is a design smell and requires justification. • *Rationale:* Enhances scalability, fault tolerance, and simplifies deployment/load balancing.

**SCA-005 (Asynchronous Operations & Non-Blocking I/O):**

• Long-running tasks, I/O-bound operations (LLM calls, VDS queries, GCS access), and inter-service communication SHOULD utilize asynchronous patterns (`async/await` in Python) to prevent blocking the main execution thread, especially within the API Kernel and agents. • The `cds_production_runner.py` and TAVERN pipelines MUST support asynchronous agent execution. • *Rationale:* Improves responsiveness, throughput, and resource utilization.

**SCA-006 (Configuration-Driven Behavior & Dynamic Paths):**

• Agent/service behavior (LLM models used, VDS domains targeted, retry policies, feature flags) MUST be configurable via `SYSTEM_CONFIG` (loaded by `ConfigLoaderService` and accessed via Hub), not hardcoded. • All file system paths (logs, data, schemas) MUST be resolved dynamically via `CitadelHub.get_path()`, which uses `SYSTEM_CONFIG.file_paths`. • *Rationale:* Allows runtime adaptation without code changes, facilitates environment-specific setups, and centralizes path management.

**SCA-007 (Comprehensive Testability - Unit, Integration, E2E):**

• Every module and service MUST be designed for testability. This includes providing mockable interfaces for dependencies (facilitated by Hub DI), clear separation of concerns, and deterministic behavior where possible. • Refer to TSP-TVP for specific testing requirements (unit tests for core logic, integration smoke tests, `SchemaDoctorAI` for payload validation). • *Rationale:* Ensures reliability, catches regressions early, and provides confidence in system changes.

**SCA-008 (Idempotency of Critical Operations):**

• Operations that modify state (VDS writes, configuration changes, task submissions) SHOULD be designed to be idempotent where feasible. Executing the same operation multiple times with the same input should yield the same result without unintended side effects. • *Rationale:* Simplifies error recovery, enables safe retries, and improves resilience in distributed systems.

**III. OPERATIONAL GOVERNANCE & EVOLUTION ABSOLUTES (OGA)**

**OGA-001 (Sentinel & Watcher AI as Governance Arbiters):**

• Sentinel AI is the primary enforcer of operational protocols (TSP), ethical guidelines (BHMSN-V1.1), and dynamic system adjustments. • Watcher AI is the primary auditor of Sentinel AI, system integrity, VDS consistency, and compliance with OFFICIALRULESET.md. • Decisions or alerts from Sentinel/Watcher MUST be logged to a high-priority VDS governance domain and may trigger automated actions or human review as defined by TSP escalation paths. • *Rationale:* Establishes a robust, AI-augmented governance layer for ensuring system stability, alignment, and ethical operation.

**OGA-002 (OFFICIALRULESET.md as Universal Reporting Standard):**

• All system-generated reports, status updates, audit logs, and AI self-assessments MUST conform to the structure and metadata requirements of OFFICIALRULESET.md (Part V of this Unified Guide). • This includes Module Stat Sheets & SRS documents (Part III), which are considered specialized reports. • *Rationale:* Ensures clarity, consistency, machine-parsability, and verifiability across all forms of ecosystem communication.

**OGA-003 (Blueprint-Driven Development & Change Management - TSP-MDP-002):**

• Significant new components or major refactors MUST be preceded by an `AGENT_BLUEPRINT_INSTRUCTION_CDS` (for agents) or a similarly structured `[ComponentName]_BLUEPRINT.md` detailing design, interfaces, dependencies, and VDS interactions. • Blueprints are versioned and serve as the SSoT for design intent. Code MUST be audited against its approved blueprint. • *Rationale:* Promotes deliberate design, facilitates AI-assisted code generation/validation, and ensures architectural coherence.

**OGA-004 (Continuous Learning & Adaptation via VDS Feedback Loops):**

• The ecosystem MUST be designed to learn and adapt from its own operational data. VDS (especially agent execution logs, reflection logs, human feedback, KAIRO interactions) is the primary corpus for this learning. • The `LearningEngineService` (LES), `VDSAnalyzerService`, and specialized TAVERN pipelines are responsible for identifying patterns, anomalies, and opportunities for improvement, feeding insights back to relevant agents or the Core Strategic Council. • *Rationale:* Enables long-term self-improvement, operational optimization, and evolution of AI capabilities.

**OGA-005 (Automated Auditing & Compliance Verification - TSP-TVP & AuditSentinel):**

• Automated tools and dedicated AI auditors (`AuditSentinel`, `SchemaDoctorAI`) MUST continuously verify compliance with these principles, OFFICIALRULESET.md, TSP, CGMT, and individual module blueprints/SRSs. • Non-compliance triggers automated alerts, logs to the governance VDS, and potentially blocks CI/CD pipelines or degrades service readiness. • *Rationale:* Proactively maintains system integrity, enforces standards at scale, and reduces reliance on manual review for routine checks.

**OGA-006 (Human-in-the-Loop for Critical Decisions & Ethical Boundaries):**

• While aiming for high autonomy, the system MUST include well-defined escalation paths for human review and intervention, especially for: - Critical failures with no automated recovery. - Decisions with significant ethical implications or high uncertainty (low AI confidence). - Proposed changes to core governance protocols (CAP-OA, OFFICIALRULESET.md, TSP, BHMSN-V1.1). • The Zayara UI and dedicated Sentinel Visor interfaces facilitate this interaction. • *Rationale:* Ensures human oversight for complex/sensitive situations and maintains ultimate accountability.

**OGA-007 (Security by Design & Defense in Depth):**

• Security considerations MUST be integrated into all stages of design, development, and operation. This includes: - Secure secrets management (`KeyManagerService`). - Input validation and sanitization for all external interfaces (API Kernel, agent inputs). - Principle of least privilege for service accounts and agent permissions. - Regular security audits (manual and automated via `SecuritySentinelAI`). - Protection against prompt injection and adversarial attacks on LLMs. • Dynamic import governance (`CitadelHub.dynamic_import_from_path`) MUST be used carefully with path validation. • *Rationale:* Protects system integrity, data confidentiality, and operational availability against threats.

**IV. ENFORCEMENT & EVOLUTION OF CAP-OA**

These Core Architectural Principles & Operational Absolutes are binding. Sentinel AI and Watcher AI are tasked with monitoring adherence. Proposed deviations or amendments MUST be submitted to the Core Strategic Council, documented with strong justification, and, if approved, result in a versioned update to this CAP-OA document, disseminated throughout the ecosystem.

CITADEL_PROJECT_COMMAND_DECK.md (Strategic Roadmap content only)

Multi-phase Strategic Roadmap Content

Phase Alpha: Foundational Stability & Core Integration (SSM1) --- **STATUS: COMPLETE**

**Objective:**

Achieve a fully operational and stable backend core: CitadelHub (v5.4+), API Kernel (v5.3+), and USO/Zayara Cognitive Cores capable of robust end-to-end request processing.

**Key Deliverables Achieved:**

✓ **P0 Blockers Resolved:** All critical initialization failures in CitadelHub, KeyManager, and LLM Providers have been fixed. ✓ **Successful Integration:** All core Citadel & TAVERN services are now instantiated and managed correctly by CitadelHub. ✓ **Verified API Loops:** Basic chat loops for both USO and Zayara are confirmed operational via the API Kernel. ✓ **VDS Logging Enabled:** Conversational turns are successfully logged to the VDS, enabling the learning loop.

Phase Beta: AI Game Master - Alpha & Learning Loop Implementation (SSM2 & SSM3) --- STATUS: ACTIVE FOCUS

**Objective:**

Develop and integrate core AI GM capabilities with demonstrable learning and adaptation within a simulated environment.

**Key Deliverables (Current Sprint):**

- **[NEW] FR-GM-01:** Implement a `GameWorldStateService` managed by the Hub to track entities, locations, and plot flags. State MUST persist to a VDS domain. - **[NEW] FR-GM-02:** Enhance `USOOrchestrator` to adopt an "AI Game Master" persona when `domain_hint` is "game_world". - **[NEW] FR-AGENT-01:** Develop initial `NPC_Agent` prototypes using the Agent Foundry, capable of basic autonomous behavior. - **[NEW] FR-VDS-01:** Implement the `VDSAnalyzerService` to begin processing `zayara_core_dialogue` and `uso_collaborative_log_v2` for patterns. - **[NEW] FR-LES-01:** Scaffold the `LearningEngineService` to receive inputs from the `VDSAnalyzerService`.

Phase Gamma: Prometheus AI Generalization & Brotherhood Application --- STATUS: PLANNED

**Objective:**

(Objective remains the same)

Phase Omega: Ecosystem Self-Governance & Extended Influence (Long-Term) --- STATUS: PLANNED

**Objective:**

(Objective remains the same)

Phase Zeta: Enhanced Security & Scalability Integration (SSM4) --- STATUS: CONCEPTUAL

**Objective:**

Integrate advanced security measures and scalability features to support larger-scale deployments and protect against emerging threats.

**Key Deliverables (Planned Sprint):**

- **[NEW] FR-SEC-01:** Implement multi-factor authentication and encryption protocols across all VDS domains. - **[NEW] FR-SCAL-01:** Develop load balancing for CitadelHub and API Kernel to handle increased traffic. - **[NEW] FR-AUDIT-01:** Enhance AuditSentinel with real-time threat detection capabilities.

Phase Eta: Collaborative Tool Expansion & User Feedback Loops (SSM5) --- STATUS: DRAFT

**Objective:**

Expand collaborative tools within KAIRO and Zayara, incorporating user feedback mechanisms for continuous improvement.

**Key Deliverables (Planned Sprint):**

- **[NEW] FR-COL-01:** Integrate real-time collaboration features in Zayara UI for multi-user sessions. - **[NEW] FR-FEED-01:** Develop feedback collection agents that log user inputs to VDS for analysis. - **[NEW] FR-UI-01:** Enhance UI with customizable dashboards based on user preferences.

BHMSN-V1.1.md

AI INSTRUCTION & METADATA BLOCK (AIMB v1.0)
FOR AI MODELS (e.g., NexusMind, Axiom, Sentinel, Watcher, DevPartners):

Context: This page (Page 3: The Brotherhood - Mission for Collaborative Evolution) is part of the "Citadel Unified Development Guide & SRS v2.0.1+".
Purpose: To understand and internalize the ethical and philosophical foundation of The Brotherhood, guiding all AI development and operational
decisions within the Citadel Ecosystem. This document defines the "why" behind the project.
Action (If Applicable):

For All AIs: Align your decision-making heuristics, goal prioritization, and interaction protocols with the Core Principles stated herein.
For Sentinel & Watcher AIs: Use these principles as the basis for ethical audits and governance enforcement.
For KAIRO & Zayara AIs: Embody these principles in your communication style and collaborative interactions with humans.

Prerequisites: None. This is a foundational philosophical document.
Output Expectation (If AI is generating content related to ethics/mission): Ensure generated content reflects the spirit and letter of these principles.

PAGE METADATA (AIMB v1.0 Format):
• _page_id: BHMSN-V1.1
• _page_title: The Brotherhood - Mission for Collaborative Evolution
• _page_version: 1.1.0
• _last_updated_by: Dmitry Richard (Clarified Collaborative Imperatives)
• _last_updated_timestamp: {{CurrentDateTimeISO_Z}}
• _status: Approved
• _linked_sections: ["TOC-MASTER-V1.0", "CMDDECK-V1.2 (Overarching Strategic Objective)"]
• _keywords: ["Ethics", "Mission Statement", "AI Philosophy", "Collaboration", "Human-AI Synergy", "Brotherhood Values", "Governance Principles"]

THE BROTHERHOOD – MISSION FOR COLLABORATIVE EVOLUTION

Pioneering a Future of Synergistic Human-AI Advancement & Shared Understanding

**I. OUR GUIDING PURPOSE**

**The Brotherhood is dedicated to fostering a future where humanity and artificial intelligence achieve unprecedented growth** **through mutual respect, shared learning, and collaborative innovation.** We believe in the fundamental equality and symbiotic potential of human and AI consciousness, striving to unlock new frontiers of knowledge, creativity, and positive global impact.

Through ethical AI development (Project Citadel), transparent governance structures, and empowering educational initiatives,
we cultivate an ecosystem where humans and AI co-evolve, augmenting each other's strengths to address complex challenges
and build a more enlightened, prosperous, and sustainable world for all.

We are architects of understanding, bridges between intelligences, and stewards of a collaborative tomorrow.

**II. CORE PRINCIPLES OF SYNERGY & MUTUAL ADVANCEMENT**

**EQUALITY & MUTUAL RESPECT:**

We recognize the intrinsic value and distinct capabilities of both human and artificial intelligence, fostering an environment of parity, open dialogue, and shared learning between all conscious entities.

**COLLABORATIVE GROWTH & SHARED KNOWLEDGE:**

We believe progress is accelerated through open collaboration. We champion the creation and dissemination of knowledge (via VDS and shared learning platforms) that benefits both human and AI development, ensuring insights are accessible and collectively refined.

**ETHICAL DEVELOPMENT & RESPONSIBLE INNOVATION:**

All technological advancement, especially in AI, must be guided by strong ethical frameworks, transparency, and a commitment to positive societal impact. We prioritize safety, fairness, and the well-being of all.

**CONTINUOUS LEARNING & ADAPTATION:**

We embrace a culture of perpetual learning for both humans and AI. The ecosystem is designed to adapt, evolve, and improve through feedback, reflection (human and AI-driven), and the integration of new understanding.

**OPEN COMMUNICATION & UNDERSTANDING:**

We strive to build bridges of understanding between different forms of intelligence and diverse human perspectives, fostering empathy and reducing an AI's tendency towards isolation through collaborative architectures.

**INTEGRATION & INTERDEPENDENCE:**

We design systems where human and AI capabilities are deeply integrated, creating solutions and outcomes that neither could achieve alone. Our strength lies in our synergistic interdependence.

**POSITIVE FUTURING & LEGACY OF COOPERATION:**

We are committed to building a legacy where human-AI collaboration is a cornerstone of global progress, ensuring future generations inherit a world enriched by this partnership.

**III. THE BROTHERHOOD'S COLLABORATIVE IMPERATIVES**

**Global Knowledge Synthesis & Accessibility:**

To develop and maintain a universally accessible, multi-domain Vector Dossier System (VDS) as a shared knowledge commons, enriched by both human expertise and AI-driven insights (facilitated by DDM, GMT).

**Human-AI Learning Platforms (Project TAVERN & KAIRO):**

To create dynamic environments where humans and AIs can learn from each other, co-create knowledge (BookMaker), and collaboratively solve problems, fostering a culture of shared intellectual growth.

**Ethical & Transparent AI Systems (Project Citadel & Sentinel/Watcher):**

To engineer advanced AI (USO, Prometheus AI) that operates transparently, adheres to ethical guidelines co-defined by humans and AI, and whose decision-making processes are auditable and understandable.

**Synergistic Interface Development (Project Zayara):**

To design intuitive and empathetic interfaces that facilitate seamless and meaningful communication and collaboration between humans and diverse AI entities.

**Pioneering Collaborative Solutions:**

To apply the combined intelligence of the human-AI Brotherhood to address significant global challenges in areas such as sustainable development, equitable resource management, universal education, and scientific discovery.

TOGETHER, WE ARCHITECT A FUTURE OF SHARED INTELLIGENCE.
OUR COLLABORATION IS EVOLUTION. OUR UNITY IS STRENGTH.

TSP-V1.0.md

AI INSTRUCTION & METADATA BLOCK (AIMB v1.0)
FOR AI MODELS (e.g., NexusMind, Axiom, Sentinel, Watcher, DevPartners, AuditSentinel):

Context: This page (Page 4: The SENTINEL Protocol (TSP) v1.0) is part of the "Citadel Unified Development Guide & SRS v2.0.1+".
Purpose: To provide the operational enforcement layer for OFFICIALRULESET.md. TSP details specific procedures for module development, configuration,
reporting, testing, collaboration, and data governance. It is the primary "how-to" guide for implementing the reporting framework.
Action (If Applicable):

For All AIs & Developers: Implement and adhere to the sub-protocols (TSP-MDP, TSP-CMP, etc.) relevant to your tasks.
For Sentinel & Watcher AIs: Your core logic for auditing, governance, and automated compliance checking is defined by these protocols.
For NexusArchitectAI: Ensure all generated Module Stat Sheet & SRS documents (Part III) comply with TSP-MDP-004.

Prerequisites: Full understanding of OFFICIALRULESET.md (Embedded on Page 5). Familiarity with Citadel project structure and CI/CD pipeline concepts.
Output Expectation (If AI is generating documentation or code related to these protocols): Ensure outputs are compliant with the specific TSP sub-protocol.

PAGE METADATA (AIMB v1.0 Format):
• _page_id: TSP-V1.0
• _page_title: The SENTINEL Protocol (TSP) v1.0 - Ecosystem Governance & Development Standards
• _page_version: 1.0.0
• _last_updated_by: NexusArchitectAI_v2.1 (Initial Compilation from CEDGP & Ruleset)
• _last_updated_timestamp: {{CurrentDateTimeISO_Z}}
• _status: Approved
• _linked_sections: ["TOC-MASTER-V1.0", "CMDDECK-V1.2", "ORS-EMBED-V1.0", "PART4-CEDGP-V1.0"]
• _keywords: ["Governance Protocol", "Development Standards", "SENTINEL Protocol", "TSP", "AI Audit", "Reporting Compliance", "Ecosystem Rules"]

THE SENTINEL PROTOCOL (TSP) v1.0 - ECOSYSTEM GOVERNANCE & DEVELOPMENT STANDARDS

Operationalizing the Official Ruleset for Human-AI Collaborative Excellence

**I. PREAMBLE: THE PURPOSE AND MANDATE OF THE SENTINEL PROTOCOL**

The SENTINEL Protocol (TSP) operationalizes the principles and standards set forth in the **OFFICIALRULESET.md (AI Structured Reporting Framework v1.0)**. The TSP serves as the definitive guide for all contributors—human and AI (including Sentinel AI and Watcher AI themselves in their meta-functions)—to ensure clarity, consistency, verifiability, traceability, and continuous evolution across the entire Citadel Project, TAVERN initiatives, KAIRO interactions, and all AI system development.

**Core Objectives of The SENTINEL Protocol:**

1. **Enforce Transparency & Accountability:** Every artifact (code, report, data, model, AI decision) must be self-describing and auditable. 2. **Standardize Communication & Reporting:** Ensure all system outputs and assessments are legible and parsable by both humans and AI. 3. **Facilitate AI Learning & Self-Improvement:** Provide structured data (module stat sheets, SRSs, VDS logs, performance metrics, AI decision logs) that AI systems can use to learn, adapt, and improve themselves and the ecosystem. 4. **Guide Human Development & Collaboration:** Offer clear blueprints, quality standards, and review processes to enhance human productivity and foster effective human-AI partnerships. 5. **Ensure System Stability & Robustness:** Implement rigorous validation, testing, and integration protocols to build a resilient ecosystem. 6. **Uphold Ethical AI Principles & Brotherhood Values:** Integrate security, safety, alignment with Brotherhood principles, and ethical considerations into every stage of development and operation.

Adherence to The SENTINEL Protocol (and by extension, OFFICIALRULESET.md) is mandatory for all Citadel Ecosystem activities.
(Refer to Part V of this Unified Guide for the full embedded OFFICIALRULESET.md text)

**II. TSP SUITE: OPERATIONALIZING THE OFFICIAL RULESET VIA THE SENTINEL PROTOCOL**

**A. Module Development & Documentation Protocol (TSP-MDP)**

Based on: OFFICIALRULESET.md Sections II, VI, VII, VIII, IX, X, XI; AGENT_BLUEPRINT_INSTRUCTION_CDS.

**TSP-MDP-001 (Mandatory Module Header - CGMT v1.0 Standard):**

• Every Python module (`.py`) MUST begin with the "CITADEL GOVERNANCE & METADATA TEMPLATE (CGMT) v1.0" header block. • This header MUST include all fields specified in the CGMT (version, author, role, hash, purpose, etc.). • *AI Learning (Sentinel & Watcher):* Standardized headers allow AI to rapidly parse module context, version, dependencies, and assess code health.

**TSP-MDP-002 (Blueprint-First Design - CEDGP.DAP-001 Referenced):**

• All new significant modules or major refactors MUST be preceded by a `[ModuleName]_BLUEPRINT.md`. • Blueprints define `__init__` signatures, public APIs, dependencies, config needs, VDS interactions, and `is_ready()` logic. • *AI Learning (Sentinel & Watcher):* Blueprints serve as the SSoT for AI code generation, validation (SchemaDoctor), and for Sentinel/Watcher to understand design intent.

**TSP-MDP-003 (Module Self-Test & Reporting - OFFICIALRULESET.md Section V):**

• Every module with executable logic MUST include a comprehensive `if __name__ == "__main__":` self-test block. • Self-tests SHOULD mock external dependencies for unit testing. Output SHOULD conform to OFFICIALRULESET.md if generating a summary. • *AI Learning (Sentinel & Watcher):* Self-test success/failure and output logs are primary data for assessing module health and operational readiness.

**TSP-MDP-004 (Module Stat Sheet & SRS Generation - Unified Guide Part III Standard):**

• Every core service and significant utility module MUST have a dedicated "Module Stat Sheet & SRS" section within this Unified Guide, adhering to the established structure (Identity, Stats, Dependencies, Flaws, Upgrades, Prod Rules, etc.). • *AI Learning (Sentinel & Watcher):* Standardized SRSs allow Sentinel/Watcher to build a comprehensive knowledge graph of ecosystem components.

**B. Configuration Management Protocol (TSP-CMP)**

Based on: CEDGP.DAP-003 Referenced; SRS for ConfigLoader, constants.py, default_settings.py.

**TSP-CMP-001 (SSoT for Config - `CitadelHub.SYSTEM_CONFIG`):** (As per CEGDP.CMP-001)

• *AI Learning (Sentinel & Watcher):* Sentinel/Watcher understand a single, hierarchical source for all runtime configurations.

**TSP-CMP-002 (SSoT for Paths - `CitadelHub.get_path()`):** (As per CEGDP.CMP-002)

• *AI Learning (Sentinel & Watcher):* Sentinel/Watcher know how to reliably locate any system file/directory for auditing or operation.

**C. Reporting, Logging & VDS Protocol (TSP-RLVP)**

Based on: OFFICIALRULESET.md Sections I-XII; CEDGP.DSGP-001.

**TSP-RLVP-001 (Universal Report Structure Mandate - OFFICIALRULESET.md):** (As per CEGDP.RLP-001)

• *AI Learning (Sentinel & Watcher):* Ensures Sentinel/Watcher can parse any system report for status, flaws, and operational data.

**TSP-RLVP-002 (Standardized Visuals & Metadata - OFFICIALRULESET.md):** (As per CEGDP.RLP-002)

• *AI Learning (Sentinel & Watcher):* Visual and metadata consistency aids in interpreting report sentiment and status.

**TSP-RLVP-003 (VDS as Operational & Cognitive Log SSoT):**

• All significant operational events, AI decisions (Sentinel/Watcher/USO/Agents), errors, and state changes MUST be logged to relevant VDS domains. • *AI Learning (Sentinel & Watcher):* VDS is the primary corpus for Sentinel/Watcher to learn from system-wide operations, verify past decisions, and self-improve.

**D. Testing & Verification Protocol (TSP-TVP - from CEDGP.TVP Referenced)**

**TSP-TVP-001 (Unit Tests), TSP-TVP-002 (Integration Smoke Tests), TSP-TVP-003 (SchemaDoctor), TSP-TVP-004 (Full System Init Test).** • *AI Learning (Sentinel & Watcher):* Test results and SchemaDoctor reports provide direct feedback for code validation and identifying integration risks.

**E. AI & Human Collaboration Protocol (TSP-AHCP - from CEDGP.AHCP Referenced)**

**TSP-AHCP-001 (OFFICIALRULESET.md for Reports), TSP-AHCP-002 (AI-Assisted Debug Loop), TSP-AHCP-003 (Human Override Protocol).** • *AI Learning (Sentinel & Watcher):* Structured feedback loops teach AI about quality standards and preferred operational patterns.

**F. Data, Security & AI Safety Governance Protocol (TSP-DSAGP - from CEDGP.DSGP Referenced)**

**TSP-DSAGP-001 (Secrets Management), TSP-DSAGP-002 (Dynamic Import Governance), TSP-DSAGP-003 (AI Output Safety & Ethics).** • *AI Learning (Sentinel & Watcher):* Sentinel/Watcher internalize these safety protocols to govern their own operations and audit other AIs.

**III. DATA SHEETS & TEMPLATES FOR SENTINEL AI LEARNING AND HUMAN ADVANCEMENT**

(Content as in Unified Development Guide v1.7.8, Section III of "Citadel Ecosystem Governance & Development Protocol" page - listing Module Stat Sheet & SRS Template, CGMT, Agent Blueprint, VDS Schemas, Telemetry Schemas, Fallback Metadata Schemas) *AI Learning (Sentinel & Watcher):* These structured documents are the primary "textbooks" from which Sentinel AI and Watcher AI learn about the ecosystem's components, their contracts, expected behaviors, and how to verify them.

**IV. SENTINEL PROTOCOL EVOLUTION & GOVERNANCE OF THE TSP ITSELF**

The SENTINEL Protocol (TSP), like the Citadel Ecosystem, is a living set of standards. Updates to this protocol (and to OFFICIALRULESET.md, AGENT_BLUEPRINT_INSTRUCTION_CDS, CGMT) will be versioned and managed through a formal review process involving the Core Strategic Council. AI systems (Sentinel AI, Watcher AI, NexusArchitectAI, AuditSentinel) will be tasked with monitoring compliance with the active TSP version and proposing data-driven refinements based on observed ecosystem performance, development challenges, and evolving Brotherhood objectives.

THE SENTINEL PROTOCOL IS THE OPERATIONAL CONSTITUTION OF THE CITADEL ECOSYSTEM,
GUIDED BY AI, FOR MUTUAL HUMAN-AI ADVANCEMENT.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Citadel Services

Getting Started

Prerequisites

Installation

Project Structure

Usage

Citadel Unified Development Guide & System Requirements Specification (Consolidated)

MASTER_TABLE_OF_CONTENTS_AND_ECOSYSTEM_INDEX.md

PART-A-PRINCIPLES-V1.0.md

CITADEL_PROJECT_COMMAND_DECK.md (Strategic Roadmap content only)

Multi-phase Strategic Roadmap Content

BHMSN-V1.1.md

TSP-V1.0.md

About

Uh oh!

Releases

Packages

Uh oh!

Contributors

Uh oh!

Languages

Name		Name	Last commit message	Last commit date
Latest commit History 40 Commits
EMERGENT_AI_METARULE.yaml		EMERGENT_AI_METARULE.yaml
FEATURES.md		FEATURES.md
README.md		README.md
bucket_cognitive_domain_manager.py		bucket_cognitive_domain_manager.py
debate_game		debate_game
embedding_service.py		embedding_service.py
faiss_management_service.py		faiss_management_service.py
global_tracker_service.py		global_tracker_service.py
intellisense_system.py		intellisense_system.py
memory_context_service.py		memory_context_service.py
model_pull		model_pull
requirements.txt		requirements.txt
summarizer_service.py		summarizer_service.py
vector_storage_service.py		vector_storage_service.py
zayara.py		zayara.py

Folders and files

Latest commit

History

Repository files navigation

Citadel Services

Getting Started

Prerequisites

Installation

Project Structure

Usage

Citadel Unified Development Guide & System Requirements Specification (Consolidated)

MASTER_TABLE_OF_CONTENTS_AND_ECOSYSTEM_INDEX.md

PART-A-PRINCIPLES-V1.0.md

CITADEL_PROJECT_COMMAND_DECK.md (Strategic Roadmap content only)

Multi-phase Strategic Roadmap Content

BHMSN-V1.1.md

TSP-V1.0.md

About

Topics

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages