architecture.
4 of 121 decisions. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| ADR-077 | Publish a nested record as a section of its parent site, staged by its own config | site.include_records mounts a whole record inside another’s vault. Each is staged by its own config, because the source-versus-view test reads from the reading config’s schemes — so a parent publishing a child’s files directly emits both a fragment and the view it renders into. | Active |
| ADR-078 | A nested record’s views are generated and committed with the parent’s | luria index regenerates every nested record’s views from the root, and --check fails on a stale one, so they are committed like this project’s own. include_records moves out of [luria.site] in the same change: it says a project contains other projects, which generation needs as much as publishing does. | Active |
| ADR-094 v2 | A cited document gets a page, and where a citation points is configurable | A render = "document" scheme’s sources are published as pages, and a new cite key chooses whether a citation of its codes resolves to that page or to an anchor in the assembled view. This record sets “page”; unset keeps today’s behaviour. Rejected: emitting anchors that survive each publisher, and shipping the key without the pages, which sends citations off-site. | Active |
| ADR-095 | An acknowledgement can carry its own deadline | A directive may be written until <YYYY-MM-DD>; after that date find stops returning it, so every check behaves as if it were never written, and luria lint reports what expired. Rejected: a relative duration, which needs an anchor the file does not carry; and a version milestone, which needs a project-version concept luria does not have. | Active |