asepharyana
eac0443c4c
Ganti explore phase MANDATORY (3 subagent tiap turn, boros) dengan tool explore_codebase yang DIPUTUSKAN agent sendiri (lazy, token-aware): - hapus ExploreService trait + with_explore + Phase 0 dari turn loop - ExploreServiceImpl kini jadi tool 'explore_codebase' (1 context-scout subagent, read-only, cap output 4k chars) - system prompt: instruksi TOKEN BUDGET (jawab langsung utk query simple, panggil explore_codebase sekali utk task kompleks) Loop utama kini adaptif & self-healing: - max_tokens adaptif (800/1600/4096 by request length) — bukan selalu 4096 - temperature 0.2 saat tool-calling, 0.7 utk final answer - ErrorTracker: deteksi tool error berulang → inject recovery note, stop setelah 8 error total (bukan 50 iterasi sia-sia) - auto-compact history > 60k chars sebelum LLM call - tool output di-truncate ke 12k chars sebelum masuk konteks Tambah 8 unit test (truncation, adaptive tokens, error tracker).
57 lines
2.0 KiB
Rust
57 lines
2.0 KiB
Rust
//! # Zesdex Application Layer
|
|
//!
|
|
//! Defines port traits (interfaces) and use-case implementations for the
|
|
//! Zesdex application. This crate depends **only** on the domain crate;
|
|
//! it has no knowledge of infrastructure or interface adapters.
|
|
//!
|
|
//! ## Architecture
|
|
//!
|
|
//! ```text
|
|
//! apps/application/src/
|
|
//! ├── lib.rs — crate root, re-exports
|
|
//! ├── ports/ — Port traits (interfaces to external services)
|
|
//! │ ├── provider.rs -- ProviderService (LLM chat completion)
|
|
//! │ ├── password.rs -- PasswordService (hash / verify)
|
|
//! │ ├── token.rs -- TokenService (JWT create / verify)
|
|
//! │ └── authentication.rs -- AuthService (combined auth)
|
|
//! ├── auth/ — Auth use-cases
|
|
//! │ ├── oauth_service.rs -- OAuth 2.0 PKCE flow
|
|
//! │ └── session_service.rs -- Session CRUD lifecycle
|
|
//! └── cms/ — CMS use-cases
|
|
//! ├── conversation_service.rs -- Conversation CRUD
|
|
//! ├── memory_service.rs -- Long-term memory management
|
|
//! └── settings_service.rs -- Settings & app-config management
|
|
//! ```
|
|
//!
|
|
//! ## Key Design Principle
|
|
//!
|
|
//! Application services are generic over their repository/port dependencies.
|
|
//! Concrete implementations are injected at the composition root, keeping
|
|
//! the use-case logic independent of any specific persistence or infrastructure
|
|
//! technology.
|
|
|
|
pub mod agent;
|
|
pub mod auth;
|
|
pub mod cms;
|
|
pub mod ports;
|
|
|
|
// Re-export port traits for ergonomic access.
|
|
pub use ports::*;
|
|
|
|
// Re-export auth use-cases.
|
|
pub use auth::{
|
|
oauth_service::{OAuthFlowStore, OAuthUseCase, TokenExchanger},
|
|
session_service::SessionServiceImpl,
|
|
};
|
|
|
|
// Re-export CMS use-cases.
|
|
pub use cms::{
|
|
conversation_service::ConversationServiceImpl, memory_service::MemoryServiceImpl,
|
|
settings_service::SettingsServiceImpl,
|
|
};
|
|
|
|
pub use agent::{
|
|
turn_service::{compact_messages_with_ai, AgentTurnServiceImpl},
|
|
AgentTurnService, ToolExecutor,
|
|
};
|