Repository navigation
The noblefactor layer is a shared address, not devlore's list - #760
Merged
Merged
Conversation
added 3 commits
August 30, 2026 19:39
The header said "the tools a devlore-cli working environment needs" and "every entry is one this repository demonstrably uses". That is the rule for this repository's contribution, stated as though it were the rule for the layer. Base, team, and personal repositories each carry a Home/noblefactor and `writ deploy noblefactor` assembles all of them, so the next person to add one would have found an inclusion rule that does not apply to them. The name is a coordination key: it has to be identical across repositories owned by different people and stable as products are renamed, which is why it names the company rather than devlore. A Home/devlore in the personal or team repository would be empty. Also records a trap found while reading Segments.Match. It splits on ".", treats everything after the first part as suffixes, and requires every suffix to be a value the machine reports. A Home/noblefactor.secrets would therefore match nowhere, and would do it silently -- no error, no deployment. Sub-scoping belongs in the project name. The per-entry justifications are unchanged. That discipline was never the problem; only the ownership of the rule was.
It documented a mistake nobody made. The claim was true -- Segments.Match requires every suffix to be a value the machine reports, so a Home/noblefactor.secrets would match nowhere -- but it warned against a name no one had written, in a file whose job is to list packages. The real hazard in that neighborhood is #746: writ.segments is shipped in the defaults file and in the schema, and the command never reads it, so a custom segment cannot be declared at all. That belongs on the issue, and is already there.
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
1 participant
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.
Home/noblefactor/packages-manifest.yaml's header said "the tools a devlore-cli working environment needs"and "every entry is one this repository demonstrably uses". That is the rule for this repository's
contribution, stated as though it were the rule for the layer.
Base, team, and personal repositories each carry a
Home/noblefactor, andwrit deploy noblefactorassembles all of them. So the next person adding one would have found an inclusion rule that does not apply
to them.
The name is a coordination key
It has to be identical across repositories owned by different people, and stable as products are renamed --
which is why it names the company rather than devlore. A
Home/devlorein the personal or team repositorywould be empty.
Each repository decides what it contributes; this one contributes the tools its own work needs. The
per-entry justifications are unchanged: that discipline was never the problem, only the ownership of the
rule.
Verification
Comment-only. No package list changes, so
writ deploy noblefactorresolves exactly what it did before.