From 67c3e2d3d50ce7b49f299a1ca500d781864198fa Mon Sep 17 00:00:00 2001 From: Steven Jannette Date: Sun, 23 Aug 2026 21:50:50 +0000 Subject: [PATCH] Update README.md --- README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f7ad647..b5679a9 100644 --- a/README.md +++ b/README.md @@ -2,11 +2,16 @@ ![kongruity demo image.](kongruity_demo_image.png) -kongruity pulls in unstructured artifacts of the creative-engineering process -- to-dos, action items, agile tickets, Jira thread comments, Slack thread comments, retrospective notes -- and synthesizes them into semantically coherent, prioritized clusters that can be incorporated into implementation planning. +kongruity pulls in unstructured artifacts of the creative-engineering process, capturing "AHA!" moments scattered across an engineering team's disparate tools: action items or backlog in Atlassian/Jira, user story comments, Slack discussions, retrospective feedback. -In kongruity, the artifacts become "sticky notes." A board full of them looks chaotic. -With a click, they are semantically evaluated, grouped into thematic clusters with descriptive headers, rankable and exportable to project planning and execution tools. +It stores and synthesizes these into semantically coherent, prioritized clusters that can be incorporated into implementation planning. + + +In kongruity, artifacts become "sticky notes." A board full looks chaotic. With a click, a RAG-pipeline levearges Models trained to semantically evaluate, group, cluster and add descriptive cluster headers. + + +These are rankable, editable and exportable to sprint project planning tools. ## Clustering and evaluation: methodology