Reference
Changelog
Public changes to BizHedge technical documentation and the Partner Demand contract.
Market generations: carried components
- Generation manifests can now declare a component carried forward from the prior verified manifest, with its own original observation time, instead of requiring every component to be freshly collected in the same cycle.
Partner Demand API v1.1.0
- Sync guidance now covers generation-safe full snapshots, ordered incremental reads and conflict recovery after a generation changes during a read.
- Weekly customer cohorts now include the minimum group size.
- The manual distinguishes evidence freshness, response generation time and public generation identity.
The six versioned GET operations and their response contract remain available under Partner Demand API reference.
System manual expansion
- The expanded manual covers the complete analysis lifecycle, candidate-selection and decision-class boundaries.
- New market chapters document generation identity, resumable refresh and fallback behavior.
- Demand coverage includes capture, cohort publication and safe-absence semantics.
- Receipt coverage spans creation, idempotency, expiry and revocation.
- Partner API guidance now covers sync, the data model and compatibility.
- Accessible diagrams were added. They show the system, analysis, market, Demand, receipt and partner flows.