Historical research • No active product commitment

LexThority is historical authority research.

LexThority is retained as historical research, with no active product commitment. The design notes below document an earlier exploration; they are not an active product roadmap or a supported installation recommendation.

Authentication and effect authorization remain necessary across the stack. ContextForge is a separate proposed context-linking library; it does not inherit authority responsibilities or authorize execution.

Historical source Stack context

Core contract

ThorityEnvelope
  what this run may attempt

EffectRequest
  what an agent or adapter is about to do

ThorityDecision
  allow | escalate | deny

EffectReceipt
  what was decided and what happened

Why it matters

Capabilities are not authority

AXF may tell an agent how to run a deploy capability. LexThority explores where the authority boundary should sit before a run mutates something important.

Personas are not credentials

LexSona can express posture and caution. LexThority is exploring how that posture relates to concrete effects, envelopes, and receipts.

IAM remains the source of truth

LexThority should not replace OAuth, cloud IAM, GitHub permissions, or enterprise brokers. The research question is how agents should describe and record boundary crossings around those systems.

Stack boundary

LexSona	Posture, duty, default caution, role-like context.
LexThority	Historical authority boundary research.
AXF	Workspace bearings, capability declarations, and effect hints.
Adapters	Wrappers around tools such as git, gh, cloud CLIs, and orchestrators.
Lex	Receipts, memory, denials, fallbacks, and learned access reality.

Historical prototype shape

Classify

Classify an attempted command or effect, starting with simple gates like `git push`.

Check

Evaluate a structured effect request against an envelope and return a decision.

Execute dry-run

Wrap an attempted command path and produce receipts without pretending to own the whole runtime.

npm install
npm run build

npm run cli -- classify -- git push origin feature/test
npm run cli -- check examples/effects/git-push.json \
  --envelope examples/envelopes/thority.local.engineer.json
npm run cli -- exec --dry-run \
  --envelope examples/envelopes/thority.local.engineer.json \
  -- git push origin feature/test

Anti-drift rule

If LexThority starts scheduling agents, managing swarms, owning credentials, or modeling every standard operating procedure, it is drifting. The earlier research target was the boundary around meaningful effects, not the whole runtime.