Files
zeekay 189ce08e51 Regenerate against the document the deployment answers for
The projection these were generated from was a month old and predated the
compute migration, so every one of them described /v1/visor — which the API
serves at zero paths now. That is why a hand-written console client and a
generated one had drifted the same way at the same time.

No /v1/visor path survives here. The word still appears as a source-plane
value and inside gvisor and supervisor, which are not this rename.
2026-09-05 18:07:13 -07:00

97 lines
3.0 KiB
C++

/**
* Hanzo Cloud API
* The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
*
* The version of the OpenAPI document: v1
*
* NOTE: This class is auto generated by OpenAPI-Generator 7.14.0.
* https://openapi-generator.tech
* Do not edit the class manually.
*/
/*
* Provenance.h
*
*
*/
#ifndef HANZO_MODEL_Provenance_H_
#define HANZO_MODEL_Provenance_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Provenance
: public ModelBase
{
public:
Provenance();
virtual ~Provenance();
/////////////////////////////////////////////
/// ModelBase overrides
void validate() override;
web::json::value toJson() const override;
bool fromJson(const web::json::value& json) override;
void toMultipart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) const override;
bool fromMultiPart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) override;
/////////////////////////////////////////////
/// Provenance members
/// <summary>
/// Backend is the leg that contributed this match: \&quot;index\&quot; (lexical), \&quot;vector\&quot; (semantic), \&quot;code\&quot; (the org&#39;s repositories) or \&quot;rerank\&quot; (the cross-encoder pass, whose Score is the relevance it assigned). It is the same name that leg reports itself under in Fusion.Backends, so a hit can be traced to a status.
/// </summary>
utility::string_t getBackend() const;
bool backendIsSet() const;
void unsetBackend();
void setBackend(const utility::string_t& value);
/// <summary>
/// Rank is this document&#39;s 1-based position in THAT leg&#39;s own result list, before fusion — 1 is the leg&#39;s best hit. It is the only input to the fused score: RRF adds 1/(60+rank) per leg, which is why a document two legs ranked second beats one a single leg ranked first.
/// </summary>
int64_t getRank() const;
bool rankIsSet() const;
void unsetRank();
void setRank(int64_t value);
/// <summary>
/// Score is the leg&#39;s NATIVE score, on that leg&#39;s own scale, reported for explanation and never used in ranking — the scales are incomparable (a cosine similarity against a term-match count), which is why fusion works on ranks. The vector leg reports Qdrant&#39;s cosine similarity; the lexical leg exposes no per-row score and reports 0, meaning \&quot;unscored\&quot;, not \&quot;scored zero\&quot;.
/// </summary>
double getScore() const;
bool scoreIsSet() const;
void unsetScore();
void setScore(double value);
protected:
utility::string_t m_Backend;
bool m_BackendIsSet;
int64_t m_Rank;
bool m_RankIsSet;
double m_Score;
bool m_ScoreIsSet;
};
}
}
#endif /* HANZO_MODEL_Provenance_H_ */