Public data boundary
What BizHedge allows into owner, receipt and partner responses.
Owner brief
Explicit schemas assemble the owner brief. It can contain the reflected business context, confirmed exposure, candidate comparison, selected contract and side, deterministic economics, rejected alternatives and material relationship limitation. Suggested risks remain labeled and unsized until confirmation.
The public reasoning trace is a concise action summary and graph path. It is not raw chain-of-thought.
Shared receipt
The receipt boundary is narrower. It accepts fixed market identity, timestamps, selected side, price and whole-dollar ledger fields, excluding arbitrary business descriptions and model-authored prose. Stored rows are revalidated on read, and revocation removes public access without changing the original private analysis.
Partner Demand
Partner records contain bounded taxonomy dimensions, released counts, curated text for proposed contract shapes, public lifecycle state and generation metadata. They exclude the original analysis, exact customer timing and any field that reconnects a group to one owner.
Blocked classes
- raw owner input and private notes;
- names, exact addresses and stable client identifiers;
- prompts, model payloads and hidden reasoning;
- credentials, authorization material and network identifiers;
- internal scores, raw upstream errors and storage locations;
- idempotency material and private event timestamps; and
- unsupported claims about execution, fills, capacity or trade placement.
Boundary checks apply to source objects and exported public artifacts. A field that is useful internally does not become public merely because it is available.