This public page shows which private wiki pieces exist, which are planned, and which remain blocked until identity, billing, ingestion, audit, and retention controls are implemented.
These pages are planning and readiness surfaces only. They do not create accounts, start checkout, accept private documents, or enable private workspace answers.
Public wiki-style articles, context, citations, and related links remain free.
Next: Keep expanding public authority content and citation coverage.
Public Ask answers from bounded public Knowledge Base context with citations and no submitted-payload echo.
Next: Keep public answers bounded to public context.
Pricing and plan pages explain the free-public and paid-private boundary without checkout.
Next: Use the pages to validate the product model before enabling billing.
Future account and member identity must be present before any private workspace access.
Next: Implement account and workspace identity after schema and billing decisions are approved.
Private source intake is planned only; public routes do not accept private documents.
Next: Design authenticated intake, redaction, storage, and audit before accepting private sources.
Workspace-scoped search over private indexes is planned after tenant isolation exists.
Next: Require workspace authorization, citations, and audit before private search launches.
Workspace-scoped answers over private context are planned and must never weaken public safety boundaries.
Next: Reuse the public answer layer only after workspace authorization and private citation controls exist.
Private workspace reads, writes, exports, and retention actions require audit-safe metadata.
Next: Add durable audit records before enabling private workspace mutations.
Retention windows, export requests, deletion requests, and holds are policy previews only.
Next: Implement retention jobs only after workspace authorization, audit, and operator approval.
Owner, admin, member, viewer, and service-agent roles are planned inside one workspace boundary.
Next: Add role checks before private reads, writes, exports, or deletion requests.
Enterprise policy and support controls are planned and must not imply certification.
Next: Define enterprise policy contracts without making unsupported compliance claims.
Billing integration is not connected; plan pages do not create checkout or payment sessions.
Next: Select and configure billing only in a separate approved implementation pass.
Agents can inspect the readiness, lifecycle, retention, audit, and future request schema without submitting private content or triggering a protected workflow.