Sarmal Library

Library

Every Sarmal type, field and edge. These pages were not written by hand; they are generated straight from Sarmal's schema and regenerated whenever the schema changes.

Schema version: SNF-0 · v0.6 · Seal: 8031fb8fcffc113a

Navigate with the tree of life

The plan backbone is a tree. Pick a level and open its reference.

The smallest unit of progress, with a clear task, acceptance and boundary.

Open this level in the Library →

Tap a level, or use the Tab key, to select it.

Search a type or field

Families

foundation3 types

productive root / skeleton (shell→project→app)

plan7 types

contains (containment) — backbone

knowledge9 types

knowledge & experience (decision · formula · glossary · idea · experiment)

orchestration7 types

manages (operation: template · policy · workflow · hook)

agent5 types

identity + capability + memory + trigger

surface21 types

contains (UI tree — what the user sees)

law6 types

rule plane (immutable)

technology6 types

depends on (adapter: technology · MCP · tool · model · environment)

product7 types

produced software (fruit 🍎 — code · non-test artifact)

process6 types

execution trace (task · run · trace · git) — record created at run time

quality6 types

verification & observation (test · metric · log · security)

meta5 types

meta / record (taxonomy · status · reminder)

behavior2 types

UI-logic bridge (animation · state) — technology-agnostic intent

backend12 types

server surface (service · endpoint · table · queue) — the UI's counterpart

Edges

The relations that connect nodes to one another.

dependsOnA depends on B; it lays the foundation of the call chain
referencesA cites B (provenance); the ⟦Adım⟧ context cone
reminds⟦a:Hatırlatıcı⟧ binds into the context of ⟦Adım⟧ B (forward binding)
produceswhen A is built it produces B (a fruit 🍎)
managesorchestrator or agent A manages B
containsA wraps B (containment)
feedsA feeds data or context into B
appliestarget A applies rule B
basedOnrule or policy A is born out of decision B; it records the trail between a decision and a rule so that 'who decided this?' can be read straight off the graph
seasonthe time edge: ⟦a:Blok⟧ binds itself to the phase in force from its own file; the load cycle normalizes that binding into a virtual `çağır` (call) edge on the ⟦Faz⟧ side, so the panel, the report card and the phase-less-block audit cover both spellings unchanged — the conversion happens at a SINGLE point
governedByagent A is governed by constitution B
triggerswhen ⟦Tetikleyici⟧ A's structural condition is met it fires ⟦Beceri⟧ B
themethe design-system binding: which ⟦Tema⟧ contract a screen is dressed in (the theme-less-screen guard looks for this)
callsthe behavior edge: ⟦Düğme⟧ or ⟦Form⟧ A calls endpoint B
navigatesTothe navigation edge: A navigates to screen B
submitsTothe data edge: ⟦Form⟧ A submits to endpoint B
contractthe convergence edge: ⟦Uç⟧ A derives from contract B — the contract is written first
runsthe run edge: ⟦Döngü⟧ A drives the steps and orchestrations in B
usesthe technology and identity binding: ⟦a:Katman⟧ uses at most one concrete ⟦Teknoloji⟧ (MIM-1.4), and ⟦a:Proje⟧ uses either the shared ⟦KimlikKökü⟧ or its own (ORK-5); the target of the binding never merges identities, and this edge can never point at ⟦a:Takım⟧
teamthe ownership binding: ⟦a:Katman⟧ binds itself through this edge to the one or more ⟦Takım|s⟧ that run it (MIM-1.4 · ORK-2.4); the target may only be of the ⟦Takım⟧ type, the edge establishes no execution order, and it can never point at ⟦a:Teknoloji⟧