Skip to content

Latest commit

 

History

History
142 lines (130 loc) · 9.05 KB

README.md

File metadata and controls

142 lines (130 loc) · 9.05 KB

Documentation

The main documentation is grouped by reader intent. Implementation history and provenance are kept separately so that API and format readers do not need to navigate chronological development records.

Library and format

  • Command-line tool: usage, profiles, and file/error behavior.
  • Composition matrix and admission history: the current profile matrix is authoritative; publication criteria, the deferred code-generation path, and numbered admission history follow it.
  • C API: public ABI, lifecycle, configuration, and errors.
  • Stream format: decoder-visible byte and bit representation.
  • Architecture: component boundaries, streaming contracts, limits, and composition.

Experimental design

Validation and project operation

  • Benchmarks: measurement contract and benchmark usage.
  • Fuzzing: bounded fuzz targets, corpora, and sanitizer workflow.
  • Interoperability: CI bundles and cross-platform verification.
  • Baseline readiness: current implementation and release-evidence status, with historical admission and CI evidence.
  • Release process: version namespaces, evidence gates, tagging, and publication.

Implementation records

Numbered design decisions, source provenance, implementation-reference records, and test-vector construction records are collected under implementation records. They document how marc was produced; they are not additional public API or stream-format specifications.

Project

  • Contributing: implementation sequence, provenance, composed-profile admission, and validation requirements.
  • Changelog: user-visible contents by project release.