export type VerticalId = | "public-sector" | "government" | "enterprise" | "research" | "sciences" | "professional-services" | "healthcare" | "finance" | "legal" | "saas" | "secops" | "ai" | "supply-chain"; export type Vertical = { id: VerticalId; title: string; kicker: string; headline: string; lede: string; pressure: string[]; provides: { k: string; v: string }[]; examples: string[]; }; export const VERTICALS: Vertical[] = [ { id: "public-sector", title: "Public Sector", kicker: "Public sector reality", headline: "Proof must survive procurement.", lede: "Public accountability is a third‑party problem: reviewers need proof without accounts or internal access. if.trace turns “trust us” into receipts that a stranger can verify.", pressure: [ "Assessors need chain‑of‑custody that survives vendor handoffs.", "Procurement and oversight bodies require documentation that outlives staff turnover.", "Some environments must support offline verification by design.", ], provides: [ { k: "Receipt surface", v: "Stable, no‑login URLs for trace + output + source." }, { k: "Offline bundles", v: "Triage bundles (light/standard/full) with expected hashes." }, { k: "Black/white", v: "States what is verified (integrity) and what is not (interpretation)." }, ], examples: [ "Procurement packet: prove the exact PDF a committee reviewed is what gets shared later.", "Oversight handoff: let third parties verify without creating accounts.", "Offline review: publish bundles for constrained or air‑gapped environments.", ], }, { id: "government", title: "Government", kicker: "Government review reality", headline: "Evidence must outlive people.", lede: "When decisions are reviewed months later, the only thing that matters is what you can still prove. if.trace produces stable proof surfaces that survive staffing changes, vendors, and audits.", pressure: [ "Oversight reviewers need “show me the proof” without accounts or internal tools.", "Procurement workflows introduce long delays and many stakeholders.", "Offline review is sometimes a requirement, not a preference.", ], provides: [ { k: "Receipt URLs", v: "Stable links that can be cited in procurement and audit threads." }, { k: "Triage bundles", v: "Downloadable bundles for offline verification." }, { k: "Clear scope", v: "Integrity verification without over-claiming correctness." }, ], examples: [ "Policy memo pack: prove what existed at the time of the decision, months later.", "Vendor deliverables: detect silent edits across handoffs with a single hash check.", "External challenge: publish deltas with a new receipt so changes are explicit.", ], }, { id: "enterprise", title: "Enterprise", kicker: "Enterprise pressure", headline: "Audit throughput without credential sprawl.", lede: "In enterprise environments, audit friction becomes a tax on delivery. if.trace provides proof that third parties can verify without joining your internal world.", pressure: [ "Auditors and security teams require repeatable evidence for decisions and outputs.", "Vendors and contractors create custody gaps.", "Internal access sprawl is a risk in itself.", ], provides: [ { k: "No-login proof", v: "Receipts that verify without granting access." }, { k: "Provenance linking", v: "Bind source → output so reviews stay grounded." }, { k: "Operational fit", v: "Works with existing workflows (PRs, tickets, approvals)." }, ], examples: [ "Third‑party assessment report: auditors verify bytes without Okta access.", "Vendor handoff: prevent “final_final_v7.pdf” drift with receipt-backed outputs.", "Approvals: tie sign‑off to a specific output hash (what was actually approved).", ], }, { id: "research", title: "Research", kicker: "External review reality", headline: "Reproducibility without leaking the lab.", lede: "Research reviewers need proof, not your whole environment. if.trace makes it practical to share verifiable outputs while keeping raw data controlled.", pressure: [ "External reviewers cannot be onboarded into internal tooling.", "Sensitive datasets must stay private, even when outputs are shared.", "Reproducibility requires stable evidence, not “trust me”.", ], provides: [ { k: "Receipt-first sharing", v: "Share proof links that survive copy/paste and time." }, { k: "Offline fallback", v: "HTML views and bundles for constrained environments." }, { k: "Scope clarity", v: "Proves integrity, not interpretation." }, ], examples: [ "Supplemental results pack: reviewers verify the bytes you published match the receipt.", "Keep raw data private: publish receipts without exposing confidential sources.", "Repro disputes: bind code+output packages so claims stay checkable later.", ], }, { id: "sciences", title: "Sciences", kicker: "Scientific review reality", headline: "Make claims checkable later.", lede: "Science is adversarial in the best way: other people must be able to check your work. if.trace keeps the proof surface simple and stable.", pressure: [ "Reviews happen outside your tooling and outside your time zone.", "Artifacts must remain checkable long after they were produced.", "Integrity needs to be easy to verify, or it won’t be verified.", ], provides: [ { k: "Stable proof surface", v: "Predictable links suitable for citations and review packs." }, { k: "Byte-level check", v: "A single hash answers “is this the same file?”." }, { k: "Offline kit", v: "HTML fallbacks and bundles for constrained environments." }, ], examples: [ "Preprint artifacts: prove the file reviewed is the file cited.", "Collaborator handoffs: preserve custody across teams and institutions.", "Offline kits: publish bundles when downloads are blocked or audited.", ], }, { id: "professional-services", title: "Professional Services", kicker: "Client delivery reality", headline: "Make deliverables defensible.", lede: "When advice, drafts, and deliverables become contested, you need custody that holds up. if.trace makes outputs checkable later without exposing your internal process.", pressure: [ "Client handoffs create ambiguity about what was delivered and when.", "Disputes happen later, under stress, with missing context.", "Third-party reviewers should not need your accounts.", ], provides: [ { k: "Receipt-backed delivery", v: "A stable proof link that can live in threads and tickets." }, { k: "Dispute grounding", v: "If bytes change, verification fails (black/white)." }, { k: "No-login verification", v: "Clients verify without accounts." }, ], examples: [ "Consulting deliverable: client verifies the PDF hasn’t changed since delivery.", "RFP response pack: keep drafts provable without exposing internal tooling.", "Executive deck: bind slides + appendix to receipts to prevent “message drift”.", ], }, { id: "healthcare", title: "Healthcare", kicker: "Healthcare constraints", headline: "Proof that respects boundaries.", lede: "Healthcare environments require strict boundaries: privacy, consent, and auditability. if.trace supports integrity verification without broad data exposure.", pressure: [ "Privacy boundaries must be respected even during review.", "Audit trails must be clear and durable.", "Third-party verification must not depend on internal access.", ], provides: [ { k: "Verification without access", v: "Receipts instead of credentials." }, { k: "De-risked sharing", v: "Share proof of integrity, not sensitive sources." }, { k: "Operational clarity", v: "Explicitly scoped claims for reviewers." }, ], examples: [ "Clinical-facing output: prove bytes weren’t modified after review (no patient data required).", "Evidence folder: if one character changes, verification fails — detect silent tampering.", "Third-party audit: provide proof without granting internal system access.", ], }, { id: "finance", title: "Financial Services", kicker: "Financial pressure", headline: "Chain-of-custody for high-stakes outputs.", lede: "Regulated environments need evidence that survives scrutiny. if.trace supports verifiable artifacts without fragile internal access dependencies.", pressure: [ "Model risk and decision audits require durable evidence.", "Regulators and auditors are external third parties.", "Evidence must remain checkable months later.", ], provides: [ { k: "Integrity receipts", v: "Downloadable bytes that match published hashes." }, { k: "Stable proof surface", v: "Predictable URLs for audit trails." }, { k: "Offline options", v: "Bundles for constrained environments." }, ], examples: [ "Bank statement / risk report: if one digit changes, the hash changes and verification fails.", "Model risk pack: prove the exact report approved is what was distributed.", "Regulator review: share proof links without sharing internal dashboards.", ], }, { id: "legal", title: "Legal", kicker: "Legal reality", headline: "Chain-of-custody for drafts and evidence.", lede: "Legal work depends on what can be proven. if.trace provides a simple, verifiable custody layer for documents and derived outputs.", pressure: [ "Draft histories matter when disputes arise.", "Evidence must be defensible in adversarial review.", "Third parties should verify without logins.", ], provides: [ { k: "Custody proof", v: "Bind source and output with trace IDs and hashes." }, { k: "Black/white verification", v: "Integrity verification with clear limits." }, { k: "Portable review", v: "Offline bundles and HTML views." }, ], examples: [ "Evidence folder: prove exhibits weren’t modified between handoffs.", "Contract drafts: bind the signed version to a receipt so disputes stay grounded.", "Discovery packets: third parties verify bytes without logins.", ], }, { id: "saas", title: "B2B SaaS", kicker: "Audit readiness", headline: "Prove what existed, when it existed.", lede: "Audit work is often a third-party proof problem. if.trace makes it easier to share evidence without turning your internal systems into public surface area.", pressure: [ "Auditors need repeatable proof for controls and decisions.", "Vendor and contractor work introduces custody gaps.", "Evidence must be stable across quarters.", ], provides: [ { k: "Receipt-first evidence", v: "Receipts for audits and reviews (integrity only)." }, { k: "Offline bundles", v: "Bring-your-own-verification kit." }, { k: "Scope discipline", v: "Integrity ≠ correctness, and we say so." }, ], examples: [ "Audit evidence exports: prove the PDF/CSV you handed auditors matches the receipt.", "Customer trust reports: prevent post‑hoc edits with receipt-backed outputs.", "Vendor questionnaires: keep supporting artifacts verifiable without access sprawl.", ], }, { id: "secops", title: "SecOps / SOC", kicker: "Security operations", headline: "Bind summaries to evidence.", lede: "Security teams summarize fast under pressure. if.trace keeps summaries tied to underlying evidence so post-incident review stays grounded.", pressure: [ "Incidents are reviewed later, often by external parties.", "Evidence chains can break during handoffs.", "Over-sharing internal access increases risk.", ], provides: [ { k: "Evidence binding", v: "Link reports to underlying inputs via hashes." }, { k: "Shareable receipts", v: "No-login verification for stakeholders." }, { k: "Offline verification", v: "Portable bundles for review." }, ], examples: [ "Incident postmortem: bind narrative outputs to evidence hashes for later review.", "Red-team report: prove the delivered PDF matches what was generated at the time.", "Executive updates: avoid “message drift” across channels and rewrites.", ], }, { id: "ai", title: "AI Products", kicker: "AI trust pressure", headline: "Freeze outputs before they ship.", lede: "When an output is contested (“that’s not what we saw”), you need to prove which bytes were reviewed and released. if.trace supports integrity receipts for AI outputs without requiring third-party access to your internal systems.", pressure: [ "Customers demand provenance and reproducibility.", "Vendors and models change over time.", "Claims must be checkable outside your system.", ], provides: [ { k: "Integrity receipts", v: "A stable proof surface for outputs (bytes, not truth)." }, { k: "Audit-ready bundles", v: "Offline verification options." }, { k: "Clear limits", v: "Integrity verified; meaning debated separately." }, ], examples: [ "AI outputs: prove the exact bytes you reviewed are the bytes clients received.", "Eval reports: detect silent edits before release with a single hash check.", "Model/vendor changes: keep outputs provable even as internals evolve.", ], }, { id: "supply-chain", title: "Industrial / Supply Chain", kicker: "Supply chain reality", headline: "Traceability across vendor handoffs.", lede: "In complex supply chains, custody breaks at handoff points. if.trace makes proof portable so verification survives contractor and vendor boundaries.", pressure: [ "Many stakeholders, many tools, many custody breaks.", "Evidence must outlive contracts and teams.", "Offline verification is common in the field.", ], provides: [ { k: "Portable proof", v: "Receipts and bundles that travel with the work." }, { k: "Stable verification", v: "Predictable URLs and black/white checks." }, { k: "Workflow fit", v: "Evidence can be attached to existing tickets and docs." }, ], examples: [ "QA certificates: make handoff artifacts verifiable across vendors.", "Field audits: use offline bundles when networks are constrained or monitored.", "Recall disputes: prove which document version was in circulation.", ], }, ]; export function getVerticalById(id: string): Vertical | undefined { return VERTICALS.find((v) => v.id === id); }