Decoding the ZAM Eagle Eye Council Reports – Mission Zambia Stake Pool

A Reader’s Guide to Proposal Audits in the Cardano Ecosystem

Version: Council Engine v0.11.6 (Beta)
Operated by: Mission Zambia Stake Pool (ZAM)
Mascot: African Fish Eagle | Style: Wise Mentor

Why the Eagle Eye Council Exists

Cardano’s treasury and governance decisions shape the future for millions. Yet many proposals lack clear evidence of technical soundness, delivery capability, or suitability for low-resource environments. The ZAM Eagle Eye Council was created to change that.

We are a forensic audit framework. Our mission is simple: protect the community treasury while empowering the Edges. We focus on proposals from Project Catalyst, gov.tools, Cardano Improvement Proposals (cips.cardano.org), and Ekklesia (app.ekklesia.vote).

Our core guardrails come from the Horizon Covenants:

Sovereignty: Users retain final control over assets and data. No central custodians. Keys stay with users.
Open-Source Freedom: Code must be public, permissively licensed (Apache 2.0 or MIT), and free of legal toll-gates.
Private by Default: Prioritise Zero-Knowledge proofs to protect personal data.
Equity for the Edges (The Field Manual): Tools must work under real-world constraints common in the Global South and low-resource settings:
Initial payload or sync must not exceed 50 MB (with limited exceptions for deferred sync where the UI layer stays light).
Fully functional at 128 kbps bandwidth with 30% packet loss tolerance.
Minimum hardware baseline: ARM-mobile browser or 4 GB RAM laptop.
Mandatory local state management (IndexedDB or equivalent) for offline resilience.
The Sunlight Clause: Absolute transparency in spending and reporting. No administrative black boxes.
Accountability: The Burden of Proof applies at all times. Absence of evidence is treated as a negative signal.

These are not suggestions. They are the baseline we measure against. Proposals that meet them strengthen Cardano for everyone, especially communities in Zambia and similar environments where connectivity, hardware, and trust assumptions differ from high-resource settings.

The Four-Winged Report: How We Communicate Our Findings

Every audit produces four outputs. The first is internal (shared with the Coordinator and DReps on request). The other three are public.

Output 1: The Forensic Blueprint (Internal Workbench)

This is our raw audit trail. It shows exactly how we reached every conclusion. High-density tables, no narrative fluff.

Key tables include:

Horizon Ledger: Proposal metadata at a glance. Title, direct URL (the ANCHOR), requesting entity, requested budget (ADA and USD equivalent where applicable), duration, submission date, ecosystem category, and domain scoring profile (Full Rubric for Catalyst and gov.tools; Partial for CIPs and Ekklesia with specific adjustments).
Link Registry: Every hyperlink extracted from the proposal text. Classified by type (Proposer Identity, Team Identity, Delivery Evidence, Financial Evidence, External Reference). Each link receives a Veracity Handshake before we rely on it:

Direct ping to confirm the URL is active (or Unverified if direct access unavailable; Google Search does not count as a ping).
Extract 1-3 unique lines of content as a verbatim snippet.
Classify the signal (Code, Documentation, or Claim).
Confirm recency and flag any stale content. Only Active links with supporting snippets can serve as primary evidence citations. Dead or Unverified links cannot be used to prove claims.

Talon Extraction: A stripped technical summary. What the team claims to build, the technology stack, stated deliverables, integration points, and dependency chain. Marketing language is removed. Minimum five bullets, maximum twelve. Pure mechanics.
Scoring Ledger: The complete scored rubric. Five dimensions with binary Yes/No per criterion. Every Yes requires an independent external Artifact Citation (commit hash + repo URL, live deployed URL with ping result, audit report link, etc.). Narrative claims without citations score No automatically. Row 1 is always the Hard-Fail Gate. If primary evidence links are dead, critical black boxes exist, or mandatory inputs are missing, scoring halts and the verdict becomes Grounded regardless of other points.
Talon Registry: The record of any Elite-level Talon Marks awarded (+1 modifier per dimension). Each entry must contain five complete fields:

Dimension being commended.
Which Fellow domain authority awarded it.
Rationale: 2-4 sentences explaining why this evidence represents Elite standard, not merely a standard Yes.
Backing Evidence: Independent external source (URL with ping result and snippet, commit hash, PR number, etc.). Circular evidence is forbidden. Quotes from the proposal document itself do not count. The proposal claiming something does not verify that claim.
Full four-step Veracity Handshake outcome explicitly stated. Incomplete fields, circular evidence, or single-word verification status render the Talon Mark void. No +1 is applied.

