Files
zeekay 645325a641 regenerate from cloud 939b09d4
The projection was 113 commits behind the document it claims to describe, and
`generate.py --all --check` reported every one of the thirteen clients DRIFTED —
the same +19 models in each, because they all fell behind the same emission.

Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4
(sha256 087024f6…), which is the only description of this API that cannot name a
route the binary does not serve. `--check` is clean across all thirteen after.

.spec-lock moved with the code. The generator READS that file and never writes
it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous
document. A lock that disagrees with the tree beside it is worse than no lock:
the next `--check` without `--spec` fetches what production serves, compares it
to a digest that was already wrong, and reports drift that is really staleness.
2026-08-24 23:32:53 -07:00

152 lines
5.1 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.
*/
/*
* RiskLabelFact.h
*
*
*/
#ifndef HANZO_MODEL_RiskLabelFact_H_
#define HANZO_MODEL_RiskLabelFact_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class RiskLabelFact
: public ModelBase
{
public:
RiskLabelFact();
virtual ~RiskLabelFact();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// RiskLabelFact members
/// <summary>
/// At is when the judged event happened, RFC 3339.
/// </summary>
utility::string_t getAt() const;
bool atIsSet() const;
void unsetAt();
void setAt(const utility::string_t& value);
/// <summary>
/// Confidence in [0,1]. A processor chargeback is 1; an analyst&#39;s hunch is not. It breaks a tie WITHIN a precedence rank and can never lift a weak source above a strong one — otherwise every caller would send 1. A litigation hold is NOT a field here. It is a fact about the record and not about the world, so it is not part of what was asserted, it is not in the content digest, and it has its own op — which is also the only way one can be released. Carried here it was silently a no-op on any record that already existed: the digest was the same, the insert was ignored, and the caller was told &#x60;duplicate&#x60; while the hold it asked for was never placed.
/// </summary>
double getConfidence() const;
bool confidenceIsSet() const;
void unsetConfidence();
void setConfidence(double value);
/// <summary>
/// Disposition is productive, unproductive, or empty for an explicit unjudged — the AML engine&#39;s own vocabulary, verbatim.
/// </summary>
utility::string_t getDisposition() const;
bool dispositionIsSet() const;
void unsetDisposition();
void setDisposition(const utility::string_t& value);
/// <summary>
/// Evidence points at the record this conclusion came from: a dispute id, a case id, a decision id. Required, because a label with no evidence cannot be defended when the adverse action it fed is challenged.
/// </summary>
utility::string_t getEvidence() const;
bool evidenceIsSet() const;
void unsetEvidence();
void setEvidence(const utility::string_t& value);
/// <summary>
/// Kind is what the subject is: account, agent, merchant, payout, person, session or transaction. Closed, because a typo in an open field would shard a tenant&#39;s labels into a partition nothing reads and nothing would say so.
/// </summary>
utility::string_t getKind() const;
bool kindIsSet() const;
void unsetKind();
void setKind(const utility::string_t& value);
/// <summary>
/// Seen is when this assertion became KNOWABLE, RFC 3339. It is required and it is not At: a chargeback lands 30 to 120 days after the transaction it judges, and a training set joined on At alone knows the future. Everything this plane does to prevent leakage is computed from Seen.
/// </summary>
utility::string_t getSeen() const;
bool seenIsSet() const;
void unsetSeen();
void setSeen(const utility::string_t& value);
/// <summary>
/// Source is who asserted: chargeoff, dispute, case, refund, review or sample. It is the primary term of the precedence rule, so it is closed — an unknown source has no rank and a conflict with it could not be resolved.
/// </summary>
utility::string_t getSource() const;
bool sourceIsSet() const;
void unsetSource();
void setSource(const utility::string_t& value);
/// <summary>
/// Subject identifies the thing being judged, in the tenant&#39;s own namespace.
/// </summary>
utility::string_t getSubject() const;
bool subjectIsSet() const;
void unsetSubject();
void setSubject(const utility::string_t& value);
protected:
utility::string_t m_At;
bool m_AtIsSet;
double m_Confidence;
bool m_ConfidenceIsSet;
utility::string_t m_Disposition;
bool m_DispositionIsSet;
utility::string_t m_Evidence;
bool m_EvidenceIsSet;
utility::string_t m_Kind;
bool m_KindIsSet;
utility::string_t m_Seen;
bool m_SeenIsSet;
utility::string_t m_Source;
bool m_SourceIsSet;
utility::string_t m_Subject;
bool m_SubjectIsSet;
};
}
}
#endif /* HANZO_MODEL_RiskLabelFact_H_ */