Skip to content

New-DevloreKeyVaults lives in devlore-cli's own Home/noblefactor-ops.Unix and sources the base's Declare-BashScript #476

Closed

Description

@David-Noble-at-work

Feature: #475 — The base layer in noblefactor-ops. Rewritten 2026-09-07 for the ruling of that day; the
original text is below the rule.

The rule, as ruled 2026-09-07 (noblefactor-ops#147)

Code that takes a dependency on, or contributes to, a repository's stack goes into a directory named for
that repository — Home/noblefactor-ops[.<selector>] for anything that needs the base. Every bash script
sources Declare-BashScript, so every bash script depends on the base and none lives under common*.
Declare-BashScript itself ships from the base since noblefactor-ops#182; personal's side landed in
personal#174.

What is left in this repository

One script, scripts/New-DevloreKeyVaults: 77 lines, source "Declare-BashScript" by PATH, no --help.
devlore-cli is a writ layer with a Home of its own (Home/common/packages-manifest.yaml today), so the
script moves to Home/noblefactor-ops.Unix/.local/bin/, sources the sibling that the merged ~/.local/bin
provides, carries the bare # shellcheck source=Declare-BashScript directive, and is brought to spec on
the way — --help, a man page, bash and zsh completions — under an Apache-2.0 header like everything else
here. .Unix, not common: it needs az and runs nowhere git alone provides. The two .sh helpers in
scripts/ are repository tooling, source nothing, and stay.

This closes the original exit: the shared library ships from base, and nothing outside the personal
layer sources a file from it.

Acceptance

  • Home/noblefactor-ops.Unix/.local/bin/New-DevloreKeyVaults with its man page and completions;
    scripts/ holds only the two CI helpers
  • star lint shell . clean; with -P at a base checkout, shellcheck follows the source clean
  • after writ deploy, New-DevloreKeyVaults --help answers from ~/.local/bin
  • noblefactor-ops#147's plan reads Phase 3 done

Plan: docs/plans/feature/476-new-devlore-keyvaults-by-project.md.


Original text (2026-08-17): Declare-BashScript is sourced by scripts in devlore-cli and lives in
Personal/Home/common/.local/bin. That is the inverted dependency this epic exists to fix. Exit: the shared
library ships from base; nothing outside the personal layer sources a file from it.


Epic: #466 · Feature: #475

Activity

  1. changed the title [-]Move Declare-BashScript and the shared bin into noblefactor-ops[/-] [+]New-DevloreKeyVaults lives in devlore-cli's own Home/noblefactor-ops.Unix and sources the base's Declare-BashScript[/+] on Sep 8, 2026
  2. David-Noble-at-work commented on Sep 8, 2026

    @David-Noble-at-work
    ContributorAuthor

    Done. #862 moved New-DevloreKeyVaults into Home/noblefactor-ops.Unix/.local/bin with the sibling source, the bare directive, --help, a man page and both completions; the deploy check ran on Danoble-MBP-A on 2026-09-08 with devlore-cli registered as the team layer: ~/.local/bin/New-DevloreKeyVaults links into devlore-cli's Home/noblefactor-ops.Unix, --help renders the man page, the three assets are deployed. The original exit holds: the shared library ships from base (noblefactor-ops#182) and nothing outside the personal layer sources a file from it.

    Two things met on the way, neither this issue's: the empty layers/team placeholder had to be removed by hand before repo add team would accept the path (#840), and the deploy needed --conflict=skip because build 919b9521 no longer reads the store's traces and so refused 270 of writ's own links as foreign — filed separately. The port to star devlore keyvault create is #861.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Epic:LayerSplitSplit the dotfiles into base, team, and personal layerstaskImplementation work item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions