Understand.
Inspect. Review.
The proposed workflow, not instructions for a live wallet or trading service.
Your context.
A reviewable proposal.
01 — DEFINE THE DECISION
Name the question, the people affected, your constraints and what would count as a useful result. Keep assumptions separate from observations.
02 — INSPECT THE SOURCES
Circle's intended role is sourced observation (IS). Preserve where each claim came from, when it was captured and whether you have permission to use it.
03 — COMPARE POSSIBILITIES
RealityFutures' intended role is uncertainty-bearing forecasts (COULD). Compare rival possibilities and preserve uncertainty; a forecast is not a fact.
04 — REVIEW THE PROPOSAL
Agentz is designed to assemble an unsigned recommendation (SHOULD or SHOULD-NOT), including alternatives, risks, constraints and missing evidence.
05 — KEEP AUTHORITY SEPARATE
A proposal cannot authorize its own execution. Any consequential action needs the exact applicable external mandate and recognized human signatures. This site performs none of those actions.
A website is not
an operational release.
Available here: seven informational pages, a browsable APU.bot site outline and a browser-only planning worksheet. The Family office and Murmur destinations explain their intended roles. The worksheet formats user-authored questions without a model, advice, source verification, upload or persistence. No account, wallet, model key or payment is needed.
The intended app address is agentz.skyzai.com. This preview does not verify that destination or offer app access. Integrated Circle → RealityFutures → Agentz operation is a design contract, not a capability demonstrated here.
SOURCE & BUILD
An operational release needs a source-verified build, dependency versions and a reproducible artifact tied to its exact release.
PERMISSIONS & CONTEXT
Any private context integration needs an authorized connection, expiring and revocable grants, and a derived context view preserving provenance and revocation.
AUTHORITY & RECOVERY
The execution boundary needs exact scope, expiry, revocation, authorized human signers, recovery and tested refusal paths. A design promise is not a guarantee.
INDEPENDENT EVIDENCE
Runtime behavior and outcomes need evidence independent of the proposal and its local fixtures. UI tests do not demonstrate customer outcomes.
One loop.
Distinct responsibilities.
The workflow guide explains intake, alternatives, audit, unsigned staging and the external authority boundary. The status and limits page explains what would justify stronger claims.
Inspect before you act.
Explore the proposed workflow and its open release gates. This preview asks for no funds, keys or identifying information.