Oracle quorum and signer controls

The deck framework defines a security governance layer that includes NAV signers and oracle quorum.

In practice, a VaaS vault can require multiple independent approvals before a NAV update becomes authoritative. For example, a vault may require a 3-of-3 NAV signer quorum, deviation checks, and role-based authorization before the new share price is published.

Oracle controls can include:

· signer quorum;

· maximum price deviation;

· stale data detection;

· source validation;

· manual review requirement for abnormal updates;

· pause on failed update;

· signed report hashes;

· onchain publication of report references.

This is especially important for products where subscriptions and redemptions are processed at NAV. If NAV is incorrect, both entering and exiting investors can be treated unfairly.