Repository navigation
GraphPaper 0.7 — operational System One/JEV decision studio - #12
Conversation
…ity and finalize v0.7 documentation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 45a13c5edc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| def rerank_pack(p,clients,pack,query,budget=38000,required_ids=None): | ||
| if not getattr(clients.settings,'system_one_retrieval',True) or not Engine(clients).enabled:return pack | ||
| passages=pack.get('passages',[]) | ||
| items=[{'id':'passage_'+str(i),**item} for i,item in enumerate(passages[:18])] |
There was a problem hiding this comment.
Retain passages outside the semantic scoring window
When a source pack contains more than 18 passages and JEV returns scores, this slice excludes every later passage from ordered and therefore from the returned pack, even when the context budget has room. This can also omit an explicitly requested required_id whose first passage falls after position 18, so outlining or drafting silently loses selected evidence; include required passages in the scoring window or carry unscored passages into the budgeted sequence.
Useful? React with 👍 / 👎.
| for edge in edges.values(): | ||
| if edge.source==raw.id:edge.source=keep.id;edge.status='proposed' | ||
| if edge.target==raw.id:edge.target=keep.id;edge.status='proposed' |
There was a problem hiding this comment.
Remove internal edges when merging connected nodes
When the two merged nodes are directly connected, redirecting both endpoints converts that relationship into a self-referencing keep -> keep edge. Graph extraction and import explicitly reject such edges, while motif mining will treat this malformed edge as a real relationship and can generate single-node motifs from it; discard edges whose endpoints collapse to the same surviving node during the merge.
Useful? React with 👍 / 👎.
Implemented
Operational System One/JEV control across GraphPaper, with a real sidebar decision studio:
Verified before merge
Successful release candidate: https://github.com/AronAxe/GraphPaper/actions/runs/38521929515 . Exact checked/built source:
45a13c5edc762ed9ed0c9131c15edcdc73f79ef6.Synthetic provider fixtures validate transport, policy and UI behavior; no live JEV editorial-quality or cost-savings claim is made. Initial thresholds are engineering policies, not domain calibration.
Preservation and delivery
No user-machine access, private manuscripts, credentials or live model accounts. Existing graph-paper UI, approved header/schematic, project data, voice library, Graphify/Codex remain. Documentation updated for v0.7 and System One wiki guide added. Temporary integration files are absent from the final tree; release workflow contains no source-patch application step.
Merge triggers the main-branch release gates. Only the exact Windows archive that passes native tests and uploaded-checksum verification is publicly published as v0.7.0.