Ask that of an agent that just did something you didn't expect. If the rule lives in a system prompt, a rules file, a skill and a chat from last spring, the answer is "one of several." Each copy was right once. They drift, and nobody can say which one the agent read.
We started SIGN to make agents reason more accurately over a company's rules. This post explains the mechanism and where it stops.
A paragraph is not a rule
In a page of prose, a hard limit and a passing remark look the same to a model. "Refunds over $500 usually need a manager" and "refunds over $500 need a manager" read almost the same. The agent has to guess which one is binding.
SIGN makes the difference explicit. Here is the example from the engineer guide:
@doc REFUND-001 [std, active, agents+employees] v1
@links REFUND-002
## Refunds over 500 dollars need a manager's approval before an agent issues them.
@rules
1. An agent may issue a refund of 500 dollars or less without approval.
2. A refund over 500 dollars needs approval from a support manager first.
@constraints
manager-approval
requires: support-manager approval on any refund over 500 dollars
forbids: an agent issuing a refund over 500 dollars without that approval
The constraint says what it requires and what it forbids. The header carries a type, a status and a version. REFUND-002 defines who counts as a support manager, so the agent doesn't have to guess that either.
Index plus fetch
Loading every rule into every prompt spends context on rules the task doesn't need. SIGN splits delivery in two. A compiler writes a short index the agent loads on every call. When a task needs a rule, the agent fetches the full document by its ID. The validator fails the build if the index grows past its budget, so it stays short.
Status does real work here. The compiler only puts active documents in the bundle. When you retire a rule, it drops out, instead of living on in an old prompt.
What SIGN does not do
SIGN is a notation and a set of tools. It doesn't decide who owns a rule. It doesn't approve a change. It enforces nothing at runtime. The reference tools are version 0.1 and will change faster than the spec.
Ownership, approval and the record of which version an agent was served are a different layer. At Five Deep that layer is Charter. You don't need it to use SIGN.
Try it
You need Git and Node.js 18 or later.
git clone https://github.com/sign-protocol/sign-lang.git
cd sign-lang
node validator/bin/sign.js validate --source examples
Expect warnings. The examples link to documents that aren't in the folder. Then write two documents of your own, one rule and one definition it links to, and compile them. The engineer guide walks through each step: https://sign-protocol.github.io/sign-lang/engineers/
I'd like criticism on three things: whether typed blocks beat markdown with front matter for this, how the index budget should work, and the provenance model. Open an issue on sign-lang, or post what you built in the GitHub discussion.
SIGN is open source under Apache 2.0. Five Deep maintains it.
Top comments (0)