import Link from "next/link";

export default function MarketOperationsPage() {
  return (
    <div className="space-y-10 font-mono text-[#c8ffd8]">
      <header>
        <p className="text-[10px] uppercase tracking-[0.45em] text-[#00ff41]/45">Layer 2 · fulfillment stack</p>
        <h1 className="mt-2 text-2xl font-black tracking-tight text-[#7af598] md:text-3xl">Operations &amp; pipeline</h1>
        <p className="mt-3 max-w-3xl text-sm leading-relaxed text-[#5a8f6a]">
          The market is not a static directory. Every SKU routes through a staged pipeline: intake, bond, listing QA, buyer messaging, ship window, and dispute arbitration. Below is how CyberLux models that stack in software — so mirrors and onions stay coherent even when traffic splits across forty-three hidden services.
        </p>
      </header>

      <section className="rounded border border-[#00ff41]/25 bg-[#050a08]/90 p-6 md:p-8">
        <h2 className="border-b border-[#00ff41]/15 pb-2 text-sm font-black uppercase tracking-widest text-[#9dffc4]">
          Order state machine
        </h2>
        <ol className="mt-6 space-y-4 text-sm leading-relaxed text-[#7ab896]">
          <li>
            <strong className="text-[#b4ffcc]">Draft</strong> — cart lines held client-side; no vendor notification until checkout commits a signed bundle.
          </li>
          <li>
            <strong className="text-[#b4ffcc]">Committed</strong> — checkout posts intent; escrow layer (see{" "}
            <Link href="/market/trust" className="text-[#7af598] underline hover:text-white">
              Trust
            </Link>
            ) opens a cooling window for key verification.
          </li>
          <li>
            <strong className="text-[#b4ffcc]">Vendor ack</strong> — stall owner confirms stock and ship SLA; late ack downgrades stall priority in search ranking.
          </li>
          <li>
            <strong className="text-[#b4ffcc]">In transit</strong> — tracking tokens are opaque hashes; plaintext carriers never touch the hub.
          </li>
          <li>
            <strong className="text-[#b4ffcc]">Settled / disputed</strong> — auto-release after timeout unless a ticket opens a moderator queue tied to the same order id across all onions.
          </li>
        </ol>
      </section>

      <section className="grid gap-6 md:grid-cols-2">
        <div className="rounded border border-[#00ff41]/20 p-6">
          <h3 className="text-xs font-black uppercase tracking-widest text-[#00ff41]/70">SLA tiers (in-world)</h3>
          <ul className="mt-4 space-y-3 text-xs leading-relaxed text-[#6a9b7a]">
            <li>
              <span className="font-bold text-[#9dffc4]">Standard:</span> vendor ack within 48h simulated clock; ship within 120h.
            </li>
            <li>
              <span className="font-bold text-[#9dffc4]">Express bond:</span> higher vendor bond unlocks 12h ack and pinned placement in category rails.
            </li>
            <li>
              <span className="font-bold text-[#9dffc4]">Cold chain / sensitive:</span> extra QA step before listing goes live; edits re-trigger QA.
            </li>
          </ul>
        </div>
        <div className="rounded border border-[#00ff41]/20 p-6">
          <h3 className="text-xs font-black uppercase tracking-widest text-[#00ff41]/70">Dispute ladder</h3>
          <ol className="mt-4 list-decimal space-y-2 pl-4 text-xs leading-relaxed text-[#6a9b7a]">
            <li>Buyer ↔ vendor thread (PGP-signed).</li>
            <li>Floor mediator — binds to listing category expertise.</li>
            <li>Market council — multi-sig release or partial refund.</li>
            <li>Permanent ban + bond forfeit for pattern fraud.</li>
          </ol>
        </div>
      </section>

      <section className="rounded border border-dashed border-[#00ff41]/30 p-6 text-xs leading-relaxed text-[#4a6b55]">
        <strong className="text-[#6a9b7a]">Why this page exists:</strong> dedicated Tor onions for <code className="text-[#7af598]">/market</code> should feel like a full vertical, not a shallow iframe. The pipeline text mirrors how cart, checkout, and support routes are wired in the Next app so operators can explain the same story on any mirror.
      </section>

      <section className="rounded border border-[#00ff41]/20 bg-[#030806]/80 p-6 md:p-8">
        <h2 className="text-xs font-black uppercase tracking-widest text-[#00ff41]/65">Glossary · ops vocabulary</h2>
        <dl className="mt-4 grid gap-4 text-xs text-[#6a9b7a] md:grid-cols-2">
          <div>
            <dt className="font-bold text-[#9dffc4]">Signed bundle</dt>
            <dd className="mt-1 leading-relaxed">
              Mirror list + hub fingerprint + timestamp; clients verify before trusting checkout addresses or vendor rotations across rendezvous points.
            </dd>
          </div>
          <div>
            <dt className="font-bold text-[#9dffc4]">Opaque hash</dt>
            <dd className="mt-1 leading-relaxed">
              Tracking token that maps to carrier events only inside vendor tooling — plaintext courier names never cross the Next boundary.
            </dd>
          </div>
          <div>
            <dt className="font-bold text-[#9dffc4]">Cooling window</dt>
            <dd className="mt-1 leading-relaxed">
              Post-commit interval where buyers validate PGP continuity and multisig cosigners can abort without burning reputation.
            </dd>
          </div>
          <div>
            <dt className="font-bold text-[#9dffc4]">Category rail</dt>
            <dd className="mt-1 leading-relaxed">
              Faceted slice of the catalog used for pinned placement; express-bond stalls can lease rail time without polluting unrelated SKUs.
            </dd>
          </div>
        </dl>
      </section>
    </div>
  );
}