Current support and evidence

Provision the Flyology Alire index

alr index --reset-community
alr index --add=git+https://github.com/flyology-ada/alire-index.git \
  --name=flyology --before=community
alr index --list
cd /path/to/your/application
alr with flyology_json=0.1.0-dev
alr build

The repository manifest declares GCC-based GNAT 13 through 16 as its intended compiler range. The executed matrix below is the compatibility evidence.

Use the implemented trusted surface

The parser and writer accept arbitrary-bound Stream_Element_Array values. Physical capacities and profiles are always application choices; the library provides no default capacity or profile.

Separate the build matrix from benchmark tooling

The benchmark jobs have portable and native tracks. The benchmark jobs build maintained adapters for independent implementations. Their different parser and writer contracts make the results optimization evidence, not a claim of semantic equivalence.

Exercise lifecycle and bounded failure

The maintained test action builds and runs:

• parser, UTF-8, number grammar, duplicate-index, and Unicode escape tests;
• public foundation and parser tests;
• private and public writer tests; and
• an external public-unit consumer compilation.

Focused cases cover:

• arbitrary Ada bounds, empty input, and chunk or fragment schedules;
• exact depth and storage limits, reset, and abort;
• destination exhaustion, commit or abort failure, and task interruption; and
• exact offsets and transactional nonpublication.

Public-surface assembly gates require parser accessors and the batched path to inline without an indirect hot call. A separate gate requires the writer string-fragment path to inline. It rejects finalization, tasking, and allocation runtime calls in that probe. The release workflow repeats the public-unit test action from the source archive and from a fresh indexed solve.

Treat corpora as evidence, not authority

The parser lane pins 314 selected JSONTestSuite fixtures and 80 selected JSON Schema Test Suite JSON files. The repository verifies exact fixture sets, licenses, byte digests, and aggregate manifests before execution.

All 394 fixtures run as one chunk, as one-byte chunks, and with deterministic randomized schedules. Malformed inputs must retain the monolithic error code and byte offset. Bounded transition fixtures additionally run every split. The full-corpus quadratic planner refuses to start without an explicit work ceiling; the release review records its computed 82,539,090,222-unit requirement instead of launching a very large loop.

The writer lane uses four project-owned event tapes and exact hexadecimal golden output. Each token runs whole, one octet at a time, at every single split, and through four deterministic randomized schedules. The public parser reparses the output under varied chunks. Node's built-in JSON parser provides an additional independent acceptance check.

Corpus labels and oracle agreement never replace the selected JSON profile or the JSON specification.

Keep future work out of current claims

• Version 0.1.0-dev is a development release; later versions may revise the experimental API.
• The trusted package has no accounting or budget surface for untrusted consumer integration.
• Binary64, decimal, and application-specific number conversions are not current public units.
• Canonical JSON, a DOM, allocating conveniences, and Type IR, Wire, or OCI adapters are not current library features.
• Ordinary_Compact is deterministic for the same calls, but it is not canonical JSON.