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