Aegis Treasury

Supporting surface

Operator guidance

Knowledge & Guidance

Use this page as an honest guide to the shipped MVP, its trust surfaces, and the routes that remain demo previews. It is not a full documentation portal yet.

Live MVP loopPublished trust surfacesPreview routes labeled in-app

For judges under time pressure, the core story is simple: submit an evaluation on `/evaluation-dashboard`, inspect the privacy split on `/decision-result`, then review the durable trail on `/evaluation-history`.

Documentation Hub

A truthful review hub for the shipped MVP, its preview routes, and the trust surfaces that are actually published today.

terminalDeep dive

What is actually shipped

Open the published manifest and discovery docs, then follow the live three-step evaluation loop instead of inferring functionality from the broader UI shell.

Open the agent manifestarrow_forward
security
rocket_launch

Live MVP checklist

Use the evaluator, open a result, and verify the durable trail before exploring the preview-only routes.

  • Run one evaluation from the dashboard
  • Inspect the private/public reasoning split
  • Open the hosted receipt and log artifacts
gavel

Screen registry

Review which routed screens are live MVP surfaces versus preserved submission previews.

Need direct assistance?

The support workspace is a labeled preview route today, but it remains useful for judges who want to see how the broader operator product could expand.

Reviewer checks
Dashboard evaluation loop
Live MVP route
Receipt publication lane
Published JSON
Discovery endpoints
Inspect live
Trust direction

Privacy boundary and trust-layer direction

Aegis keeps the canonical reviewer story bounded: private reasoning stays inside the originating browser session, while public receipts, logs, and discovery docs remain inspectable.

Hosted receipts

Hosted receipt artifacts and decision packages keep each evaluation reviewable without claiming signed or immutable proofs.

OPEN MANIFESTchevron_right

Private lane discipline

Sensitive treasury policy interpretation stays out of the public evaluation APIs and remains confined to the originating browser session.

Threshold approvals preview

Signer-review and quorum concepts remain visible as labeled operator-facing preview controls rather than pretending to be fully live.

Frequently asked questions

Does Aegis expose our private treasury policy?

No. The product is designed to separate private reasoning from public-safe outputs, so the external recommendation does not need to reveal confidential internal constraints.

What does the ERC-8004 layer actually do here?

It anchors the trust story: identity, manifests, receipts, and reviewable logs that make agent outputs more credible and auditable.

Why is this framed as a service on Base?

Because the product should feel like a callable treasury decision service, not just a static analytics dashboard. Base is the distribution and service layer.