luria

Tag: mechanism

58 items with this tag.

Sep 03, 2026
Source repairs are committed on the branch that authored them; generated views on the default branch only
- mechanism
- process
Sep 03, 2026
A workflow file cites decisions in a form the generation job's token can commit: by number, or in prose
- ci
- mechanism
Sep 03, 2026
Typed edges come from fields, and a superseded document names its successor in `superseded_by:`
- mechanism
Sep 03, 2026
The status note is its own field
- record
- mechanism
Sep 03, 2026
A finding names the key that declared its obligation; the record page lists the contract; no explain verb
- mechanism
Sep 03, 2026
A scheme can require one of several fields
- mechanism
Sep 03, 2026
A reference field declares whether it holds one code or many; a list where one was declared is a finding
- mechanism
Sep 03, 2026
A frontmatter field can be backed by a scheme-local controlled vocabulary
- record
- mechanism
Aug 28, 2026
A code relates to named URIs through one template vocabulary
- mechanism
Aug 27, 2026
Remote content endorsed by hash, drift compared offline
- mechanism
Aug 25, 2026
A suppressed build is branch protection's problem, not the lint's
- mechanism
- process
Aug 25, 2026
Init takes shorthand and writes ordinary tables
- mechanism
Aug 25, 2026
Files are UTF-8; the console is the platform's
- mechanism
Aug 24, 2026
Schemes declare their own shape — where the vocabulary lives, and what a field means
- mechanism
Aug 24, 2026
A scheme's template is a form, not a document
- mechanism
Aug 16, 2026
A scheme can constrain which of its tags combine
- mechanism
Aug 16, 2026
A link target is checked from where the prose renders
- record
- mechanism
Aug 16, 2026
A scheme declares which statuses it uses and what they mean
- record
- mechanism
Aug 16, 2026
A scheme whose status never varies is reported
- record
- mechanism
Aug 12, 2026
Temporary codes at filing; concretized and aliased at the serialization point
- mechanism
- process
Aug 11, 2026
The configuration reference is generated from the config schema
- mechanism
Aug 11, 2026
Worked configurations are executable examples, not prose
- mechanism
- record
Aug 11, 2026
Reference detection is scheme-driven, not three hardcoded patterns
- mechanism
Aug 11, 2026
A declared family replaces the default; settings still merge
- mechanism
Aug 11, 2026
The scaffold is planned from configuration, not copied from a tree
- mechanism
- process
Aug 10, 2026
The site wears the project's brand: artwork by path, favicon rasterized at build time
- mechanism
Aug 09, 2026
The record publishes as a Quartz vault: paths preserved, sources withheld, frontmatter surfaced
- mechanism
- process
Aug 07, 2026
The CLI surface is the workflows, not the module layout
- mechanism
- process
Aug 07, 2026
A fact the tree already states is populated, not demanded
- mechanism
Aug 07, 2026
The status reports are committed views, and the badges land on them
- mechanism
- record
Aug 07, 2026
A document can opt out of reference checking, and the report counts it
- mechanism
Aug 07, 2026
Fixture codes come from a registered prefix, not from the sequence
- mechanism
- process
Aug 07, 2026
Status enforcement is a dial — reported by default, failable by configuration
- mechanism
- process
Aug 07, 2026
One scaffold for every entry kind — `luria new`, driven by the config
- mechanism
- process
Aug 07, 2026
Drive the CLI with Fire: typed functions, derived flags
- mechanism
Aug 07, 2026
Migrations: renaming schemes and moving documents without losing the record's memory
- record
- mechanism
Aug 05, 2026
A generated view must be committed by something; the remedy says so where it is read
- process
- mechanism
Aug 04, 2026
The devlog is a journal: dated entries that persist, rendered into books
- record
- mechanism
Aug 04, 2026
The read/write boundary: views in docs/, sources in record/
- record
- mechanism
Aug 04, 2026
A remote constructs per scheme: dir, document + anchor, or url
- record
- mechanism
Aug 04, 2026
A remote reference is a prefix, a delimiter and a uid — numbers are the special case
- record
- mechanism
Aug 04, 2026
Wikilinks: `[[CODE]]` is a typed reference, and typing it changes the rules
- record
- mechanism
Aug 04, 2026
One ordered pmap over threads; width is an environment variable
- mechanism
Aug 04, 2026
Published to PyPI via trusted publishing; the scaffold ships inside the package
- process
- mechanism
Aug 04, 2026
Collection styles are configuration; the changelog shape is one of them
- mechanism
Aug 03, 2026
Contributions write fragments; shared documents are generated views
- record
- mechanism
Aug 03, 2026
Status is a closed vocabulary in frontmatter, enforced by lint
- record
- mechanism
Aug 03, 2026
The decision index is generated from frontmatter
- mechanism
Aug 03, 2026
References in prose are hyperlinks, enforced by lint
- mechanism
Aug 03, 2026
Reference schemes and paths are configuration, not constants
- mechanism
Aug 03, 2026
Document status is reported, not enforced
- process
- mechanism
Aug 03, 2026
One directive vocabulary, one scope rule
- mechanism
Aug 03, 2026
Principles are fragments too, rendered as a document
- record
- mechanism
Aug 03, 2026
A document's filename is its code; the title lives in the frontmatter
- record
- mechanism
Aug 03, 2026
A code that resolves to nothing is reported, not dropped
- mechanism
- record
Aug 03, 2026
A foreign record gets a prefix; the config turns it into a URL
- record
- mechanism
Aug 03, 2026
Remotes are public URLs, Luria is its own worked example, and every scheme versions
- record
- mechanism
Aug 03, 2026
The README's badges are counts derived from the record
- record
- mechanism

Created with Quartz v4.5.2 © 2026

Repository
Quartz