# Quarterly development programme

Target: strengthen MoonOCI with a reproducible executable consumer and broadly
reusable cloud-native capabilities. Eligibility and which dates of contribution
count remain subject to the quarterly organizer's rules. Submission volume is
not an official scoring criterion verified by this project.

The starting branch contains 12 commits. At the root filesystem indexing
milestone, the branch reached 101 commits with 89 new commits. The development
history preserves actual dates and authors.

Development streams, each requiring real interfaces, adversarial cases,
integration examples, measured resource costs and maintenance documentation:

| Stream | Current increment | Further work requiring implementation |
| --- | --- | --- |
| Executable consumption | Native self-hosted verifier packaging and Linux runner | Execute CI, negative runtime cases, reproducibility across clean runners |
| Registry interoperability | Windows HTTP/TLS fixture, ORAS copy, bounded referrer bundles and exact Statement admission. Public Alpine consumed via ORAS and independently compared across 517 entries | Native public network interoperability and Linux runtime CI evidence |
| Multi-platform distribution | Merge/select/slice plus bounded nested-index walking, image projection, trusted root pins and derivation receipts | Additional feature/variant contracts, reference selection and independent Skopeo selection |
| Offline delivery | Delta archives, trusted pins, bounded hydration, restartable chunk sessions/recovery, bounded scheduling and independent Windows consumer | External transport adapters, peak-memory/workload curves and Linux runtime evidence |
| Content lifecycle | Indexed lookup, mixed physical catalogs, subject/referrer retention, extension-preserving copies, stale-review rejection, bounded Native load/export and Windows CPython/ORAS consumer | Host retention scheduling, deletion transactions, external workloads and remote CI evidence |
| Release governance | Versioned policies, all-platform runtime metadata rules and a pre-publication Registry gate for required types and pinned Statement binding | External signer trust and predicate-specific rules |
| Change analysis | Final-file content/ownership provenance, structured file/config comparisons, pinned upgrade review and independent consumer | Larger workload evidence, host approval integration and additional platform cases |
| Supply-chain attachments | OCI 1.1 artifacts, image/index subject binding, referrer pages/discovery, content checks, required-type gates and Windows ORAS consumer | Semantic document/signature adapters, retention and broader external fixtures |
| Performance and robustness | Root filesystem path-segment index, independently checked 1,000 and 4,000 entry workloads, quotas and four-backend tests | Peak-memory curves and additional external workloads |

Record each completed coherent implementation or validated fix as it happens.
Review commit quality and actual count at milestone boundaries. The 100+ target
is complete only when the work exists and all relevant checks pass; a roadmap
or generated list of commits is not delivery.