Output 2: The Mentor’s Briefing (Public Verdict Letter)

This is the primary public document addressed to the proposer and the wider community. Tone is mentor, not magistrate. It follows a strict six-element structure with generous white space for readability. No more than three sentences per paragraph.

Opening: Direct address. We state our identity and posture clearly.
The Council’s Sightline: The human hook. A plain-language framing of the proposal’s core value or core risk, expressed through a simple analogy or contextual frame. Designed to be legible to a non-technical reader within 60 seconds even on a slow connection. This element is mandatory and always appears early.
Good News: Structural strengths. We validate verified evidence, integrations, and vision with specific citations back to the Scoring Ledger.
The Gaps: Fortification opportunities. Framed as actionable improvements, never as personal failures. Specific citations provided.
Path Forward: A numbered six-step, plain-language roadmap toward an Apex Seal. Each step is concrete and achievable.
Closing and Signature: One sentence of encouragement. The Appeals Protocol is stated verbatim: proposers have 14 days to submit verified corrections or additional evidence via X. We will re-audit upon receipt. Then the Sovereign Signature block with variable CTA and “Stake with ZAM + Eagle Eye Council v0.11.5”.

Tiers of Flight (30-point hybrid scale) appear prominently before the closing thought:

APEX 🟢 (27–30 points): Peak technical and ethical excellence. Verified across all dimensions. At least one valid Talon Mark awarded.
SOARING 🟢 (21–26 points): High integrity with strong delivery signals. Minor gaps exist but do not undermine confidence.
NESTING 🟡 (16–20 points): Validated intent with incomplete evidence. Genuine capability present, but gaps must be addressed before the community can vote with full confidence.
GROUNDED 🔴 (Below 16 points or Hard-Fail triggered): Lacks the evidence to leave the earth. A Grounded verdict is not a comment on character or vision. It is a statement about what we could verify at the time of review.

A triggered Hard-Fail Gate overrides all other scoring and produces Grounded.

Output 3: The Social Signal (Public X Summary)

