import type {
    CalloutContent,
    HeroContent,
    PageSeo,
    TrustPrincipleContent,
} from '@/types/site';

export const securityTrustSeo: PageSeo = {
    title: 'TenantAtlas | Security & Trust',
    description:
        'TenantAtlas frames trust through substantiated product posture, safer restore discipline, and operational clarity rather than inflated guarantees.',
    path: '/security-trust',
};

export const securityTrustHero: HeroContent = {
    eyebrow: 'Security & Trust',
    title: 'Explain the trust posture in the language of operational controls, not marketing claims.',
    description:
        'The public trust page should set realistic expectations: what the product helps teams observe, preserve, review, and restore, and where launch claims intentionally stay narrow until they can be substantiated further.',
    primaryCta: {
        href: '/legal',
        label: 'Read the legal surface',
    },
    secondaryCta: {
        href: '/contact',
        label: 'Discuss trust requirements',
        variant: 'secondary',
    },
    highlights: [
        'Preview, confirmation, and auditability remain part of the restore story.',
        'Public claims stay narrower than internal ambition.',
        'No fake compliance theater for launch.',
    ],
};

export const securityPrinciples: TrustPrincipleContent[] = [
    {
        title: 'Safer changes are a product rule, not an afterthought.',
        description:
            'Destructive or high-risk flows are framed around preview, validation, and explicit confirmation instead of one-click confidence theater.',
        note: 'Trust starts with operator discipline.',
    },
    {
        title: 'Operational evidence stays tied to the real object and version.',
        description:
            'Findings, exceptions, and reviews remain anchored to observable tenant state so the trust story is defensible when someone asks for proof.',
        note: 'Evidence should stay attributable.',
    },
    {
        title: 'Launch messaging stays within substantiated boundaries.',
        description:
            'The public site avoids promising certifications, guarantees, or full automation outcomes that are not yet appropriate to claim.',
        note: 'Restraint is part of credibility.',
    },
];

export const securityTrustNotes: CalloutContent[] = [
    {
        eyebrow: 'Substantiated public posture',
        title: 'Public posture should stay anchored to product safeguards.',
        description:
            'The launch story focuses on product shape and operator safeguards: inventory truth, immutable snapshots, safer restore flows, drift visibility, and review support.',
        tone: 'accent',
    },
    {
        eyebrow: 'Sensitive connections',
        title: 'Sensitive Microsoft connections should be explained carefully.',
        description:
            'The public site acknowledges Graph- and tenant-facing access without pretending the site itself is part of the runtime trust boundary.',
    },
    {
        eyebrow: 'What we will not say',
        title: 'No blanket assurances and no vague “fully automated governance” language.',
        description:
            'Trust pages lose credibility quickly when they substitute slogans for the actual controls and workflows a buyer will later inspect.',
        tone: 'subtle',
    },
];
