07 / Objects & flows
Objects & flows
Partnership, referral, document, and benchmark models
Public object model
| Object | Visible fields and identity | Actions and limits |
|---|---|---|
| Company partnership inquiry | First/last name, work email, company, website, software, peak/current size, operating years, phone, optional measurement consent | Request a private review. The observed page says no dataset files are uploaded through this form. |
| Referral | Referrer identity and contact, company details, software, relationship, company contact, optional context | Submit a referral. The source says the referrer is contacted before the company. Reward conditions must remain qualified. |
| Document valuation request | Archive count, estimate, files or shared link, name, email, rights agreement | Request valuation or email an estimate. Production upload, acceptance, valuation, and payout outcomes are not verified. |
| Benchmark report | Title, publication context, model names, metrics, chart/table values, methodology, task examples | Read, select a metric, inspect model results. Do not treat a display value as a live performance feed. |
| Legal / privacy article | Title, updated date where present, sections, contact route | Read and return. Local paraphrases demonstrate layout and are not legal terms for this reference. |
Entry to outcome
- Partnership. Home → Data partnerships → company form → local validation → fixture receipt. The real inquiry endpoint and review process are excluded.
- Referral. Home → Referral → referrer and company groups → context → fixture receipt. No referred contact receives a message.
- Document review. Sitemap / direct route → archive estimate → local selection or shared link → rights checkbox → fixture state. Files never leave the browser.
- Research. Home announcement or Benchmarks → selected report → metric and method → return to index. Keep report-specific units and caveats next to data.
Safe fixture data
{
"company": {
"firstName": "Alex",
"lastName": "Morgan",
"workEmail": "alex@example.test",
"company": "Example Research",
"website": "https://example.test",
"tools": [
"Slack"
],
"peakEmployees": 80,
"currentEmployees": 65,
"yearsOperating": 5,
"optionalMeasurementConsent": false
},
"submission": {
"state": "idle",
"network": "disabled",
"persistence": "page-memory-only",
"sourceAuthority": "local reconstruction"
}
}Integration boundary
The production site's backend permissions, duplicate handling, retention, evaluation jobs, analytics payloads, and payment systems are unknown. The reference implements none of them. Adding a real integration requires a separately authorized API, security, privacy, and consent review.