{% extends "base.html" %}


<section class="subscription-hero private-workspace-hero">
    <div class="container">
        <div class="section-badge"><i class="fa-solid fa-building-shield"></i> Private Workspace Data Boundary</div>
        <h1>Identity can add workspace scope, not weaker safety.</h1>
        <p class="hero-subtitle">Paid private workspace access is planned around authorized private context. It does not weaken tenant isolation, redaction, protected review, destructive-action safeguards, or audit requirements.</p>
        <div class="hero-actions">
            <a href="/api/private-workspace/data-boundary" class="btn btn-primary"><i class="fa-solid fa-code"></i> Read JSON Contract</a>
            <a href="/private-workspace/" class="btn btn-secondary"><i class="fa-solid fa-id-card-clip"></i> Workspace Scaffold</a>
            <a href="/private-workspace/request-access/" class="btn btn-secondary"><i class="fa-solid fa-inbox"></i> Access Request Preview</a>
        </div>
    </div>
</section>

<section class="subscription-section">
    <div class="container two-column-layout">
        <div>
            <div class="section-heading compact-heading">
                <span class="eyebrow">Current State</span>
                <h2>Public is usable; private remains planned.</h2>
                <p>These pages are planning and readiness surfaces only. They do not create accounts, start checkout, accept private documents, or enable private workspace answers.</p>
            </div>
            <dl class="status-list wide">
                <div>
                    <dt>Public knowledge</dt>
                    <dd>free and available</dd>
                </div>
                <div>
                    <dt>Billing</dt>
                    <dd>{% if status.billingLive %}active{% else %}planned, not live{% endif %}</dd>
                </div>
                <div>
                    <dt>Private ingestion</dt>
                    <dd>{% if status.privateIngestionLive %}active{% else %}planned, not live{% endif %}</dd>
                </div>
                <div>
                    <dt>Private Ask/Search</dt>
                    <dd>{% if status.privateAskLive or status.privateSearchLive %}active{% else %}planned, not live{% endif %}</dd>
                </div>
            </dl>
        </div>
        <aside class="boundary-panel">
            <h3>Access rule</h3>
            <p>Identity can add authorized workspace scope later. Payment is not a safety bypass.</p>
            <ul class="check-list">
                <li><i class="fa-solid fa-check"></i> No cross-workspace access.</li>
                <li><i class="fa-solid fa-check"></i> No private content in public routes.</li>
                <li><i class="fa-solid fa-check"></i> No destructive action without confirmation, idempotency, and audit.</li>
            </ul>
        </aside>
    </div>
</section>

{% if page_kind == "readiness" %}
<section class="subscription-section muted-band">
    <div class="container">
        <div class="section-heading compact-heading">
            <span class="eyebrow">Readiness Matrix</span>
            <h2>What is available, planned, blocked, and operator-controlled</h2>
        </div>
        <div class="entitlement-list">
            
        </div>
    </div>
</section>
{% endif %}

{% if page_kind == "lifecycle" %}
<section class="subscription-section muted-band">
    <div class="container">
        <div class="section-heading compact-heading">
            <span class="eyebrow">Lifecycle Preview</span>
            <h2>Future private workspace flow</h2>
        </div>
        <div class="architecture-grid">
            
        </div>
    </div>
</section>
{% endif %}

{% if page_kind == "data_boundary" %}
<section class="subscription-section muted-band">
    <div class="container">
        <div class="section-heading compact-heading">
            <span class="eyebrow">Data Boundary</span>
            <h2>Paid private access cannot weaken core safety</h2>
        </div>
        <div class="architecture-grid">
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>Public knowledge stays public and free</h3>
                <p>Public KB, public Ask, public discovery, and safety guidance remain available without paid private workspace access.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>Paid value comes from authorized private workspace data</h3>
                <p>Private value is planned around workspace-scoped private sources, search, answers, audit, retention, and team controls.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>Identity expands authorized workspace scope only</h3>
                <p>Knowing who a user is may allow workspace-scoped access in the future; it does not grant global or cross-tenant access.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>Payment is not a safety bypass</h3>
                <p>Paid users still cannot bypass redaction, tenant isolation, protected review, destructive-action safeguards, or audit requirements.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>No cross-tenant access</h3>
                <p>Private reads, citations, exports, and answers must be limited to the authorized workspace.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>No credential exposure</h3>
                <p>Public and private routes must keep credentials, tokens, provider values, account secrets, and database settings out of browser-visible output.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>No raw traces or stack traces</h3>
                <p>Diagnostics and errors must use compact categories and redaction flags instead of trace details.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>No protected reviewer or admin data exposure</h3>
                <p>Protected reviewer values, private drafts, protected raw records, and admin-only output stay server-side.</p>
            </article>
            
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>No destructive mutation without confirmation, idempotency, and audit</h3>
                <p>Future private workspace mutations need explicit confirmation, idempotency, authorization, and audit-safe records.</p>
            </article>
            
        </div>
    </div>
</section>
{% endif %}

<section class="subscription-section">
    <div class="container two-column-layout">
        <div>
            <span class="eyebrow">Machine-readable planning</span>
            <h2>Public-safe APIs define the future contract.</h2>
            <p>Agents can inspect the readiness, lifecycle, retention, audit, and future request schema without submitting private content or triggering a protected workflow.</p>
        </div>
        <aside class="boundary-panel">
            <h3>Foundation APIs</h3>
            <div class="api-link-grid vertical">
                <a href="/api/private-workspace/readiness"><i class="fa-solid fa-list-check"></i> Readiness JSON</a>
                <a href="/api/private-workspace/lifecycle"><i class="fa-solid fa-route"></i> Lifecycle JSON</a>
                <a href="/api/private-workspace/data-boundary"><i class="fa-solid fa-shield-halved"></i> Data Boundary JSON</a>
                <a href="/api/private-workspace/retention-policy"><i class="fa-solid fa-clock-rotate-left"></i> Retention Policy JSON</a>
                <a href="/api/private-workspace/audit-policy"><i class="fa-solid fa-clipboard-list"></i> Audit Policy JSON</a>
                <a href="/api/private-workspace/access-request-schema"><i class="fa-solid fa-file-lines"></i> Request Schema JSON</a>
                <a href="/api/private-workspace/access-request/schema"><i class="fa-solid fa-file-code"></i> V1.3 Request Schema</a>
            </div>
        </aside>
    </div>
</section>