src.dackar.RCA.signal_evidence.contracts
========================================

.. py:module:: src.dackar.RCA.signal_evidence.contracts


Attributes
----------

.. autoapisummary::

   src.dackar.RCA.signal_evidence.contracts.JsonDict


Classes
-------

.. autoapisummary::

   src.dackar.RCA.signal_evidence.contracts.SignalEvidenceBuilderContract
   src.dackar.RCA.signal_evidence.contracts.StageCScorerContract
   src.dackar.RCA.signal_evidence.contracts.StageFRefineContract


Module Contents
---------------

.. py:data:: JsonDict

.. py:class:: SignalEvidenceBuilderContract

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:method:: build(*, run_id, event, telemetry_summary, kg_context)


.. py:class:: StageCScorerContract

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:method:: score(event, telemetry_summary, kg_context, operational_context, run_context, signal_evidence = None)


.. py:class:: StageFRefineContract

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:method:: refine_with_evidence(causality_candidates, evidence_bundle, kg_context = None, signal_evidence = None, entity_normalizer_cfg = None)