Resolve exact installed Domain Pack artifacts - #166
Merged
Conversation
eamirian
force-pushed
the
codex/v1-installed-pack-resolver
branch
from
August 14, 2026 00:29
f6ff892 to
a2e45c0
Compare
eamirian
force-pushed
the
codex/v1-installed-pack-resolver
branch
from
August 14, 2026 00:42
a2e45c0 to
2100bbf
Compare
eamirian
marked this pull request as ready for review
August 14, 2026 00:51
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
ace.intelligence.packs.conformanceboundary while preserving the existingace.testing.domain_packcompatibility importdomain_packs/<pack-id>/manifest.jsonshape without compiling or conforming unrelated Packsconformance/activation_golden_fixture.jsonfor the requested Pack, then recompile and reconform only that Pack's declared bytes before returning an artifactCompiledPackRefV1match across pack ID, pack version, compiled-pack ID, and pack digestSafety boundaries
The resolver never imports Domain Pack packages, inspects or executes entry points, or treats a distribution version as the Pack version. It rejects missing, malformed, substituted, symlinked, nonconformant, provenance-crossed, and duplicate Pack material. Duplicate Pack identities fail closed even when their bytes are identical.
The provider-free conformance interpreter lives on the pure
ace.intelligence.conformancesurface. Installed distribution discovery is an application/host concern exposed fromace.application.installed_pack_artifacts; it depends only on the standard library and publicace.*contracts and interpreters. No implementation lives undercore.engine, and no boundary allowlist exception is added.An installed distribution may carry several inert Packs at different readiness levels. Valid manifest identities are indexed together, while only the exact requested Pack is compiled and conformed. An unrelated Pack without an activation fixture does not block an exact valid activation; requesting that unready Pack still fails closed.
Verification
ace_core-0.8.2-py3-none-any.whlworld_intelligence_aiwhile unrelated Packs remained inertDependency
World Intelligence currently packages Pack manifests but does not yet package the required fixed
conformance/activation_golden_fixture.json. Its installed Pack will therefore fail closed until the World repository adds one exact passing fixture and includes it as package data. This PR does not change World, activate a Pack, merge, publish, or release.