dtoro
4e725c0b2b
The editor now runs Socrates' three Phase-0-validated detection prompts against the live model, persists the findings, and surfaces them in a new FindingsPanel beside the IssuesPanel. Click any finding to focus its linked element across rail + diagram. Re-detect after model edits to refresh against the new state. apps/web/lib/llm/prompts/socrates - detect-assumptions.md / detect-risks.md / detect-inconsistencies.md promoted verbatim from phase-0 (Phase 0 corpus validated them 10/10). apps/web/lib/llm/detect.ts - Three sequential detection passes (parallel was OOM-prone on 4B local models — Phase 0 lesson). Each pass uses the Phase 0 JSON schema with jsonObjectMode fallback + chatJSON repair-retry. Fail-soft per pass: one busted pass returns [] rather than blowing up the whole detect. - post-validate strips hallucinated element refs (drops findings whose refs ALL fail to resolve; keeps findings with zero refs since some inconsistencies are genuinely about absences). apps/web/prisma/schema.prisma - Finding table: kind / text / linkedElementIds (JSON) / confidence / severity / validationCode / status / modelVersion / provider / model. - ResearchFinding table reserved for the Tavily integration that comes next — schema in place so we don't have to migrate again. apps/web/lib/db/repo.ts - listOpenFindings(projectId), replaceFindings(...) — replaceFindings wipes prior open findings in a transaction and writes the new set so re-detect doesn't accumulate stale findings. apps/web/app/api/projects/[projectId]/findings/route.ts - GET returns persisted open findings. - POST runs detect, persists, returns findings + meta (provider, model, durationMs, strippedRefs, droppedFindings). apps/web/components/editor/FindingsPanel.tsx - New panel, anchored bottom-right just left of IssuesPanel. Shows count summary (asm / risk / inc), detect / re-detect button, list grouped by kind (inconsistencies first, then risks, then assumptions), per-finding glyph + tag + severity + confidence + linked refs. - Click a finding row → focus its first linked element via the same setFocusBlockId path the rail and IssuesPanel already use. - "stale" indicator when the model version has advanced past the one the findings were detected against. EditorShell wires version + projectId through to FindingsPanel. Smoke-tested end-to-end: 12 findings returned (5 asm / 4 risk / 3 inc), 0 hallucinated refs stripped, ~37s on local gemma-4-e4b. Sample assumption "students are willing to engage with an AI tutor that is programmed to refuse providing complete solutions" — specific to Aristotle's refusal_policy, not a generic startup truism. Deferred to follow-ups: inline rail/diagram badges from findings, auto-detect-on-save, Tavily research, experiment modal.
1.9 KiB
1.9 KiB
Detect inconsistencies in a generated model
You will receive a seed payload (JSON) and a generated model (JSON). Your job: find inconsistencies — internal contradictions or structural problems in the model.
Categories
- Internal contradictions — two requirements that can't both hold simultaneously; a block whose properties contradict its kind; a constraint already violated by some property value
- Reference issues — an association whose endpoints don't make semantic sense (e.g., actor → constraint, or system → external actor with the wrong direction)
- Over-broad claims — a requirement that promises more than the system can deliver based on the blocks present
- Missing satisfiers — a requirement with no plausible block to satisfy it
- Unused elements — a block with no associations and no requirement satisfaction (may be dead)
Output
Return a JSON object with a single field findings. Each candidate:
text— the inconsistency stated clearly in one sentencelinkedElementIds— array of element ids involvedconfidence— 0.0 to 1.0validationCode— optional. If the issue matches a structural rule, include the code:M2(cyclic composition),T1(untraced requirement),T2(unused element),S1(dangling association endpoint). Otherwise omit.
Rules
- Return only candidates with
confidence ≥ 0.6— for inconsistencies, false positives are worse than misses - Cap at 6 findings
- An inconsistency must point to a SPECIFIC contradiction or structural defect, not a stylistic preference
- "This block has too many properties" is NOT an inconsistency
- "Requirement REQ-002 forbids what association A2 enables" IS an inconsistency
Schema
{
"findings": [
{
"text": "string",
"linkedElementIds": ["string"],
"confidence": 0.0,
"validationCode": "string (optional)"
}
]
}
Return ONLY the JSON object. No prose, no code fences.