What is an Authority Artifact?
An authority artifact is a .nomos file: an institution's rules in a form a system can evaluate, signed so that any change is detectable. Each rule states a condition and an outcome, cites the sentence of the source it came from, and names the facts it needs. Systems ask it before acting; anyone can check the signature with the published public key.
What it contains
Metadata (who issued it, its version, its scope); a data contract naming the facts the rules read; the rules themselves, ordered by priority, with outcomes such as allow, block or escalate to a named role; how conflicts between rules are resolved; and the seal, an Ed25519 signature over all of it.
Why sealed
A rule a system relies on must be the rule that was approved. The seal binds the content: change a threshold, a word or a priority and the signature no longer verifies. A new version is sealed separately, and the old one stays valid for checking decisions made under it.
How it is used
With nomos.can() (or POST /api/v1/can), a system gives the facts of an action and gets AUTHORIZED, DENIED or ESCALATED with the rule that decided. Verification needs only the artifact and the public key, so a system can check it offline.
Example
A refund agent can issue refunds up to a limit set in the returns policy.
The limit lives in the agent's prompt. Nobody can show which version of the policy the agent followed last Tuesday.
The returns policy is sealed as an artifact. The agent asks it before every refund; an amount over the limit is escalated to a supervisor, and each answer names the rule and the sealed version.
Frequently asked questions
Related concepts
See it in practice
Upload a policy, confirm its rules, seal them: any system can then check an action against them.