How CitrusGate separates public proof from private client work

1. Purpose

This page explains how CitrusGate separates public proof from private company research. A cold visitor should be able to inspect the quality of the reasoning, the recurring blocker patterns, and the delivery boundary without gaining access to company-specific diagnosis or internal research material.

The public layer is meant to make the problem legible before purchase. It is not meant to reproduce the private workspace behind one paying order.

2. What CitrusGate Publishes Publicly

The public site may include public-safe research material such as:

• Public-safe blocker pages, dispatches, and research summaries.
• Recurrence counts with denominators and dated publication windows.
• Public-source specimen briefs that show how the diagnosis works without leaking a live company.

Public pages are written so a reader can understand the blocker and the reasoning pattern without learning the identity, internal notes, or exact action sequence for one specific company.

3. What CitrusGate Keeps Private

Private material stays out of the public site. That includes:

• Raw company notes, source bundles, and internal operator artifacts.
• Company-specific diagnosis, contact context, outreach state, and sendability logic.
• The private next move or ordered fix sequence for one live team.

If a document or insight depends on knowing the exact company, contact, outreach state, or hidden intervention order, it belongs in the private brief or internal systems, not on the public site.

4. Why the Boundary Exists

CitrusGate needs a public trust layer so a new buyer can evaluate the quality of the diagnosis before purchase. That only works if the public layer stays strong enough to prove judgment and narrow enough to avoid leaking private company research.

The practical boundary exists for three reasons:

• The public site proves recurrence; it does not mirror the private research workspace.
• Paid delivery happens through a protected buyer flow, not through public pages or public file links.
• If an insight becomes less useful after abstraction, it belongs in the private brief instead of on the site.

5. Delivery Boundary

Paid delivery happens through a protected buyer flow. The final brief is released privately to the buyer and is not surfaced through the public corpus.

Public pages can show how the brief thinks. They do not expose the company-specific diagnosis, supporting raw notes, or the private next move reserved for the buyer.

6. Practical Rule

If a page would stop being useful after removing company identity, private outreach state, or the ordered private fix sequence, that material should not be on the public site.

If an insight becomes less useful after abstraction, it belongs in the private brief instead of on the site.

7. Questions and Next Steps

If you want to inspect the public proof layer first, read the specimen briefs. If you want the scope of the private service, read the brief page.

If you need to ask where a piece of information belongs before sharing it, email [email protected]. The same path applies if your company needs an NDA, a model-processing restriction, or a stricter provider-retention boundary before context is shared for the brief.