← Lexicor
Walkthrough · Technology
The Lexicor stack, diagrammed
Encoding, policy, and evidence — the machinery underneath the agent layer. Meaning stays checkable across hops, hops don’t restate full natural language, and every disposition becomes a portable record.
01 — Why the stack
Three outcomes of the same path — not a separate cost product, not a chat log after the fact.
Checkable meaning
Structured packets make “did meaning survive?” a yes-or-no at the boundary. Drift fails closed instead of being quietly accepted.
Less repeated work
Packets carry intent, constraints, and provenance so each hop doesn’t restate the full natural-language brief — less waste, same meaning.
Evidence at decision time
Allow and deny are written when the gate decides — a portable record you can hand over, not a reconstruction from chat later.
02 — Encoding — natural language to a verifiable packet
Loose task text becomes a sealed semantic packet: intent, objects, constraints, provenance, and tool intents — portable across harnesses.
LOOSE NATURAL LANGUAGE
"Refund order #8841, no more than $200, and log the justification.▌
LEXICOR ENCODE✓ encoded · signed
VERIFIABLE SEMANTIC PACKET
pkt: lexicor/1 · symtab v14sig ✓
intent commerce.refund
object order#8841 · amount ≤ 200 USD
constraints require justification.log
provenance agent support-triage · session s-77
tool-intents stripe.refund, ledger.append
packet sealed · portable across any carrierPILLAR 1 OF 3
FIG. T1 | SEMANTIC REQUEST ENCODING — TASKS, CONSTRAINTS, PROVENANCE, AND TOOL INTENTS AS ONE VERIFIABLE PACKET
03 — Policy — checked before the tool runs
The same packet hits a policy gate in-path. Who, what, scope, tool, and tenant must match the grant — mismatch denies and notifies.
PACKETcommerce.refund
→POLICY GATE · P-041
who support-agent✓
what commerce.refund✓
scope within grant✓
tool stripe.refund✓
tenant acme-co✓
✓ allow → stripe.refund
✗ deny → audit + operator
verdict: allow · all dimensions in grantdecision in-path · PILLAR 2 OF 3
FIG. T2 | POLICY-BOUND EXECUTION — CHECKED BEFORE THE TOOL RUNS, FAIL-CLOSED ON MISMATCH
04 — Governance plane — registry, policy, audit around one enforcement layer
Surfaces your teams use sit on top of one enforcement plane: inventory, versioned rules, live topology, and operator oversight.
REGISTRY
agents · capabilities
POLICY
versioned rules · in CI
AUDIT
every decision · replayable
↕
LEXICOR ENFORCEMENT PLANE✓ executed · decision appended to audit
↕
TOPOLOGY
who talks to what, live
ENFORCEMENT STATE
grants, trust, suspensions
OPERATOR
oversight · override · attest
registry, policy, audit, topology — all saw the same packetPILLAR 3 OF 3
FIG. T3 | VERIFIABLE AGENTIC GOVERNANCE — REGISTRY, POLICY, AUDIT, TOPOLOGY, AND OVERSIGHT AROUND ONE ENFORCEMENT PLANE
05 — Supporting machinery
Canonical IR, versioned transport, equivalence checks, controlled rendering, domain vocabularies, and path visibility — the contracts under the pillars.
lexicor / canonical-semantic-ir
actor support-triage
—performs→action refund
—on→object order#8841
amount ≤ 200 USDrequires justificationsession s-77
FIG. T4 | CANONICAL IR — ONE SHARED CONTRACT FOR "WHAT THIS REQUEST MEANS"
lexicor / versioned-semantic-transport
envelope · symtab v14 · checksum
overHTTPMCPagent msgv14 ↔ v14 · compatible → ✓ deliver
v14 ↔ v12 · mismatch → ✗ fail-closed, never guess
FIG. T5 | VERSIONED TRANSPORT — CARRIER-AGNOSTIC, COMPATIBILITY-CHECKED, FAIL-CLOSED
lexicor / semantic-equivalence-verification
canonical
→ render →natural language
→ re-encode →canonical′
✓ meaning preserved after the hop
FIG. T6 | EQUIVALENCE VERIFICATION — ROUND-TRIP PROOF THAT A HANDOFF PRESERVED MEANING
lexicor / controlled-rendering
one canonical
request
⇉request
natural languagecompact formJSON / protocol payloadtool-specific schema
FIG. T7 | CONTROLLED RENDERING — SAME MEANING, EVERY TARGET FORMAT
lexicor / domain-vocabulary-registry
core contract — stable, versioned
↑ extends without breaking ↑healthcare · PHI termsfinance · instrument typesenterprise · custom entities
FIG. T8 | ONTOLOGY REGISTRY — REGULATED DOMAINS PLUG IN CONTROLLED VOCABULARIES
lexicor / path-visibility
proposed action
grant browser → vendor-scraper
→grant browser → vendor-scraper
CHECKED BEFORE EXECUTION
agent pathtool grantout-of-grant blocked
FIG. T9 | PATH VISIBILITY — SEE THE REQUEST PATH BEFORE IT RUNS
ALSO IN THE STACK
provenance & audit trailinteroperability gatewayoperator oversight
checkablecompact packetsfail-closedreproducibleevidence-gradePatent Pending
The windows your teams work in — registry, control plane, operator console, and audit evidence — are on the product surfaces walkthrough →