SNAXK · judgement before action
A judgement engine for agentic work.
Surface the ownership, boundaries, stop conditions, evidence and review a person needs before long-running agentic work moves.
SNAXK 0.10.8
Before the work moves.
Signal
What changed?
What changed?
Boundary
What may happen?
What may happen?
Evidence
What can be inspected?
What can be inspected?
The judgement layer
Fast output is useful. Accountable judgement is what makes it operational.
SNAXK asks a quieter set of questions before an agent continues: what changed, how much confidence is justified, which boundary applies, and what evidence must remain visible afterwards?
Understand what this action could change.
Slow down when confidence and consequence do not match.
Concept model
A loop that can pause itself.
Each move leaves a trail. Routine work can continue. Meaningful uncertainty reaches a boundary, and consequential work returns to review.
01Signal arrivesnotice
02Meaning is checkedinterpret
03Boundary is appliedslow · stop · ask
04Evidence is carriedrecord
05Review changes the next movelearn
Five deliberate moves
Signal, meaning, boundary, reflection, review.
The loop is intentionally smaller than the systems around it. Its job is to help people inspect why an agent continued, paused, escalated, or changed course.
Fast heuristic pass
Scan messages, events, and signals before action. The first pass asks whether anything meaningful is happening.
Meaning check
Separate routine noise from work that is risky, surprising, sensitive, valuable, or likely to affect a human.
Bounded route
Triggered cases move through judgement boundaries: slow down, stop, escalate, adapt, or ask for human review.
Reflect overnight
The system does not carry every reaction forward. It reflects, compares, and waits before changing behaviour.
Reviewed carry-forward
Only changes that survive review become part of the agent's future judgement.
Stop lines
A boundary should be visible before it is crossed.
Permissions, privacy, safety, spending, publishing and accountability are not exceptions to tidy up later. They are part of the route.
-
01
When to slow down
High consequence, weak evidence, unfamiliar context, or mismatched confidence.
-
02
When to stop
A request crosses permission, privacy, safety, spending, publishing, or accountability boundaries.
-
03
What to share
Judgement includes deciding what is appropriate to reveal, quote, remember, or pass to another system.
-
04
How to adapt
The same action may be right for one person, wrong for another, and unclear until the context is reviewed.
Chief Agentic Officer
The board needs to inspect the judgement, not just the output.
A Chief Agentic Officer needs a clear view of what agentic work exists, who owns it, which boundaries apply, how uncertainty escalates, and what evidence survives after the work is done.
01Ownership
02Boundaries
03Evidence
04Escalation
05Measurable trust
Sibling systems
Visible work and visible judgement belong beside one another.
Orchistra keeps agent work visible and coordinated. SNAXK helps decide what may proceed, what should stop, and where human judgement is required.
Orchistra
Keep the work visible. Let judgement decide what happens next.