JVNAUTOSCI-2600 A3r3: thin controller and bounded effects#310
Draft
witbrock wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
inconclusive.create_concepts,upsert_text_relation, andadd_relationship.von_chat_runsurface honest by filtering write effects from its advertised catalogue.Why
The preceding architecture accumulated Python-side guesses about intent and success. Those guesses blocked alternative model strategies, confused evidence collection with evaluation, and encouraged more case-shaped control code after each miss. This candidate subtracts that controller policy while retaining deterministic authority and effect truthfulness only where concrete harm or ambiguity was demonstrated.
Impact and boundary
Ordinary authenticated turns can now choose among broad delegated reads and a small generic representation aperture. No request classifier, domain resolver, prompt patch, automatic model router, merge, cutover, or production activation is included.
This is a stacked draft on PR #309 and is frozen at commit
51ccd68cff41519a0a4741f9ee7cd5fde4174a7bfor a bounded fresh-case experiment. Do not merge independently or before the human evidence gate.Validation
py_compile, andgit diff --checkpassed.Frozen live evidence
The bounded round is complete; there were no post-reveal code or prompt changes.
arXiv:2408.02603): the paper type, paper, and qualified source record committed after effect timeouts, but final synthesis timed out and the fallback falsely said nothing changed.arXiv:2506.03346): the paper and an analyst-inference predicate committed; the requested cross-paper relation did not. Final synthesis again timed out and the fallback falsely said nothing changed.General judgement: the model demonstrated useful cross-domain semantic judgement without case-specific controller code. The merge blocker is a general effect-completion/terminal-reconciliation defect: late commits remain indeterminate to the turn, and a final-model timeout can produce a false no-change narration. The evidence does not justify ecology/arXiv/Harry-specific Python, required predicate lists, or a stronger-model arm.
Recommended bounded successor: persist late completion against the existing
effect_id; reconcile fallbacks with effect/canonical evidence; reserve or route a measured final-response budget; and remove measured synchronous Atlas/index work that is not needed for the committed fact. Keep identity and authority checks. Then use known cases as regressions and fresh cross-domain ecology/deontology cases as unseen evaluation.Full evidence judgement SHA-256:
0b87dea4793acaf8eae25c187d5e723a55cde6f73c543d63243e2e51e7f13b17.PR remains draft and unmerged.
Atlas/handler diagnostic addendum
Independent log analysis found negligible MCP queue time (about 0.2–3.1 ms) but handler/database dominance: eight create deadlines at 8.7–20.0 s, seven late completions at 19.8–44.3 s, broad legacy-name scans returning 101 + 899 concepts, visibility reads over about 1,617 IDs, and relationship-extent refreshes of 1.0–3.9 s. A stronger model would not remove this cost.
The smallest measured performance candidates are to coalesce a whole logical create batch inside the existing deferred relationship-extent synchronisation scope; batch name/content/note enrichment into one existing text fetch; and avoid launching a successor mutation while the first non-cancellable handler remains live. Tightening legacy name search is separate because it changes compatibility behaviour.
The redacted Mongo diagnostic entry point itself failed with
NameError: _mongo_query_diagnostics_report, and the profiler fallback had no samples. Therefore no missing-index or winning-plan claim is made.Diagnostics addendum SHA-256:
e3c227e110ee7b8a259c560aeebc076404750a797d116347603e1a0b0688c622.