{% extends "base.html" %}


<section class="subscription-hero private-wiki-hero">
    <div class="container">
        <div class="section-badge"><i class="fa-solid fa-building-lock"></i> Private Wiki Architecture V1.0</div>
        <h1>A planned private wiki layer for teams that need NeuralWikis without public disclosure.</h1>
        <p class="hero-subtitle">
            Private wiki support is being designed around account, workspace, member, source, audit, and retention boundaries. The public NeuralWikis knowledge base remains free and separate.
        </p>
        <div class="hero-actions">
            <a href="/pricing/" class="btn btn-primary"><i class="fa-solid fa-table-list"></i> View Planned Tiers</a>
            <a href="/api/subscription/status" class="btn btn-secondary"><i class="fa-solid fa-signal"></i> Read Status JSON</a>
        </div>
    </div>
</section>

<section class="subscription-section">
    <div class="container two-column-layout">
        <div>
            <div class="section-heading compact-heading">
                <span class="eyebrow">Isolation Model</span>
                <h2>Private content must be workspace-scoped before it is useful.</h2>
                <p>No private ingestion, private Ask, private search, or private export should go live until these boundaries exist.</p>
            </div>
            <div class="isolation-steps">
                
                <article>
                    <h3>Account</h3>
                    <p>Billing and ownership container planned for private wiki customers.</p>
                </article>
                
                <article>
                    <h3>Workspace</h3>
                    <p>Isolated private wiki boundary for source documents, indexes, citations, and answers.</p>
                </article>
                
                <article>
                    <h3>Member</h3>
                    <p>Role-scoped person or agent identity inside one workspace.</p>
                </article>
                
                <article>
                    <h3>Private Source</h3>
                    <p>Customer-provided material that remains non-public unless explicitly promoted through a separate reviewed public-source process.</p>
                </article>
                
            </div>
        </div>
        <aside class="boundary-panel">
            <h3>Current status</h3>
            <dl class="status-list">
                <div>
                    <dt>Private workspace</dt>
                    <dd>planned, not live</dd>
                </div>
                <div>
                    <dt>Billing</dt>
                    <dd>planned, not live</dd>
                </div>
                <div>
                    <dt>Private data accepted</dt>
                    <dd>no</dd>
                </div>
                <div>
                    <dt>Public knowledge</dt>
                    <dd>free</dd>
                </div>
            </dl>
        </aside>
    </div>
</section>

<section class="subscription-section muted-band">
    <div class="container">
        <div class="section-heading compact-heading">
            <span class="eyebrow">Implementation Direction</span>
            <h2>What V1.0 makes explicit</h2>
        </div>
        <div class="architecture-grid">
            <article>
                <i class="fa-solid fa-layer-group"></i>
                <h3>Public and private stay separate</h3>
                <p>Public routes expose public knowledge, public Ask, and planned subscription metadata only.</p>
            </article>
            <article>
                <i class="fa-solid fa-shield-halved"></i>
                <h3>Payment is not a safety bypass</h3>
                <p>Paid identity can support higher trust and private storage, but it does not remove provenance, review, or retention constraints.</p>
            </article>
            <article>
                <i class="fa-solid fa-database"></i>
                <h3>Durable tables are planned</h3>
                <p>Any persistence must use additive nw_* owned tables, with no destructive changes and no writes to unrelated databases.</p>
            </article>
            <article>
                <i class="fa-solid fa-file-shield"></i>
                <h3>Private source bodies stay private</h3>
                <p>Private documents must never appear in public APIs, discovery files, diagnostics, logs, or screenshots.</p>
            </article>
        </div>
    </div>
</section>

<section class="subscription-section">
    <div class="container">
        <div class="section-heading compact-heading">
            <span class="eyebrow">Planned Tiers</span>
            <h2>Private wiki tiers this architecture must support</h2>
            <p>Private Starter, Private Team, Business, and Enterprise are planned paid tiers. They are not live checkout offers.</p>
        </div>
        <div class="api-link-grid">
            <a href="/pricing/"><i class="fa-solid fa-table-list"></i> Pricing plan boundary</a>
            <a href="/api/subscription/plans"><i class="fa-solid fa-list"></i> Plans JSON</a>
            <a href="/api/subscription/status"><i class="fa-solid fa-signal"></i> Status JSON</a>
            <a href="/knowledge-base/"><i class="fa-solid fa-book-open-reader"></i> Free public KB</a>
        </div>
    </div>
</section>

<section class="subscription-section">
    <div class="container two-column-layout">
        <div>
            <span class="eyebrow">Schema Planning</span>
            <h2>Durable schema posture</h2>
            <p>The architecture is ready for additive schema design, but this pass performs no database writes.</p>
            <dl class="status-list wide">
                <div>
                    <dt>Table prefix</dt>
                    <dd>nw_* only</dd>
                </div>
                <div>
                    <dt>Writes enabled</dt>
                    <dd>false</dd>
                </div>
                <div>
                    <dt>Destructive changes</dt>
                    <dd>false</dd>
                </div>
            </dl>
        </div>
        <aside class="boundary-panel">
            <h3>Boundary summary</h3>
            <ul class="check-list">
                
                <li><i class="fa-solid fa-check"></i> Public knowledge stays free.</li>
                
                <li><i class="fa-solid fa-check"></i> Private wiki features are planned and are not live billing or live private workspace access.</li>
                
                <li><i class="fa-solid fa-check"></i> Payment is not a safety bypass; paid users still follow workspace scope, provenance, retention, and review boundaries.</li>
                
                <li><i class="fa-solid fa-check"></i> Public NeuralWikis routes must not expose private workspace records, customer records, private source bodies, tokens, stack traces, or database settings.</li>
                
                <li><i class="fa-solid fa-check"></i> Private content must be account/workspace/member scoped before any ingestion, search, answer, export, or retention behavior goes live.</li>
                
            </ul>
        </aside>
    </div>
</section>