Complete the pinned Enterprise 2026r2 capability inventory

Open
#820 23 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@DeandreT is already working on this.

Since Oct 18, 2026.

Assessment

This issue has not been assessed yet.

Description

The canonical conformance/mfd-2026r2.json ledger is explicitly seeded and non-exhaustive. Full Enterprise 2026r2 parity cannot be established while capabilities, workflows and backend applicability remain unitemized.

Scope

Expand the pinned Enterprise 2026r2 capability inventory into independently assessable functions, configuration operations, connectors, formats and workflows. Establish the release/edition provenance of the reference documentation, preserve existing broad capability IDs and evidence, and keep native MFD support separate from Ferrule extensions.

Own the inventory proposal, evidence references and focused ledger controls. Coordinate through #89. Runtime features, importer/exporter changes, GUI changes and live vendor qualification remain separate implementation scopes.

Acceptance

  • Identify version-bound official documentation or explicitly retain uncertainty about a documentation source's release.
  • Itemize the documented product surfaces and map each item to import, interpretation, native export, self-roundtrip, GUI, debugging, generated Rust/C# and vendor-backend applicability.
  • Preserve existing assessments; do not infer execution support from source presence, manuals, emission or local roundtrips.
  • Link concrete implementation or qualification gaps to existing owning issues where possible.
  • Independently review coverage and ledger validity. Keep inventory_complete=false until the complete pinned inventory has been established and reviewed.
Dominant language
Rust
Stars
1
Forks
0
Avg merge
2h 50m
Merged PRs (30d)
571

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DeandreT/ferrule

All issues in DeandreT/ferrule

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.