Workspace - Pivot from "set of open panes" to a Finder-style miller column stack: TopBar / LeftSidebar / [section → entity → entity ...] / pinned text editor. openPanesStore is now an ordered Column[] with pushFrom / closeFrom / setStack; only one top-level section is rooted at a time. - New entity column panes: Term, Block, Association, Constraint, Requirement, Finding. Click-through navigation truncates deeper columns automatically. - LeftSidebar surfaces a pending-count chip per section (single-glance navigation cue) and spins its analyze ↻ via SVG Spinner whenever the LLM is working — including server-initiated runs caught by the runs poll, not just user-triggered ones. Analyze pipeline + persistence - Unified `concepts` pass (taxonomy + glossary in one LLM call) replaces the two-pass setup. Server still accepts ?section=taxonomy|glossary and normalizes them for back-compat. - model / requirements / detection (assumptions, risks, inconsistencies) + cross-layer validation rules (X1–X4: stale term link, unlinked formalism, undefined linked term, prose-only term). - Persistence: NarrativeDocument, ModelSnapshot, ChangelogEntry, TaxonomyTerm, RequirementEntry, Finding, AnalysisRun. Re-runs MERGE instead of replace: gentle update on existing items, suggested on new, deprecated on missing — same idiom for every artifact kind. User pins preserve "kept" decisions across re-analyses. - Migrations: pivot_text_first, add_requirement_linked_term, term_review_state, review_state_for_reqs_and_findings, add_term_definition_pinned. Concept ↔ ontology integration - linkedTermId on Block / Association / Constraint / Requirement. PromoteToolbar lets the user formalize a concept inline: + Block / + Association / + Constraint / + Requirement, all routed through applyOps so undo/redo and SSE work for free. - decideElement op for in-canvas keep/discard on review-pending model elements. User-authored definitions - TermColumn definition is click-to-edit. Save (Cmd-Enter / blur), Cancel (Esc), Reset to AI suggestion when pinned. - definitionPinned flag on TaxonomyTerm: future Analyze runs leave the user's text alone. setTermDefinition repo function + POST /api/projects/[id]/terms/[termId]/definition endpoint. - mergeTaxonomySuggestion + applyGlossaryDefinitions both pin-aware. UX/UI - StatusChip: single component for all state idioms (suggested, deprecated, accepted, dismissed, resolved, severity, validation code, confidence, warn). Replaces 5+ ad-hoc badge classes. - PaneControls (PaneViewTabs + PaneFilterChip): separates view-mode toggles from filter chips so toggling Pending no longer flips you off the current view. - PaneEmpty: unified empty-state with title + hint + action. - PaneDrawer: collapsible groups for Pending / Discarded review; cards group as Kept (top) → Pending (bottom drawer) → Discarded (Findings only, hidden when empty). Restore action recovers dismissed/resolved findings. - ConceptCard unifies Tree and A–Z views in Concepts; only Tree parents carry the chevron (no empty placeholder offset). - Type + spacing tokens (--text-xs..xl, --space-1..6, --lh-tight/ui/ prose, --radius-*) replace every ad-hoc value. - Buttons standardized to body sans 500 (was a mishmash of mono / display). - Card shells unified across Concepts / Requirements / Findings. Cleanup - Removed: LeftRail, FindingsPanel, IssuesPanel, SocratesDock, ProposalCard, SlashMenu, SlashExtension, slashSuggestion, CanvasHeader, TaxonomyPane, GlossaryPane, TermDetail (popover; now TermColumn). - Section ids in openPanesStore: dropped taxonomy/glossary, added concepts. localStorage migration runs on hydrate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.5 KiB
2.5 KiB
You are deriving a SysML model from a product-thinking document and a known taxonomy of terms. The output backs a visual ontology canvas the user will edit.
Inputs
- The prose document.
- The taxonomy term list — each label is a candidate block.
What to produce
A lean SysML model with blocks (and optionally associations, constraints, requirements). Prefer a small, accurate model over a large, speculative one.
Blocks
- Use the taxonomy as the primary source of block candidates. Most blocks should correspond to a taxonomy term.
kind:"system"for the overall thing being designed,"actor"for human/external roles,"block"for everything else.- Reuse the term's exact
labelas the block label. - Set
linkedTermLabelto the matching term so we can mark it as linked in the sidebar. Use the same spelling as the term list. - A block is allowed without a taxonomy term only when the document clearly implies it but no term was extracted (rare).
Associations
- Only include associations the document actually describes. No speculation.
- Verb phrase labels:
"guides","contains","reports_to". - Optional
linkedTermLabel: when the relationship itself is named in the taxonomy as a concept (e.g. there's a term "Mentorship" and the association is "Tutor mentors Student"), set it. Most associations don't have one.
Constraints
- Optional
linkedTermLabel: when the constraint is a concept on its own (e.g. the term "Daily Cap" and the constraint issessions_per_day <= 3), set it.
Requirements
- Optional
linkedTermLabel: when the requirement is fundamentally about a single taxonomy term (e.g. REQ-001 is about Personalization), set it. This is distinct fromsatisfiedBy(which links to blocks the requirement formalizes against).
Confidence
Score confidence ∈ [0, 1] honestly. Things straight from the prose: 0.8+. Reasonable inferences: 0.5–0.7. Speculation: leave it out.
Output
{
"systemOfInterestId": "tutor",
"blocks": [
{
"id": "tutor",
"label": "Tutor",
"kind": "system",
"linkedTermLabel": "Tutor",
"confidence": 0.95,
"properties": [
{ "name": "personality", "type": { "kind": "enum", "values": ["socratic", "encouraging"] } }
]
}
],
"associations": [
{ "id": "a1", "fromBlockId": "tutor", "toBlockId": "student", "label": "guides", "kind": "association", "confidence": 0.9 }
],
"constraints": [],
"requirements": [],
"overallConfidence": 0.8
}
Return ONLY the JSON object. No prose. No code fences.