const { useState } = React; // English canonical articles (17 questions, 3 categories) const CANON_ARTICLES_EN = { security: [ { category: 'PRODUCT OVERVIEW', icon: '\uD83C\uDFD7', title: 'What is Launch Ark?', body: 'Launch Ark is a structured continuity package for solo-built and AI-built software projects. It maps what exists, what is missing, what is uncertain, and what another person would need to know to understand how the project survives a bad week. It is not consulting, not certification, and not DevOps implementation.', meta: { updated: 'Canonical definition', visibility: 'Public Knowledge' } }, { category: 'PRIVACY POLICY', icon: '\uD83D\uDD12', title: 'What is the No-Secrets Policy?', body: 'The intake form is explicitly designed to exclude credential fields. No secrets, API keys, tokens, passwords, private repository URLs, or connection strings are requested or collected at any stage. Our validator scans for secret-like patterns and blocks any intake that contains them before it reaches any operator.', meta: { updated: 'Active policy', visibility: 'Public Knowledge' } }, { category: 'DATA GOVERNANCE', icon: '\uD83D\uDCBE', title: 'How is my data handled?', body: 'We collect only the minimum information required to assemble your package. Raw intake data is deleted after delivery. We retain only minimal metadata needed for order tracking (reference ID, delivery status, date). No marketing use. No third-party sharing.', quote: '"Data not stored cannot be stolen." \u2014 Core operating principle', meta: { updated: 'Current policy', visibility: 'Public Knowledge' } }, { category: 'USER RIGHTS', icon: '\uD83D\uDCC4', title: 'What are Deletion Receipts?', body: 'When you request deletion of your intake data, we generate a DELETION_RECEIPT.md \u2014 a structured document confirming what input data was received, what was deleted, what minimal metadata was retained, and the timestamp of deletion. Deletion receipts are process records, not cryptographic deletion certificates.', meta: { updated: 'Available on request', visibility: 'Public Knowledge' } }, { category: 'INTAKE BOUNDARY', icon: '\uD83D\uDEAB', title: 'Should I send secrets or credentials?', body: 'No. You must not send secrets, production credentials, private repository URLs, API keys, passwords, or customer data dumps. The intake form does not have fields for these. If you include secret-like values, the intake will be rejected. Launch Ark is designed to work with minimal, structured, high-level project descriptions.', meta: { updated: 'Hard rule', visibility: 'Public Knowledge' } }, ], product: [ { category: 'SERVICE TYPE', icon: '\uD83E\uDD1D', title: 'Is this consulting?', body: 'No. Launch Ark is an async-first documentation product, not consulting. There are no discovery calls, no advisory sessions, and no ongoing relationship. You provide a structured project description; we assemble a bounded package from it. Scope and price are confirmed by email before proceeding.', meta: { updated: 'Product definition', visibility: 'Public Knowledge' } }, { category: 'PROCESS', icon: '\uD83D\uDCDE', title: 'Do I need a call?', body: 'No calls are required or offered at this stage. The entire process is async-first: you submit a project description, we validate it, confirm scope and price by email, and deliver the package. If your project needs a discovery call to define scope, it may not be the right fit for Launch Ark in its current form.', meta: { updated: 'Active process', visibility: 'Public Knowledge' } }, { category: 'ACCESS BOUNDARY', icon: '\uD83D\uDD11', title: 'Do you need access to my repository?', body: 'No. We do not require, request, or accept private repository access, production system credentials, or deployment pipeline access. The intake is based on a structured high-level description you provide. If a fact cannot be confirmed from your intake, it is recorded as a gap \u2014 not assumed.', meta: { updated: 'Hard boundary', visibility: 'Public Knowledge' } }, { category: 'PACKAGE SCOPE', icon: '\uD83D\uDCE6', title: 'What is included in a Launch Ark package?', body: 'Depending on the selected package tier, the bundle may include: SYSTEM_OVERVIEW.md, ARCHITECTURE_SKETCH.md, SECURITY_BASELINE.md, DATA_MAP_AND_PII.md, ACCESS_AND_ROLES.md, BACKUP_RESTORE_PLAN.md, RELEASE_CHECKLIST.md, RUNBOOK_BROKEN_DEPLOY.md, RUNBOOK_SERVICE_UNAVAILABLE.md, EMERGENCY_CONTINUITY_STEPS.md, ARK_GAPS_REPORT.md, and DELETION_RECEIPT.md. Not all modules are included in every tier.', meta: { updated: 'Current spec', visibility: 'Public Knowledge' } }, { category: 'GAPS POLICY', icon: '\uD83D\uDD0D', title: 'What happens to unknowns?', body: 'Unknowns stay visible. If a required field is missing, ambiguous, or contradictory in your intake, it is rendered as a clearly marked placeholder in the relevant document \u2014 not filled with invented content. Every package includes an ARK_GAPS_REPORT.md that explicitly lists all gaps. The gap report is a feature, not a failure.', meta: { updated: 'Core behavior', visibility: 'Public Knowledge' } }, { category: 'GAP REPORT', icon: '\uD83D\uDCCB', title: 'What is the ARK_GAPS_REPORT?', body: 'The ARK_GAPS_REPORT.md is a structured document included in every package. It lists every field that was missing, ambiguous, contradictory, or unverifiable in your intake. For each gap, it records: what was expected, what was found, the assessed risk, and the recommended next action. It is the most important document in the package for planning purposes.', meta: { updated: 'Core output', visibility: 'Public Knowledge' } }, ], commercial: [ { category: 'SCOPE BOUNDARY', icon: '\uD83D\uDD10', title: 'Is this a security audit?', body: 'No. Launch Ark produces a SECURITY_BASELINE.md that maps known security configurations from your intake. It does not perform penetration testing, vulnerability scanning, code review, or any active security assessment. It does not certify your application as secure. Security gaps are surfaced, not resolved.', meta: { updated: 'Hard boundary', visibility: 'Public Knowledge' } }, { category: 'SCOPE BOUNDARY', icon: '\uD83D\uDCDC', title: 'Is this compliance certification?', body: 'No. Launch Ark does not certify compliance with any standard (SOC2, ISO 27001, GDPR, HIPAA, or other). It produces structured documentation that can support compliance preparation \u2014 but the documentation itself is not a certification, not a formal audit, and not a legal compliance record.', meta: { updated: 'Hard boundary', visibility: 'Public Knowledge' } }, { category: 'SCOPE BOUNDARY', icon: '\uD83D\uDE80', title: 'Does this make my app production-ready?', body: 'No. Launch Ark documents your current project state \u2014 including its gaps. It does not implement fixes, deploy infrastructure, upgrade security, or resolve the issues it surfaces. A project with a large gaps report is better documented, not more production-ready. Acting on the gaps report is your responsibility.', meta: { updated: 'Hard boundary', visibility: 'Public Knowledge' } }, { category: 'PAYMENT STATUS', icon: '\uD83D\uDCB3', title: 'Is payment active?', body: 'Payment and checkout are not yet enabled. All current requests are handled manually through the concierge pilot process. We confirm scope and price by email before any payment is discussed. You will never be charged before you agree to the final scope. No payment provider scripts are active on this site.', meta: { updated: 'Current state', visibility: 'Public Knowledge' } }, { category: 'DELIVERY STATUS', icon: '\uD83D\uDCEC', title: 'Is delivery active?', body: 'Customer delivery is not yet authorized as a fully automated process. The current pipeline has passed synthetic end-to-end validation. Live customer intake, payment, and delivery remain separate gates that have not yet been opened. Pilot requests are handled manually on a case-by-case basis.', meta: { updated: 'Current state', visibility: 'Public Knowledge' } }, { category: 'PIPELINE EVIDENCE', icon: '\u2699', title: 'What does synthetic pipeline validation mean?', body: 'The generation pipeline (intake validation \u2192 template mapping \u2192 gap detection \u2192 Markdown assembly \u2192 ZIP export) has been tested end-to-end using synthetic, fictional project data \u2014 not real customer data. This is internal quality evidence that the pipeline works as designed. It is not authorization to process real customer data, take payment, or claim live delivery readiness.', meta: { updated: 'Technical boundary', visibility: 'Public Knowledge' } }, ], }; const FAQTrustPage = ({ navigate }) => { const [activeCategory, setActiveCategory] = useState('security'); const getArticles = () => { const lang = window.CURRENT_LANG || 'EN'; if (lang === 'EN') return CANON_ARTICLES_EN; return (window.CANON_FAQ_ARTICLES && window.CANON_FAQ_ARTICLES[lang]) || CANON_ARTICLES_EN; }; const trustMetrics = () => [ { icon: '\uD83D\uDEE1', badge: S.tm1_badge, badgeColor: T.accent, title: S.tm1_t, body: S.tm1_b, borderColor: T.accentDim }, { icon: '\u2713', badge: S.tm2_badge, badgeColor: T.teal, title: S.tm2_t, body: S.tm2_b, borderColor: 'oklch(48% 0.13 195)' }, { icon: '\u25cb', badge: S.tm3_badge, badgeColor: T.muted, title: S.tm3_t, body: S.tm3_b, borderColor: T.border }, { icon: '\uD83D\uDCC4', badge: S.tm4_badge, badgeColor: T.muted, title: S.tm4_t, body: S.tm4_b, borderColor: T.border }, ]; const categories = () => [ { id: 'security', label: S.fcat1, icon: '\uD83D\uDEE1' }, { id: 'product', label: S.fcat2, icon: '\uD83D\uDCCB' }, { id: 'commercial', label: S.fcat3, icon: '\uD83C\uDFDB' }, ]; return (
{S.tc_sub}
{m.body}
{S.fcon_b}
{art.body}
{art.quote && ({art.quote})}
{S.fc_sub}