Skip to main content
This site is pinned to langstate/langstate@df40bc49bc8e3a51b2bb695b30ff93ef81b2cc4b, with source metadata version 0.1.0 source alpha.

​
Release status

  • Source-only alpha: the repository has no project tags and no GitHub releases at the documented baseline.
  • No supported PyPI install: the PyPI name langstate is owned by an unrelated project.
  • Source imports: working examples use core.* while the current directory is packages/langstate.
  • Packaging incomplete: the Poetry project metadata does not yet produce the intended public import surface.

​
Verified workflow

At df40bc49bc8e3a51b2bb695b30ff93ef81b2cc4b, this workflow passes 628 tests. This count describes the pinned baseline; it is not a compatibility guarantee for later commits.

​
Capability matrix

​
Contract corrections

The source defines:
  • ActionResultData for a completed orchestrator flow
  • get_current_state() for interpretive state access
  • InterpretiveStateSchema and CanonicalStateSchema as transport models
  • one latest inference per interpretive field, plus multiple candidate values
Older names such as StateResultData, get_state(), or a generic StateSchema are not part of the pinned implementation.

​
Adopter guidance

Evaluate the concrete state and schema primitives first. If you need a full agent loop, stable installed imports, a prebuilt UI projector, or a production persistence integration, plan to implement and maintain those extension points in your application until the project publishes a release-ready package. For the intended generated developer workflow and end-to-end architecture, see Library target and System design. Both are explicitly labeled design targets rather than current package behavior.