Skip to content

Design the layer-source model: roles, precedence, and configuration #468

Open

Description

@David-Noble-at-work

There is no architecture document for writ's layer model -- it lives in plan documents and in the code.
This task writes it, and settles: how a source is named, which role it fills, where that is configured, and
the precedence rule when two sources provide the same path.

The layer tree is packaging and contributes no configuration values; the config tree is a separate
model rolled up on source, scope and builtin. The document must keep them apart rather than unify them.


Epic: #466 · Feature: #467

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 layersThread:WritOriginCross-cutting: writ records and verifies where a deployment came fromtaskImplementation work item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions