research(eve): programmatic sources - unify framework registration - #2404
Open
AndrewBarba wants to merge 2 commits into
Open
research(eve): programmatic sources - unify framework registration#2404AndrewBarba wants to merge 2 commits into
AndrewBarba wants to merge 2 commits into
Conversation
Contributor
This was referenced Aug 22, 2026
ctgowrie
approved these changes
Aug 22, 2026
AndrewBarba
marked this pull request as ready for review
August 22, 2026 04:26
Signed-off-by: Andrew Barba <barba@hey.com>
Signed-off-by: Andrew Barba <barba@hey.com>
AndrewBarba
force-pushed
the
barba/programmatic-agent-sources
branch
from
August 22, 2026 14:23
3321534 to
7ad5939
Compare
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.
Summary
Related to #2347. Framework defaults and extension contributions currently bypass eve's filesystem compiler through separate loading, merge, routing, sandbox, and inspection paths. This proposal replaces them with one effective source graph: framework modules, extension packages and overrides, and application files compete for canonical path-derived slots before the ordinary compiler loads or normalizes a winner.
The plan makes physical backing required per compiled node, projects extension sources into final logical paths, and makes runtime, Nitro, bundling, and inspection consume the same manifest. It migrates ordinary tools,
connection_search, the default sandbox, and framework channels; confines genuinely native behavior to a closed kernel inventory; replaces agent-info v2 with a truthful v3; and makes deletion of the old catalogs, merge paths, fallbacks, and duplicate projectors an acceptance gate. Memory integration remains an explicit later lifecycle proof and is not claimed by this research PR.Review should focus on the required binding table, choose-before-normalize precedence, extension path projection, the closed kernel boundary, and whether the deletion ledger leaves any parallel source of truth.
Validation
Cross-checked the proposal against current compiler loading and module maps, extension composition, dynamic-tool durability, framework graph and Nitro routing, sandbox fallback, adapter rehydration, and both agent-info builders.
pnpm guard:invariantspasses; runtime tests are not applicable to this research-only change.Checklist
CONTRIBUTING.mdevepackagegit commit --signoff)Changeset not applicable: this PR does not modify the published
evepackage.Diff size
Docs — 1 file ·
+595 / -0The research plan now specifies the source model, composition semantics, framework migrations, native boundary, deletion gates, and validation required for a cross-cutting compiler/runtime refactor.
Implementation — 0 files ·
+0 / -0Not applicable.
Tests — 0 files ·
+0 / -0Not applicable for a research-only change.