Skip to content

01_reference_grammar.md

Latest commit

 

History

History
58 lines (44 loc) · 2.27 KB

01_reference_grammar.md

File metadata and controls

58 lines (44 loc) · 2.27 KB

Semantic Reference Grammar (SRG)

This document defines the invariant concepts that must be preserved in all rewrites of the LogLine papers. Each component has a core invariant that cannot be removed or altered without semantic loss.

Component Invariants

Component Invariant Concept Expression Range Must Survive in Rewrites
LogLine Intent → Proof JSON / Natural language 9 fields of accountability: who, did, this, when, confirmed_by, if_ok, if_doubt, if_not, status
TDLN Intent → Deterministic structure AST / Hash / Semantic ISA Same hash for equivalent meaning; byte-identity via Json✯Atomic
UBL Physics validation layer Ledger / Membrane Conservation + authority checks; blind to JSON/intent
Json✯Atomic Byte-stable serialization JSON profile Lexicographic sort + deterministic encoding; Policy Pinning mechanism
Trust Architecture Risk-tiered governance ABAC / Pactum 5 risk levels (L1-L5) + multi-sig proof; Shadow Entity as structural security
Trinity Agent metabolism Loop runtime 3-plane continuity (OFFICE/UBL/Messenger) + AriaMotor

Dependency Graph

LogLine
 ├─ uses → TDLN
 ├─ validated_by → UBL
 ├─ serialized_with → Json✯Atomic
 ├─ governed_by → TrustArchitecture
 └─ metabolized_in → Trinity

TDLN
 └─ depends_on → Json✯Atomic (for byte-identity)

UBL
 ├─ depends_on → TDLN
 └─ depends_on → Json✯Atomic

TrustArchitecture
 └─ depends_on → UBL

Trinity
 ├─ depends_on → UBL
 ├─ depends_on → TDLN
 └─ depends_on → Json✯Atomic

Rewrite Rules

  1. Never delete a claim that can be verified or falsified
  2. Delete only stylistic redundancy or narrative scaffolding
  3. Preserve invariant formalism (proofs, equations, field definitions)
  4. Compress expressions (language, examples, metaphors)
  5. Use cross-references instead of duplication

Validation Checklist

Before any rewrite, verify:

  • All required fields/concepts are present
  • Mathematical formulations are preserved
  • Dependencies are correctly referenced
  • Core invariants are intact
  • Only expression (not meaning) has changed