Glyph Tokens
Typed semantic carriers between natural language and governed operations
Purpose
A tokenizer token is a unit used by a model to process text. A Glyph Token is a typed semantic object used by a runtime to preserve operational meaning.
A Glyph Token may represent:
- proposition;
- constraint;
- authority;
- condition;
- substitution;
- uncertainty;
- source;
- action;
- block;
- approval;
- obligation;
- completion criterion.
The token is not an attempt to replace natural language. It is the intermediate form that lets a system distinguish statements with similar words but different force.
Example
“I might use Postgres.”
may compile into:
{
"type": "PROPOSAL",
"subject": "database_choice",
"value": "postgres",
"modality": "POSSIBLE",
"authority": "USER_SPEECH",
"accepted": false,
"source_ref": "capture:..."
}
while:
“Use Postgres for this project.”
may compile into a candidate directive. Project scope and authority still require validation.
Token lifecycle
Capture
→ candidate Glyph Tokens
→ source-span validation
→ authority and scope checks
→ accepted graph / rejected proposal / unresolved ambiguity
→ Work Order or surface projection
→ satisfaction or blocking evidence
→ receipt
A model may propose tokens. A deterministic compiler and policy runtime mint trusted identities.
Modality
Useful modalities include:
OBSERVED
INFERRED
DESIRED
PROPOSED
DIRECTED
AUTHORIZED
BLOCKED
COMPLETED
VERIFIED
ACCEPTED
The vocabulary prevents “finished” from collapsing tool completion, verification, and human acceptance.
Graph
Tokens form a graph:
objective
REQUIRES constraint
AUTHORIZED_BY decision
BLOCKED_BY missing_evidence
SATISFIED_BY artifact
A graph can compile into a PromptCapsule, Work Order, SurfaceDelta, decision page, or receipt.
Security
A typed token is not trusted because it is typed. Trust derives from:
- exact source;
- authority;
- signature;
- project;
- compiler policy;
- validator;
- current state;
- human approval.
Threats include authority spoofing, source tampering, graph bombs, hidden substitution, stale approvals, and prompt injection represented as high-authority tokens.
Evidence state
The project corpus contains a detailed Glyph Token protocol, lifecycle, security register, Jefe Frame architecture, and integration with GlyphCAS, SurfaceDelta, Work Orders, and receipts. The public note describes the public-safe semantic contract, not a claim of a universal language-understanding compiler.
Source register
- N01-S01 — Glyph Tokens Main Build Thread Handoff.
GLYPH_TOKENS_MAIN_BUILD_THREAD_HANDOFF.md - N01-S02 — LM Jefe Full System Specification.
LM_JEFE_FULL_SYSTEM_SPEC.md - N01-S03 — GlyphCAS Design Report.
How_we_can_make_CAS_lightning_fast_for_any_LLM_by_design_or_adaptation.docx