implementations.yaml

# Observed 2026-07-31 from the filesystem, not inferred from architecture docs.
# See docs/deployment-inventory.md for how each fact was established.
contract_version: "0.1"

# Three axes, kept apart. Conflating them lets a gap analysis imply code
# adoption: "PARTIAL" reads as "some of it is wired up" when what exists is a
# document saying it is not.
#
#   contract_status         does the contract exist for this component
#   implementation_adoption is any code producing contract objects
#   predecessor_mapping     has the existing code been mapped against it
maturity_states:
  - NOT_LOCATED          # no code found anywhere
  - PLANNED              # named as in scope, nothing written
  - SPECIFIED            # contract written, no adapter
  - ADAPTER_STARTED      # an adapter exists and produces contract objects
  - ROUND_TRIP_PROVEN    # a complete round trip through the adapter boundary
  - PARTIAL_ADOPTION     # application code consumes at least one contract
  - CONFORMANT           # all claimed contracts pass golden fixtures
  - DEPLOYED_CONFORMANT  # and the deployed commit is observable and matches

# ADAPTER_STARTED to ROUND_TRIP_PROVEN is the honest boundary: reproducing a
# golden hash proves translation, not adoption. PARTIAL_ADOPTION begins only
# when application code itself consumes a canonical contract.

implementations:

  quantify:
    implementation_adoption: ADAPTER_ONLY
    predecessor_mapping: documented
    repository: redevops-io/RAAAL
    commit: dd2b860
    status: ADAPTER_STARTED
    adapter: adapters/quantify
    role: canonical-consumer
    note: >-
      Imports neither runtime today. Contributes fixtures and discipline; it is
      the incubator, not the owner. The adapter translates at the boundary and
      Quantify has adopted nothing internally — `ADAPTER_ONLY` says exactly that,
      where `PARTIAL` would imply application code produces contract objects.

  context-runtime:
    implementation_adoption: NOT_STARTED
    predecessor_mapping: documented
    repository: redevops-io/context-runtime
    commit: 8fe5f3a
    describe: v7.0-2-g8fe5f3a
    status: SPECIFIED
    adapter: adapters/context_runtime
    deployed: unknown
    note: >-
      At v7.0. None of the v0.1 contract types exist in it; the nearest
      predecessor is context_runtime.registry.Capability. See its mapping.

  redevops-rag:
    implementation_adoption: NOT_STARTED
    predecessor_mapping: documented
    repository: redevops-io/redevops-rag
    commit: e3e37df
    describe: v0.2.0-31-ge3e37df
    status: SPECIFIED
    adapter: adapters/redevops_rag
    deployed: unknown
    warning: >-
      Checked out twice at different commits — submodule e3e37df, standalone
      ceec853. One of them is not what runs.

  rag-saas-platform:
    implementation_adoption: PARTIAL_ADOPTION
    predecessor_mapping: documented
    repository: redevops-io/rag-saas-platform
    commit: 7d562c2
    branch: feat/context-runtime-migration
    status: PARTIAL_ADOPTION
    adopted_contracts:
      - MissionProgram
      - InvestigationTransitionEvent
      - VerificationResult
      - submission idempotency
      - replay
      - finding routing
    not_adopted:
      - ArtifactHandle
      - ContextPreviewPlan
      - ContextView
      - CapabilityDescriptor
    adapter: adapters/rag_saas_platform
    role: deployed control plane
    note: >-
      The only component actually deployed, and now the first real consumer:
      the Investigation lifecycle is persisted and replayed through the
      canonical contracts. One lifecycle does not prove the package, so the
      gate stays below CONFORMANT. Context Runtime and ReDevOps RAG do not move
      because this application imports them — adoption is per implementation.

  mission-runtime:
    status: NOT_LOCATED
    evidence: zero occurrences in code, docs or config

  discovery-runtime:
    status: NOT_LOCATED
    evidence: zero occurrences in code, docs or config

  sidekick:
    status: NOT_LOCATED
    evidence: >-
      Not a repository. An integration module at
      context_runtime/integrations/sidekick.py.

  agentic-os:
    status: NOT_LOCATED
    evidence: >-
      No directory on this machine and no import reference from any located
      repository. Possibly the private umbrella repo holding the v8/v10 work.