Wiki source code of POC Specification
Last modified by Robert Schaub on 2026/02/08 08:13
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | = POC Specification = |
| 2 | |||
| 3 | **This section contains detailed specifications for FactHarbor POC phases.** | ||
| 4 | |||
| 5 | **Core Philosophy:** Prove the AKEL automation works before building production features. Each POC phase validates critical technical capabilities. | ||
| 6 | |||
| 7 | {{warning}} | ||
| 8 | **Critical Innovation in POC1 Context-Aware Analysis:** | ||
| 9 | |||
| 10 | POC1 tests whether AI can understand that an article's overall credibility is not simply the average of its individual claim verdicts. An article with mostly accurate facts can still be misleading if it draws unsupported conclusions. | ||
| 11 | |||
| |
2.1 | 12 | See [[Article Verdict Problem>>FactHarbor.Specification.POC.Article-Verdict-Problem]] for full discussion. |
| |
1.1 | 13 | {{/warning}} |
| 14 | |||
| 15 | == POC Phase Navigation == | ||
| 16 | |||
| |
2.1 | 17 | * **[[POC Requirements>>FactHarbor.Specification.POC.Requirements]]** Complete POC1 & POC2 specification (v4.0) |
| 18 | * **[[POC Summary>>FactHarbor.Specification.POC.Summary]]** Executive overview | ||
| 19 | * **[[Article Verdict Problem>>FactHarbor.Specification.POC.Article-Verdict-Problem]]** Why context-aware analysis matters | ||
| |
1.1 | 20 | |
| 21 | == Roadmap Navigation == | ||
| 22 | |||
| |
3.6 | 23 | * **[[POC1 Roadmap>>Archive.FactHarbor 2026\.01\.20.Roadmap.POC1.WebHome]]** Core Workflow with Quality Gates |
| |
3.7 | 24 | * **[[POC2 Roadmap>>Archive.FactHarbor 2026\.01\.20.Roadmap.POC2.WebHome]]** Robust Quality & Reliability |
| |
3.8 | 25 | * **[[Requirements Roadmap Matrix>>Archive.FactHarbor 2026\.01\.20.Roadmap.Requirements-Roadmap-Matrix.WebHome]]** Phase assignments |
| |
1.1 | 26 | |
| 27 | == Key Specifications == | ||
| 28 | |||
| 29 | **POC1 Goal:** Prove AI can extract claims and evaluate them with context-aware analysis | ||
| 30 | |||
| 31 | **POC1 Output:** 5 components | ||
| |
3.3 | 32 | |
| |
1.1 | 33 | 1. Analysis Summary (context-aware, 4-6 sentences) |
| 34 | 2. Claims Identification (3-5 claims) | ||
| 35 | 3. Claims Verdicts (verdict + confidence + reasoning) | ||
| 36 | 4. Article Summary (optional) | ||
| 37 | 5. Usage Statistics (cost tracking) | ||
| 38 | |||
| 39 | **POC1 Philosophy:** | ||
| |
3.3 | 40 | |
| |
1.1 | 41 | * Context-aware analysis (article ≠ sum of claims) |
| 42 | * Cost efficiency tracking (viable at scale) | ||
| 43 | * Fail-fast learning (test critical capabilities) | ||
| 44 | |||
| 45 | **POC1 Success Criteria:** | ||
| |
3.3 | 46 | |
| |
1.1 | 47 | * AI quality ≥70% (including context-aware assessment) |
| 48 | * Cost per analysis <$0.05 (target) | ||
| 49 | * Minimal manual editing (<30%) | ||
| 50 | |||
| 51 | **POC1 → POC2 Decision Gate:** GO / NO-GO / ITERATE | ||
| 52 | |||
| |
2.1 | 53 | See [[POC Requirements>>FactHarbor.Specification.POC.Requirements]] for complete specification. |
| |
1.1 | 54 | |
| 55 | == POC vs. Full System == | ||
| 56 | |||
| 57 | |= Feature |= POC1 |= POC2 |= Full System | ||
| 58 | | Scenarios | ❌ Deferred | ✅ Multiple | ✅ + Persistence | ||
| 59 | | Evidence Display | ❌ None | ✅ With sources | ✅ + Quality scoring | ||
| 60 | | Quality Gates | 🟡 4 simplified | ✅ 6 comprehensive | ✅ + ML validation | ||
| 61 | | Database | ❌ Stateless | ✅ PostgreSQL | ✅ + Redis + S3 | ||
| 62 | | User Contributions | ❌ Read-only | ✅ Enabled | ✅ + Reputation |