Repository policy
Lex policy files describe module IDs, boundaries, allowed edges, forbidden edges, and other architectural constraints.
Policy is useful when it is concrete enough for tools and agents to read: module boundaries, capability metadata, authority envelopes, and escalation rules.
Lex policy files describe module IDs, boundaries, allowed edges, forbidden edges, and other architectural constraints.
AXF capabilities can describe inputs, lifecycle state, expected side effects, and safe usage notes.
LexThority envelopes describe what this run may attempt and what must escalate.
LexRunner applies the relevant gates and promotion rules for the current plan.
Do not ask an agent to infer policy from company folklore when a small structured file or envelope can state the boundary directly.