Identity and permission. Verified before execution.
Writ is the identity and permission layer for the autonomous enterprise. Deployed as an IdentityToken applet on WeilChain, it maps human identities from Entra ID and defines what each agent or human can call and which data they can access. @secured checks that authority before a protected applet executes.
One call allowed, one call refused.
Same identified caller, same protected applet, two different actions. See how @secured checks the authority recorded in Writ before execution.
An authority check at call time
@secured checks Writ’s identity and permission record before the protected applet receives a call.
Illustrative
Keep identity and permissions in one verifiable record.
Credential-based access
Access depends on a credential
- A bearer credential can confer its permissions on whoever presents it while it remains valid.
- A leaked standing credential can expose access until it expires or is revoked.
- The credential by itself does not establish a full record of human and agent authority.
- An application must still determine whether that caller is authorized for the requested operation.
Writ
Authority is checked against Writ
- One tamper-evident record defines identity and permitted actions for agents and humans.
- Entra ID human identities map into Writ bidirectionally.
- Writ defines what each actor can call and what data it can access.
- @secured checks the record before calls enter protected applets.
Identity and authority, enforced together.
Identity and permissions together
Writ is the authority record for both agents and humans. Their permitted calls and data access live in tamper-evident state rather than in standing bearer credentials.
Checked before it runs
Any call into a protected applet is checked against Writ's structural, tamper-evident state before it executes, not reconciled afterwards.
Build on your existing IAM
Human identities already managed in Entra ID map bidirectionally into Writ. Agent identity extends your existing IAM instead of creating a disconnected replacement.
Identity, permissions and enforcement, answered.
What security teams need to know before agents or humans act through protected applets.
What is Writ?
Writ is Weilliptic’s identity and permission layer for agents and humans, deployed as an IdentityToken applet on WeilChain. It records what each actor can call and which data they can access. @secured checks that authority before protected applets execute.
How is a Writ different from an API key or a bearer token?
A bearer token carries access rights to the caller. Writ keeps identity and permission information in tamper-evident state and lets @secured check it at the protected applet boundary, without relying on standing bearer credentials for that authority.
What does Writ authorize?
Writ defines an actor’s authorized calls and accessible data. @secured checks the relevant permission against Writ’s recorded state before a protected applet runs.
What happens when an agent lacks permission?
If the caller lacks the required permission in Writ, @secured refuses the request before the protected applet executes. The demonstration above illustrates an allowed call and a refused call.
Does Writ replace our existing IAM?
No. Human identities already managed in Entra ID are mapped into Writ bidirectionally. Writ extends that identity model to agent authority, so existing enterprise IAM remains part of the architecture.
How does Writ connect to Entra ID?
Human identities already managed in Entra ID map bidirectionally into Writ. That extends existing enterprise identity management to agents without replacing the directory.