You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/PrompterOne.Core/AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,5 +46,7 @@ It owns TPS parsing, compilation, export, RSVP helpers, preview and workspace st
46
46
- AI script graph labels, descriptions, semantic scopes, tokenizer chunks, and knowledge-graph markdown input must come from compiled TPS display text through the TPS SDK so they match the clean prompter text; raw TPS source is allowed only for source ranges and structural metadata, not post-hoc string-cleaned visible prose.
47
47
- AI script graph semantic extraction must use an available LLM/chat-client path as the primary extractor. Regex, stop-word, capitalization, keyword, or hardcoded-domain semantic heuristics are strictly forbidden; when no LLM graph extraction is configured, the app may either show no semantic graph or run only an explicit user-requested tokenizer/vector similarity fallback based on `Microsoft.ML.Tokenizers` token vectors and distance calculations.
48
48
- Script graph tokenizer/vector fallback must use the tokenizer/vector primitives exposed by `ManagedCode.MarkdownLd.Kb` when that package provides them; do not keep a duplicate Core-owned tokenizer implementation.
49
+
- Script graph extraction must track the current `ManagedCode.MarkdownLd.Kb` graph model and use its metadata/front matter primitives such as entity hints, graph groups, related links, next steps, focused graph/search, and token topics before adding PrompterOne-owned graph glue.
50
+
- Script graph output should feel like an Obsidian-style writer knowledge graph: documents, people, topics, backlinks, related ideas, and neighborhood metadata are primary; TPS mechanics remain source metadata unless they explain writing meaning.
49
51
- AI and agent services must not use ad-hoc language heuristics for semantic meaning, intent matching, or action similarity. Prefer LLM extraction; the only non-LLM fallback allowed for similarity or search is explicit tokenizer/vector similarity based on `Microsoft.ML.Tokenizers`.
50
52
- Respect root maintainability limits. Large parser/compiler edits need explicit decomposition or documented exceptions.
Copy file name to clipboardExpand all lines: src/PrompterOne.Shared/AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,8 @@
44
44
- Script graph UI must expose an intentional analysis path when richer extraction is needed, and every graph mode should answer a concrete writer question such as "what is this about", "how are blocks connected", "which terms recur", "which references matter", or "where should I edit this idea".
45
45
- Script graph UI must not silently fall back to regex/keyword semantic extraction when LLM graph extraction is unavailable; regex, stop-word, capitalization, keyword, and hardcoded-domain semantic heuristics are strictly forbidden. In that state, show an explicit action to connect AI or run tokenizer/vector similarity analysis; the tokenizer path must be user-visible as a lower-fidelity fallback, not disguised as LLM semantic understanding.
46
46
- Script graph UI should surface tokenizer/vector similarity through the `ManagedCode.MarkdownLd.Kb` tokenizer path when available; do not add a separate browser or Shared-owned tokenizer implementation for the same fallback.
47
+
- Script graph UI should read like an Obsidian graph workspace: expose document metadata, tags/topics, people, backlinks/links, node neighborhoods, and source-jump affordances around the canvas instead of showing only a decorative graph renderer.
48
+
- Script graph UI must stay aligned with the current `ManagedCode.MarkdownLd.Kb` model; when that package adds graph metadata, focused search, entity hints, graph groups, related links, next steps, or token-topic primitives, PrompterOne should surface those concepts rather than flattening them into generic nodes.
47
49
- Assistant spotlight suggestions and script graph UI must not use ad-hoc language heuristics for intent or similarity. Use LLM-backed semantics when available, or explicit tokenizer/vector similarity over localized action descriptions and the user query when a non-LLM fallback is needed.
48
50
- Script graph editing must support a split source/graph workflow: the user should be able to inspect the graph beside the editor, click a meaningful graph node, and have the owning source range revealed or highlighted without leaving the graph workspace.
49
51
- Script graph split mode must expose a user-resizable divider between source and graph panes, and graph view must also support a graph-only workspace mode for focused exploration.
0 commit comments