MAYAN_ALFA — Summary Reports Public Note
=========================================

Purpose
-------
This folder contains the centralized summary-report layer for the MAYAN_ALFA P0.7 benchmark framework.

The summary reports are intended to help reviewers, researchers and archive users understand the benchmark evidence produced across the public 10M–10B validation range. They consolidate selected benchmark and comparison outputs into a more readable publication-support layer.

Interpretation Boundary
-----------------------
MAYAN_ALFA is presented as an Independent Computational Observation Framework. The summary reports document observed benchmark behavior, deterministic comparison results, scaling characteristics and validation continuity within the tested workflow.

These reports do not constitute a universal mathematical proof, a cryptographic security claim or a hardware-independent performance guarantee. All timing and throughput interpretations are bounded by the documented hardware, compiler, operating-system, dataset and workflow conditions.

Public / Private Boundary
-------------------------
The ordinary public release boundary is 10M–10B. Public-facing packages may include sanitized summary reports, public benchmark summaries, comparison summaries and publication notes.

Protected core source logic, internal heuristics, private registry internals and raw controlled layer [CONTROLLED_SCALE_REDACTED] validation datasets must not be included in public GitHub / Zenodo / BRONZE / SILVER packages.

[CONTROLLED_ARCHIVE_REDACTED] Boundary
-------------
The [CONTROLLED_ARCHIVE_REDACTED] archive is the only package layer that may contain real protected [CONTROLLED_SCALE_REDACTED] validation archive material. BRONZE and SILVER may contain publication structure, research context and archive documentation, but they must remain free of raw [CONTROLLED_SCALE_REDACTED] numeric data and protected implementation logic.

Recommended Use
---------------
Use these summary reports as a navigation and interpretation layer. For formal review, pair them with the original CSV outputs, compare artifacts, release notes, governance files and the corresponding execution logs.
