Repository navigation
Epic: lore packaging and the registry #446
Description
Spec: 7-registry-knowledge.md
Plan: phase-8/lore-migration.md
Packages, manifests, the registry transport, and the lifecycle commands over them — prepare, install,
provision, verify, with traces recording what actually happened.
Three of its command families are open with FalseSuccess labels: registry, manifest and lifecycle
commands that report success without performing the work.
How lore relates to the pkg provider
Position, 2026-09-09: lore is a tool the pkg provider uses, not a target the pkg provider routes to.
apt, brew, port and winget are targets: the router chooses one and it installs. lore is the lifecycle
service: given a product, it constructs one pipeline per action — for deploy: resolve, prepare, install,
provision, verify — and the install stage is where a native manager is reached. The pkg provider's router,
the broker of #868 and #872, decides which manager; lore wraps that decision in the product's lifecycle.
Today the call runs the other way, writ deploy → lore → pkg.install → manager, and this epic is not
ready to introduce lore to the pkg provider. The position is recorded so the work under #551, #553 and
#784 has a direction. The boundary in one sentence: lore identifies the product and constructs its
pipelines; which manager installs a native release is the pkg provider's decision, at the install stage.
Activity
David-Noble-at-work commentedon Sep 10, 2026
Direction, 2026-09-09, recorded beside the position above and not ruled: the expected landing is a devlore
provider whose operations are the lifecycle actions on a devlore package, used by the pkg provider the way
this epic's position describes. Until then the manifest path keeps lore in place; the reasons are in
#814's plan under "Why the merge stays in lore": registry packages' pipelines run only through lore, the
trace and receipts read the package and phase annotations lore's subgraph carries, and
lore deployshares the planner.
David-Noble-at-work commentedon Sep 10, 2026
Placement, ruled 2026-09-09:
lore.Planner, the graph author that turns manifests into pipelines over theconstruction surface (
plan.Provider→ each method'sop.Planner), is this epic's. writ'sConfig.ManifestPlanneris the seam it is reached through today; the seam's interface is #814's, theplanner behind it is #446's.