__init__.py

"""OpenArmature: workflow framework for LLM pipelines and tool-calling agents.

AI agents: three discovery surfaces are available, pick whichever
your environment can reach:

1. **Bundled reference** at ``openarmature/AGENTS.md`` — capability
   contracts, common patterns, non-obvious shapes, and an example
   index. Path resolves via::

       python -c "import openarmature; print(openarmature.__path__[0] + '/AGENTS.md')"

   Or via the CLI: ``openarmature docs`` prints the same path.

2. **Programmatic patterns catalog** at ``openarmature.patterns`` —
   ``list()`` returns the available pattern names; ``get(name)``
   returns the canonical recipe as a markdown string. Useful in
   sandboxed environments that can ``import openarmature`` but
   can't freely read arbitrary package paths.

3. **CLI** registered as ``openarmature`` (and reachable as
   ``python -m openarmature`` where script entry points don't land
   cleanly). ``openarmature init`` writes a discovery pointer block
   into the project's ``AGENTS.md`` / ``CLAUDE.md`` so future agent
   sessions opening the project find the bundled docs automatically.
"""

__version__ = "0.13.0"
__spec_version__ = "0.55.1"
# Proposal 0052 (spec observability §5.1 / §8.4.1): canonical
# package-registry name for this implementation. Surfaces on every
# OTel invocation span as ``openarmature.implementation.name`` and on
# every Langfuse trace as ``trace.metadata.implementation_name``.
# Matches the PyPI distribution name so operators can paste it
# straight into a registry search box.
#
# No symmetric ``__implementation_version__`` constant — the spec
# requires the implementation_version value to match the package's
# release identity, which is already exposed as ``__version__`` above.
# Both observers source the version from ``__version__`` directly to
# avoid the maintenance trap of two constants that have to stay in
# lockstep across releases.
__implementation_name__ = "openarmature-python"