> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequency.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Review Strategy Route

> Get the research team's take on a Lab strategy (interop Increment 4).

Runs the strategy through the research loop (RESEARCH → VALIDATE → JUDGE, no
DEVELOP — Review does not refine the strategy) and returns a real dossier +
terminal verdict. Records the pass in ``strategy_review`` and caches the
verdict on the strategy for the lineage ribbon. Review is read-only over the
strategy definition — it writes ONLY the ``last_verdict`` cache + the link
tables (``strategy_review`` + ``research_run.reviewed_strategy_id``).

#1309 degraded state: a ``cross_sectional`` strategy cannot be carried into
the loop's Phase-1 ``StrategySpec`` (``strategy_to_strategyspec`` raises before
a spec exists), so it is NOT backtestable. It still gets an honest 7-lens
advisor critique of its mechanism and records a degraded ``strategy_review``
row (``run_id``/``verdict`` null, ``backtestable=false``) — NEVER a ``rejected``
verdict from a backtest that could not run.

On the RULE (backtestable) path, a pipeline that fails before JUDGE
(``run.status == "failed"``, ``run.dossier is None``) raises **502** instead of
returning a fake ``200`` with null verdict/dossier — design-contract §7 requires
a ``backtestable=true`` response to ship a terminal verdict. No ``strategy_review``
link row is written for a failed review. Once a dossier IS produced, persisting
the link/cache rows is best-effort: a DB hiccup there is logged and swallowed so
the already-computed dossier is still returned, never discarded behind a 500.



## OpenAPI

````yaml /api/openapi.json post /api/graph/v1/strategies/{strategy_id}/review
openapi: 3.1.0
info:
  title: Sequency Graph API
  description: >

    # Sequency Graph-Native Trading API


    Graph-native API for trading intelligence, built on FalkorDB.


    ## Features


    - **Screener**: Filter stocks using graph-native queries with relationship
    expansion

    - **Stock Detail**: Complete stock context with all relationships

    - **Confluence Scoring**: Setup quality assessment with weighted components

    - **Strategy Matching**: Find matching options strategies via graph
    traversal

    - **Market Context**: Current market-wide context for trading decisions


    ## Data Sources


    All data is sourced from the FalkorDB knowledge graph, populated by:

    - Pattern detector (Go) - Technical indicators, patterns

    - Graph sync service - Levels, volume profiles, news, day classification
  version: 1.0.0
servers: []
security: []
paths:
  /api/graph/v1/strategies/{strategy_id}/review:
    post:
      tags:
        - strategies
      summary: Review Strategy Route
      description: >-
        Get the research team's take on a Lab strategy (interop Increment 4).


        Runs the strategy through the research loop (RESEARCH → VALIDATE →
        JUDGE, no

        DEVELOP — Review does not refine the strategy) and returns a real
        dossier +

        terminal verdict. Records the pass in ``strategy_review`` and caches the

        verdict on the strategy for the lineage ribbon. Review is read-only over
        the

        strategy definition — it writes ONLY the ``last_verdict`` cache + the
        link

        tables (``strategy_review`` + ``research_run.reviewed_strategy_id``).


        #1309 degraded state: a ``cross_sectional`` strategy cannot be carried
        into

        the loop's Phase-1 ``StrategySpec`` (``strategy_to_strategyspec`` raises
        before

        a spec exists), so it is NOT backtestable. It still gets an honest
        7-lens

        advisor critique of its mechanism and records a degraded
        ``strategy_review``

        row (``run_id``/``verdict`` null, ``backtestable=false``) — NEVER a
        ``rejected``

        verdict from a backtest that could not run.


        On the RULE (backtestable) path, a pipeline that fails before JUDGE

        (``run.status == "failed"``, ``run.dossier is None``) raises **502**
        instead of

        returning a fake ``200`` with null verdict/dossier — design-contract §7
        requires

        a ``backtestable=true`` response to ship a terminal verdict. No
        ``strategy_review``

        link row is written for a failed review. Once a dossier IS produced,
        persisting

        the link/cache rows is best-effort: a DB hiccup there is logged and
        swallowed so

        the already-computed dossier is still returned, never discarded behind a
        500.
      operationId: review_strategy_route_api_graph_v1_strategies__strategy_id__review_post
      parameters:
        - name: strategy_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
            title: Strategy Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````