Changes for page System Architecture

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -2,7 +2,7 @@
2	2
3	3	**FactHarbor system architecture including POC simplifications and full system design**
4	4
5		------
	5	+---
6	6
7	7	== 1. Architecture Evolution ==
8	8
...	...	@@ -49,7 +49,6 @@
49	49	{{/diagram}}
50	50
51	51	**Components:**
52		-
53	53	* Single AKEL API call (Claude Sonnet 4.5)
54	54	* Gates 1 & 4 (claim validation, verdict confidence)
55	55	* Basic UI display
...	...	@@ -57,7 +57,7 @@
57	57
58	58	**Data Storage:** Minimal (stateless or simple SQLite)
59	59
60		------
	59	+---
61	61
62	62	=== 1.2 POC2 Architecture (Enhanced) ===
63	63
...	...	@@ -103,7 +103,6 @@
103	103	{{/diagram}}
104	104
105	105	**New Components:**
106		-
107	107	* Scenario generation
108	108	* Evidence deduplication system
109	109	* Gates 2 & 3 (evidence relevance, scenario coherence)
...	...	@@ -111,7 +111,7 @@
111	111
112	112	**Data Storage:** Enhanced (claims, scenarios, evidence, metrics)
113	113
114		------
	112	+---
115	115
116	116	=== 1.3 Full System Architecture (V1.0+) ===
117	117
...	...	@@ -163,7 +163,6 @@
163	163	{{/diagram}}
164	164
165	165	**Production Components:**
166		-
167	167	* Multi-component AKEL pipeline
168	168	* Review workflow system
169	169	* Audit sampling framework
...	...	@@ -170,7 +170,7 @@
170	170	* Federation architecture
171	171	* Full data model (PostgreSQL + Redis + S3)
172	172
173		------
	170	+---
174	174
175	175	== 2. Quality Gate Architecture ==
176	176
...	...	@@ -216,7 +216,7 @@
216	216	(Any gate FAIL → Block + Explain)
217	217	{{/diagram}}
218	218
219		------
	216	+---
220	220
221	221	=== 2.2 Gate Implementation by Phase ===
222	222
...	...	@@ -228,7 +228,7 @@
228	228
229	229	**Hardening** means: Thresholds validated, edge cases handled, <5% failure rate
230	230
231		------
	228	+---
232	232
233	233	== 3. Data Architecture ==
234	234
...	...	@@ -237,7 +237,6 @@
237	237	**Storage:** SQLite or minimal database
238	238
239	239	**Entities:**
240		-
241	241	* Articles (input text/URL)
242	242	* Claims (extracted from articles)
243	243	* Verdicts (per claim)
...	...	@@ -245,7 +245,7 @@
245	245
246	246	**No complex relationships, versioning, or scenarios**
247	247
248		------
	244	+---
249	249
250	250	=== 3.2 Full System Data Model (V1.0+) ===
251	251
...	...	@@ -252,7 +252,6 @@
252	252	**Storage:** PostgreSQL (primary), Redis (cache), S3 (documents)
253	253
254	254	**Core Entities:**
255		-
256	256	* Claims (with versions, clustering)
257	257	* Scenarios (interpretations of claims)
258	258	* Evidence (deduplicated, provenance tracked)
...	...	@@ -262,7 +262,7 @@
262	262
263	263	**Complex relationships, full audit trail, federation support**
264	264
265		------
	260	+---
266	266
267	267	== 4. Component Architecture ==
268	268
...	...	@@ -272,7 +272,6 @@
272	272	**Full System:** Multi-component orchestration
273	273
274	274	**Responsibilities:**
275		-
276	276	* Route input through component pipeline
277	277	* Manage component state
278	278	* Handle errors and retries
...	...	@@ -279,7 +279,7 @@
279	279	* Coordinate quality gates
280	280	* Trigger review workflows
281	281
282		------
	276	+---
283	283
284	284	=== 4.2 Quality Gate Validator ===
285	285
...	...	@@ -286,7 +286,6 @@
286	286	**All Phases:** Present but evolving complexity
287	287
288	288	**Responsibilities:**
289		-
290	290	* Execute all configured gates
291	291	* Aggregate gate results
292	292	* Make publication decisions
...	...	@@ -293,7 +293,7 @@
293	293	* Generate explanatory messages
294	294	* Log quality metrics
295	295
296		------
	289	+---
297	297
298	298	=== 4.3 Review Queue Manager ===
299	299
...	...	@@ -302,7 +302,6 @@
302	302	**V1.0:** Full implementation
303	303
304	304	**Responsibilities:**
305		-
306	306	* Route low-confidence verdicts to review
307	307	* Manage reviewer assignments
308	308	* Track review status
...	...	@@ -309,7 +309,7 @@
309	309	* Implement audit sampling
310	310	* Generate review metrics
311	311
312		------
	304	+---
313	313
314	314	== 5. Architecture Decisions ==
315	315
...	...	@@ -316,7 +316,6 @@
316	316	=== 5.1 Why Single AKEL Call for POC? ===
317	317
318	318	**Rationale:**
319		-
320	320	* Validates core capability fastest
321	321	* Simplest to implement and test
322	322	* Fail-fast if AI fundamentally can't do task
...	...	@@ -325,12 +325,11 @@
325	325
326	326	**Trade-off:** Less granular control, harder to optimize individual steps
327	327
328		------
	319	+---
329	329
330	330	=== 5.2 Why Add Components in V1.0? ===
331	331
332	332	**Rationale:**
333		-
334	334	* Better error handling per step
335	335	* Independent optimization of each component
336	336	* Easier to add new capabilities
...	...	@@ -339,7 +339,7 @@
339	339
340	340	**Trade-off:** More complexity, more to maintain
341	341
342		------
	332	+---
343	343
344	344	== 6. Related Pages ==
345	345
...	...	@@ -346,10 +346,11 @@
346	346	* [[Requirements>>Test.FactHarbor.Specification.Requirements.WebHome]] - System requirements
347	347	* [[Design>>Test.FactHarbor.Specification.Design.WebHome]] - UI/UX design
348	348	* [[Roadmap>>Test.FactHarbor.Roadmap.WebHome]] - Implementation phases
349		-* [[POC1>>FactHarbor.Archive.FactHarbor delta for V0\.9\.70.Roadmap.POC1.WebHome]] - POC1 details
	339	+* [[POC1>>Test.FactHarbor.Roadmap.POC1.WebHome]] - POC1 details
350	350	* [[POC2>>Test.FactHarbor.Roadmap.POC2.WebHome]] - POC2 details
351	351
352		------
	342	+---
353	353
354	354	**Document Status:** ✅ Architecture Specified (POC1, POC2, Full System)
355	355	**Version:** V0.9.70
	346	+