Changes for page System Architecture
Last modified by Robert Schaub on 2025/12/22 13:50
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -48,6 +48,7 @@ 48 48 {{/diagram}} 49 49 50 50 **Components:** 51 + 51 51 * Single AKEL API call (Claude Sonnet 4.5) 52 52 * Gates 1 & 4 (claim validation, verdict confidence) 53 53 * Basic UI display ... ... @@ -100,6 +100,7 @@ 100 100 {{/diagram}} 101 101 102 102 **New Components:** 104 + 103 103 * Scenario generation 104 104 * Evidence deduplication system 105 105 * Gates 2 & 3 (evidence relevance, scenario coherence) ... ... @@ -158,6 +158,7 @@ 158 158 {{/diagram}} 159 159 160 160 **Production Components:** 163 + 161 161 * Multi-component AKEL pipeline 162 162 * Review workflow system 163 163 * Audit sampling framework ... ... @@ -164,7 +164,6 @@ 164 164 * Federation architecture 165 165 * Full data model (PostgreSQL + Redis + S3) 166 166 167 - 168 168 == 2. Quality Gate Architecture == 169 169 170 170 === 2.1 Quality Gate System === ... ... @@ -228,6 +228,7 @@ 228 228 **Storage:** SQLite or minimal database 229 229 230 230 **Entities:** 233 + 231 231 * Articles (input text/URL) 232 232 * Claims (extracted from articles) 233 233 * Verdicts (per claim) ... ... @@ -241,6 +241,7 @@ 241 241 **Storage:** PostgreSQL (primary), Redis (cache), S3 (documents) 242 242 243 243 **Core Entities:** 247 + 244 244 * Claims (with versions, clustering) 245 245 * Scenarios (interpretations of claims) 246 246 * Evidence (deduplicated, provenance tracked) ... ... @@ -259,6 +259,7 @@ 259 259 **Full System:** Multi-component orchestration 260 260 261 261 **Responsibilities:** 266 + 262 262 * Route input through component pipeline 263 263 * Manage component state 264 264 * Handle errors and retries ... ... @@ -265,12 +265,12 @@ 265 265 * Coordinate quality gates 266 266 * Trigger review workflows 267 267 268 - 269 269 === 4.2 Quality Gate Validator === 270 270 271 271 **All Phases:** Present but evolving complexity 272 272 273 273 **Responsibilities:** 278 + 274 274 * Execute all configured gates 275 275 * Aggregate gate results 276 276 * Make publication decisions ... ... @@ -277,7 +277,6 @@ 277 277 * Generate explanatory messages 278 278 * Log quality metrics 279 279 280 - 281 281 === 4.3 Review Queue Manager === 282 282 283 283 **POC:** Not present ... ... @@ -285,6 +285,7 @@ 285 285 **V1.0:** Full implementation 286 286 287 287 **Responsibilities:** 292 + 288 288 * Route low-confidence verdicts to review 289 289 * Manage reviewer assignments 290 290 * Track review status ... ... @@ -291,12 +291,12 @@ 291 291 * Implement audit sampling 292 292 * Generate review metrics 293 293 294 - 295 295 == 5. Architecture Decisions == 296 296 297 297 === 5.1 Why Single AKEL Call for POC? === 298 298 299 299 **Rationale:** 304 + 300 300 * Validates core capability fastest 301 301 * Simplest to implement and test 302 302 * Fail-fast if AI fundamentally can't do task ... ... @@ -309,6 +309,7 @@ 309 309 === 5.2 Why Add Components in V1.0? === 310 310 311 311 **Rationale:** 317 + 312 312 * Better error handling per step 313 313 * Independent optimization of each component 314 314 * Easier to add new capabilities ... ... @@ -323,10 +323,8 @@ 323 323 * [[Requirements>>Test.FactHarbor.Specification.Requirements.WebHome]] - System requirements 324 324 * [[Design>>Test.FactHarbor.Specification.Design.WebHome]] - UI/UX design 325 325 * [[Roadmap>>Test.FactHarbor.Roadmap.WebHome]] - Implementation phases 326 -* [[POC1>>Test.FactHarbor.Roadmap.POC1.WebHome]] - POC1 details 332 +* [[POC1>>Test.FactHarbor pre10 V0\.9\.70.Roadmap.POC1.WebHome]] - POC1 details 327 327 * [[POC2>>Test.FactHarbor.Roadmap.POC2.WebHome]] - POC2 details 328 328 329 - 330 330 **Document Status:** ✅ Architecture Specified (POC1, POC2, Full System) 331 331 **Version:** V0.9.70 332 -