luria

Concept: Record theory and self-governance

3 min read

Graph View

A useful abstraction for a Luria record is:

K = (O, M, R, E)

where:

  • O is the ontology: the schemes, vocabularies, relations and fields the record can express;
  • M is governing knowledge: rules about how the record is interpreted and changed;
  • R is subject-level knowledge;
  • E is executable machinery: lint, indexing, chains, reports, publication and export.

The notation is not required to use Luria. It names the distinction this page develops: a record contains both knowledge about a subject and knowledge about how that knowledge is represented, checked, and revised.

Some knowledge describes a subject.

Some knowledge describes how knowledge about that subject should be represented, interpreted, and changed.

That distinction gives Luria a natural two-level interpretation.

Subject record

Call the subject-level knowledge R.

Examples:

Use renewable leases for durable jobs.
Paper LIT-042 supports technique X.
Policy P applies to contractors.

Governing knowledge

Call the governing knowledge M.

Examples:

Every superseded decision identifies a successor.
A SOTA recommendation requires evidence.
Generated views are not authoritative sources.

Then the rough judgment:

M; R ⊢ x

means:

under the current record and its current governing rules, does this object or relation remain admissible?

Governance can be proactive or reactive

A process rule does not have to wait for repeated failure.

It may arise from:

  • an incident,
  • a near miss,
  • a foreseeable vulnerability,
  • experience elsewhere,
  • repeated friction,
  • a deliberate policy.

The important move is making a consequential norm explicit when doing so helps.

Executable and discursive rules

Some governance can become mechanism:

Superseded decisions must name a successor.

Other principles require judgment:

Introduce a new abstraction only when it reduces more complexity than it creates.

A mature record theory contains both.

DP-5 describes the progression from prose toward convention, mechanism, and guarantee when that promotion is warranted.

Self-amendment

Once process rules themselves have identity and standing, the record can preserve how its governance evolves.

A process rule may even govern how process rules are changed.

That does not require an infinite tower of meta-records, and Luria has no special machinery for it. It is a modelling pattern: a project that files its process rules as ordinary scheme documents — this repository’s decisions and design principles are an example — gets identity, standing, supersession and citation checking for its governance from the same mechanisms that serve its subject record.

Documentation as a governed dependent

Luria’s own docs participate in this layer.

A sentence saying:

luria init scaffolds from configuration

depends on ADR-048.

If ADR-048 becomes inactive, the sentence should be surfaced for review.

Documentation citations are therefore maintenance edges, not bibliography.

Backlinks