Notes
This content is not available in your language yet.
Short pieces on how to check what an agent does, written by the Geometer team. Each one says what it covers and where its sources are.
- What you depend on when you build on Geometer
Free agent templates, no joining fee, stable monthly terms, shops that stay yours, and exactly what happens if a payment is late or someone leaves.
- A refund agent can pass every code scan and still refund twice.
What code scanning, evaluations and action checks each cover, and where they overlap.
- Questions to ask before an agent takes real actions.
A starting checklist for buyers, risk reviewers and builders assessing an agent that moves money, changes records or makes commitments.
- Taking a different route is not the same as breaking a rule.
Measure adherence to active constraints, rather than similarity to a preferred path.
- Approve the action that will happen.
An approval needs an exact scope, a current authority and a meaningful expiry.
- A timeout is not a failed refund.
Separate the intent, the attempt and the effect. Then reconcile what you actually know.
- Read the scope before the signature.
Three questions to ask of a certificate: what was checked, is the record intact, and does it still apply?
- A small experiment: retrying a refund can pay it twice.
A reproducible synthetic experiment shows why losing a reply and losing an effect are different events.
- How to read a Geometer certificate.
For a customer's security or risk reviewer: three gauges to read separately, who issued it, what a fingerprint lets you check and what a certificate cannot tell you.