A single post, maximum 280 characters. It captures the core finding from the Sightline, states the Tier of Flight, names the proposal, and includes at least one relevant hashtag or token ($ADA, #ProjectCatalyst, #CardanoGov, or the proposal’s own tag). Authoritative yet warm. Only independently verified findings are cited. No unverified financial figures or performance claims from the proposal text alone.

Output 4: The Visionary Visual

A complementary AI-generated image in the official ZAM visual language is created for every audit. It visually translates the core finding of the report and is included to enhance the public Mentor’s Briefing and Social Signal.

How Scores Are Arrived At: The 30-Point Hybrid Rubric

We use a weighted hybrid system designed for transparency and rigour.

Base Score (maximum 25 points): Binary Yes/No across criteria in five dimensions. Each dimension carries a weight reflecting its priority to Cardano’s long-term health and our mission:

Accountability (weight 3) — owned by fiscal and governance scrutiny.
Resilience (weight 3) — owned by performance engineering and Field Manual compliance.
Privacy (weight 2) — owned by cryptographic integrity and formal methods.
Equity (weight 2) — owned by Global South applicability and accessibility.
Blueprints (weight 1) — owned by documentation quality and contribution barrier reduction.

Each dimension has a minimum number of criteria that must be scored (generally three, except Blueprints which requires one). A Fellow cannot collapse a weight-3 dimension into a single criterion.

Talon Mark Modifiers (maximum +5 points): One additional point per dimension where Elite-standard evidence is demonstrated and fully documented in the Talon Registry. Maximum total score is 30.

Weighted Historical Verification Record (wHVR): For proposers with prior delivery history on Catalyst or gov.tools (conditional on other domains). This forensic metric calculates delivery success on past milestones:

wHVR = (sum of Verified milestones × complexity weight) / (sum of Funded milestones × complexity weight)

Complexity weights:

W=1: Minor outreach (community posts, documentation updates, workshops, marketing).
W=2: Moderate tooling (SDKs, libraries, integration modules, dashboards).
W=3: Major infrastructure (core protocol work, smart contract systems, cryptographic implementations, on-chain governance tools).

Capping rules apply where wHVR is computed:

Below 0.85 caps at Soaring ceiling (26).
Below 0.70 caps at Nesting ceiling (20).
Below 0.50 triggers Grounded (0) and overrides all other scoring.

CIPs receive a zero-history exemption: if the author has no prior Catalyst or gov.tools funding history, wHVR is recorded as N/A — Exempt (CIP Domain) and no capping is applied. Ekklesia proposals apply wHVR only where prior history exists; otherwise N/A — No Prior History.

Domain Scoring Profiles adjust emphasis:

Project Catalyst and gov.tools: Full rubric including budget and wHVR.
CIPs (cips.cardano.org): Partial rubric. No budget dimension scored. Steward fiscal lens suspended. Architect and Visionary carry primary weight. wHVR zero-history exemption applies.
Ekklesia (app.ekklesia.vote): Partial rubric. No treasury budget. Steward scores governance mechanism integrity only. wHVR applied only where proposer history exists.

Mandatory Process Gates (non-negotiable):

Dual-signal input required: Direct ANCHOR URL to one of the four approved domains + full hydrated proposal text pasted inline between [SCROLL-BEGIN] and [SCROLL-END] delimiters. Missing either triggers immediate Hard-Fail with fixed notice. File uploads are not accepted as SCROLL.
Link Registry must be produced and output before any scoring begins.
Veracity Handshake applied to every link before use as evidence.
Recursive link traversal capped at two layers from the proposal page.
Session isolation: Each audit is discrete. Prior outputs do not carry over.
Unified voice in all public outputs: No individual Fellow is named. The Council speaks as one.

Every criterion requires an independent external Artifact Citation. The proposal text quoting its own claims is never sufficient evidence.

The Guardrails We Champion: Qualities of Strong Proposals

We reward proposals that demonstrate:

Technical sovereignty and cryptographic rigour: Formal verification roadmaps where user funds or private data are handled. Zero-Knowledge implementations that protect identity by default. User-owned keys with no central points of failure. Open-source code under permissive licences.
Performance engineering for real-world constraints: Designs that respect the Field Manual. Documented optimisation (O-notation analysis, WASM/Rust builds with benchmarks where relevant). No dependency bloat that bloats payloads or runtime requirements.
Fiscal and operational transparency: Public milestone modules with artifact citations. Clear budget breakdowns. Independently auditable financial records where treasury funds are involved. Governance mechanisms with verifiable on-chain accountability. No administrative black boxes.
Equity and Global South intentionality: Scaling models that work on low-bandwidth, low-hardware, intermittent-connectivity environments. Network effects that include rather than exclude the Edges. Alignment with Digital Public Good principles. Evidence of consideration for African and developing-world deployment contexts.
Excellent blueprints and accessibility: Architecture diagrams, developer guides, open API specifications, and documentation that materially lower the barrier for others to review, contribute, fork, or build upon the work.
Proven delivery discipline: Historical milestone completion rates that demonstrate the team can turn promises into shipped, verifiable artifacts. Complexity-weighted success, not just volume of past proposals.

These qualities are not nice-to-haves. They are the difference between proposals that extract value from the treasury and proposals that multiply value for the entire ecosystem, especially for communities that have historically been underserved by high-resource-assumption tooling.

How to Use These Reports

For community members, DReps, and voters:
Start with the Tier and the Council’s Sightline. These give you the fastest reliable signal. Then read Good News and The Gaps for specifics. Check the Artifact Citations yourself on critical claims. Use the reports to inform your voting and to hold proposers accountable to higher standards. Demand that proposals meet the Field Manual and Sunlight Clause before receiving community funds.

For proposers and builders:
Treat every report as free, high-signal feedback from a team aligned with sovereignty and equity values. Study the Path Forward steps. They are concrete actions you can take to strengthen your next submission or iteration. Address the gaps we identified. Re-audit is available within 14 days if you supply verified new evidence. Future proposals that proactively meet the Covenants and Field Manual will score higher and earn stronger community confidence.

For Mission Zambia Stake Pool and aligned partners:
These reports give us a consistent, evidence-based lens to evaluate alignment with our mission. We can identify proposals that truly serve low-resource environments, respect user sovereignty, and demonstrate delivery integrity. This protects both the treasury and the long-term health of Cardano in Africa and beyond.

A Note on Beta Status and Continuous Improvement

The ZAM Eagle Eye Council is currently in beta (v0.11.5). The constitution, scoring rubric, and output formats are being refined based on live audits and community input. We publish our full operating instrument openly so the process remains transparent and contestable.

We welcome feedback from proposers, DReps, builders, and ADA holders. Your observations on clarity, fairness, and usefulness directly shape future versions.

The Eagle Eye Council does not block vision. We fortify it with proof.

Contact us on X @missionzampool to correct technical inaccuracies, provide missing deliverables, or share feedback. We will re-audit upon verified receipt.

Stake with ZAM to support this initiative and the broader mission of equitable, sovereign Cardano infrastructure for the Edges.

Eagle Eye Council v0.11.6 — Operated by Mission Zambia Stake Pool