Identity
Answers who or what the requester is. Identity alone does not grant the right to cause a consequence.
Consequence authority
The right to compute is not the right to cause the next consequence.
Veklom uses consequence authority to name a precise machine-control boundary: whether this concrete execution, under its current identity, capability, policy, budget, time and runtime binding, may cause this specific bounded effect now.
Definition
Consequence authority is current, bounded and execution-specific.
Possessing code, state, a process image, an API credential or historical permission does not by itself establish current authority to mutate a governed target. The authority has to survive the full set of current constraints at the moment the effect is attempted.
Access
Answers which system or resource can be reached. Reachability is not current consequence authority.
Capability
Describes the bounded operation that may be requested, including scope, budget, target and time constraints.
Execution
Identifies the concrete runtime manifestation attempting the action. A copied or recreated runtime does not automatically inherit current authority.
Consequence authority
Determines whether this execution may cause this specific bounded effect now.
Evidence
Preserves what was authorized, attempted, observed and established after execution.
One governed consequence
Request
A human or machine proposes a bounded operation.
Bind
Identity, capability scope, target, budget, time and execution context are bound into current authority.
Decide
CAPPO evaluates whether the proposed consequence fits the authority that actually exists now.
Enforce
The effect path must fail closed when the current execution no longer satisfies that authority.
Observe
The resulting state or external effect is read back independently where the integration supports it.
Preserve
PGL / Gnomledger retains evidence so the record can outlive the execution that produced it.
Falsification standard
Authority is only meaningful if stale possession cannot reproduce the consequence.
Veklom treats these as machine invariants to test, not slogans to assume.
01
A copied token must not make a different execution current.
02
A restored snapshot must not resurrect expired or revoked consequence authority.
03
A recreated runtime must not inherit authority solely because it has the same code or state.
04
A revoked execution must be unable to produce the governed consequence through the tested enforcement path.
05
A successful request or healthy endpoint must not be promoted into proof that the external consequence occurred.
Decision boundary
CAPPO
Evaluates the governed consequence against current bounded authority.
Evidence boundary
PGL / Gnomledger
Preserves evidence and provenance without becoming an authority issuer.
Connection boundary
VLink
Carries governed connectivity without turning a connection into ambient authority.