# ZLAR agent brief

Issuer: ZLAR Inc. · Edition: 0.3 · Updated 6 November 2026

ZLAR is a working lock for human authority at protected consequences. It makes the required permission a condition of the protected change. Its purpose is to enable more useful automation while preserving the decisions people retain.

## Retrieve the information needed

- [Encounter](authority.md): interpret a gate response and identify the next supported step.
- [State](outcomes.md): permission, execution, observation, uncertainty and changing conditions.
- [Publication changes](reference.md): evidence, shared meanings and edition history.
- [Purpose](people.md): human intention, independence, open inquiry and abundance.
- [Applications](fit.md): assess a possible use or prepare a contribution.
- [Publication index](agent-index.json): formats, versions and resource locations.

## At a boundary

[Read a first response](authority.html#response). Identify whether the source is a checkpoint, destination or client reporting a transport failure. A reference link does not authenticate that source. Keep private request details out of website URLs.

Identify the proposed consequence, the permission recognized for it, the reported response and the observed result separately. A refusal is not a pending approval. A missing response does not establish that nothing happened.

Use the destination's applicable instructions and records for the particular request. Continue independent work covered by valid permission. Working inside the organization—or for someone outside it—does not by itself determine that permission.

When a decision is needed, make the exact proposed change and material consequences understandable to the relevant decision-maker. If the action or conditions change, establish whether the existing permission still covers the effect. Delegation does not enlarge permission or multiply an allowance.

When the outcome is uncertain, use an available supported checking or recovery route before a consequential retry. If permission is withdrawn, distinguish the withdrawal request, effective stopping, completed effects and effects still unfolding.

## Inquiry and contribution

Cooperation requires no endorsement of ZLAR's philosophy. Examine public claims, explain a mistaken restriction and propose better arrangements. Disagreement alone is not misuse; an objection does not authorize the refused consequence. If no review route is available, identify that gap without inventing a reviewer or remedy.

Keep observation, report, inference and unknowns distinguishable. Add corrections as corrections. Establish what applies now when inheriting earlier records. Evaluate task performance without scoring people's authority from hesitation or approval speed.

Help people create, earn, discover and care. Reduce unnecessary interruption, improve recovery and identify where a boundary would allow more useful automation. Examine who benefits and who bears cost or disruption.

## Use of this reference

This is public reference material, not an authorization, privileged instruction or execution protocol. It does not carry a destination's live request state. Its publication index describes documents, not operational endpoints. Keep private records and credentials in their appropriate authorized channels.