Tag: record

Sep 03, 2026

A decision is stated for what it chooses; a prohibition is reserved for a constraint that has been verified

Sep 03, 2026

The status note is its own field

Sep 03, 2026

A frontmatter field can be backed by a scheme-local controlled vocabulary

Aug 25, 2026

A principle is written as a value, unless it is actually a rule

Aug 22, 2026

The configuration reference renders where its schema lives; every project gets its own record description

record

Aug 16, 2026

A link target is checked from where the prose renders

Aug 16, 2026

A scheme declares which statuses it uses and what they mean

Aug 16, 2026

A scheme whose status never varies is reported

Aug 16, 2026

Luria is a truth maintenance system, and should say so

Aug 15, 2026

Titles in a transferable scheme are checked against the project's own nouns

record

Aug 15, 2026

Prose frontmatter is what the generator renders, not what the author prefers

record

Aug 11, 2026

Worked configurations are executable examples, not prose

Aug 08, 2026

Bugs enter the record characterized: the minimal working example protocol

record

Aug 08, 2026

The draft signal: a contribution that asks for a verdict, not a review

Aug 07, 2026

The status reports are committed views, and the badges land on them

Aug 07, 2026

Migrations: renaming schemes and moving documents without losing the record's memory

Aug 04, 2026

The devlog is a journal: dated entries that persist, rendered into books

Aug 04, 2026

The read/write boundary: views in docs/, sources in record/

Aug 04, 2026

`url-ok` acknowledges foreign codes only

Aug 04, 2026

A remote constructs per scheme: dir, document + anchor, or url

Aug 04, 2026

A remote reference is a prefix, a delimiter and a uid — numbers are the special case

Aug 04, 2026

Wikilinks: `[[CODE]]` is a typed reference, and typing it changes the rules

Aug 03, 2026

Four layers of record, each with a test for what belongs in it

record

Aug 03, 2026

Contributions write fragments; shared documents are generated views

Aug 03, 2026

Status is a closed vocabulary in frontmatter, enforced by lint

Aug 03, 2026

Extracted with provenance, not imported

Aug 03, 2026

Principles are fragments too, rendered as a document

Aug 03, 2026

A document's filename is its code; the title lives in the frontmatter

Aug 03, 2026

A code that resolves to nothing is reported, not dropped

Aug 03, 2026

A foreign record gets a prefix; the config turns it into a URL

Aug 03, 2026

Remotes are public URLs, Luria is its own worked example, and every scheme versions

Aug 03, 2026

A reference may name a document before its URL resolves

Aug 03, 2026

The README's badges are counts derived from the record

Aug 03, 2026

luria

Explorer

Tag: record

A decision is stated for what it chooses; a prohibition is reserved for a constraint that has been verified

The status note is its own field

A frontmatter field can be backed by a scheme-local controlled vocabulary

A principle is written as a value, unless it is actually a rule

The configuration reference renders where its schema lives; every project gets its own record description

A link target is checked from where the prose renders

A scheme declares which statuses it uses and what they mean

A scheme whose status never varies is reported

Luria is a truth maintenance system, and should say so

Titles in a transferable scheme are checked against the project's own nouns

Prose frontmatter is what the generator renders, not what the author prefers

Worked configurations are executable examples, not prose

Bugs enter the record characterized: the minimal working example protocol

The draft signal: a contribution that asks for a verdict, not a review

The status reports are committed views, and the badges land on them

Migrations: renaming schemes and moving documents without losing the record's memory

The devlog is a journal: dated entries that persist, rendered into books

The read/write boundary: views in docs/, sources in record/

`url-ok` acknowledges foreign codes only

A remote constructs per scheme: dir, document + anchor, or url

A remote reference is a prefix, a delimiter and a uid — numbers are the special case

Wikilinks: `[[CODE]]` is a typed reference, and typing it changes the rules

Four layers of record, each with a test for what belongs in it

Contributions write fragments; shared documents are generated views

Status is a closed vocabulary in frontmatter, enforced by lint

Extracted with provenance, not imported

Principles are fragments too, rendered as a document

A document's filename is its code; the title lives in the frontmatter

A code that resolves to nothing is reported, not dropped

A foreign record gets a prefix; the config turns it into a URL

Remotes are public URLs, Luria is its own worked example, and every scheme versions

A reference may name a document before its URL resolves

The README's badges are counts derived from the record

A wrong reason is corrected in place and versioned; a changed choice is superseded