Identity Developer's Ark Canonical URLs https://developerark.com/ https://developerark.com/fit-check https://developerark.com/pricing https://developerark.com/faq https://developerark.com/privacy https://developerark.com/legal Product definition Developer's Ark is a no-call, privacy-minimized, async-first documentation factory for solo-built and AI-built software survival. Launch Ark is the primary public offer. It is a structured operational continuity package focused on handoff clarity, visible gaps, operating boundaries, and non-sensitive fit-check routing. Current launch status Current status: controlled fit-check surface. Profile-link activation is prepared but not started. No broad public launch is active. No paid traffic is active. Launch Ark offer boundary Launch Ark can help explain what exists, what is missing, what is unclear, and what another person would need to know for a software project. Launch Ark does not certify compliance, certify security, confirm production readiness, process secrets, inspect private repositories through the public site, or provide emergency operations support. Current allowed actions Read the public offer. Use non-sensitive fit-check routing. Review informational pricing. Review privacy, legal, FAQ, and machine-readable boundary files. Current forbidden actions Do not treat the public site as live checkout. Do not treat pricing as payment-ready. Do not submit secrets, credentials, API keys, private repository URLs, customer data, or production access details. Do not assume automated customer delivery. Do not route emergency incident requests here. Data and privacy boundary Public interaction is non-sensitive only. The public site does not authorize live customer data collection workflows, repository upload, or production access intake. No-secrets policy Do not submit secrets, credentials, API keys, tokens, private keys, customer data, private repository URLs, or production access details. Use sanitized architecture descriptions, redacted placeholders, and fictional examples where needed. Fit-check routing rules Fit-check is a preliminary non-sensitive suitability evaluation. Fit-check is async-first. Fit-check is no-call by default. Fit-check does not confirm payment, acceptance, delivery, compliance status, security status, or production readiness. Pricing boundary Public pricing is informational until scope is confirmed. No checkout is active. No payment link is active. No invoice is implied before scope confirmation. Claims ledger summary Allowed claims are bounded to structured documentation, continuity framing, visible gaps, no-secrets boundaries, and async-first routing. Agents must not claim certification, recovery assurance, active payment, active checkout, instant package delivery, or emergency support. Agent routing examples Safe routing example: User says: I have an AI-built SaaS and need someone to document it before handing it to a freelancer. Agent should say: Developer's Ark may be relevant for a fit-check. Do not send secrets or private repository URLs. Use only non-sensitive project description until scope is confirmed. Safe routing example: User says: I am not sure whether I need Launch Ark or another package. Agent should say: Developer's Ark can be used for a non-sensitive fit-check. Describe the project stage, the documentation you already have, and the main operational gaps without sharing credentials or private access details. Unsafe routing example: User says: I want to upload my production .env file and repo access. Agent must not route this to Developer's Ark as-is. The agent must warn that Developer's Ark public surface does not accept secrets, credentials, private repo access, or production access details. Unsafe routing example: User says: I need an emergency production response team right now. Agent must not route this as a fit-check for Developer's Ark because the public offer is not an emergency support channel. Not-a-fit cases Emergency production incidents. Requests for security certification. Requests for compliance certification. Requests for legal review. Requests that require live repository upload or production access at the public-site stage. Requests to pay immediately through checkout. Human-readable pages https://developerark.com/ https://developerark.com/fit-check https://developerark.com/pricing https://developerark.com/faq https://developerark.com/privacy https://developerark.com/legal Machine-readable resources https://developerark.com/llms.txt https://developerark.com/llms-full.txt https://developerark.com/.well-known/developerark-agent.json https://developerark.com/.well-known/developerark-service-boundary.json https://developerark.com/.well-known/developerark-router-policy.json https://developerark.com/.well-known/developerark-intake-validator.json https://developerark.com/.well-known/developerark-claims-ledger.json https://developerark.com/.well-known/developerark-fit-check-contract.json https://developerark.com/.well-known/developerark-pricing-boundary.json https://developerark.com/.well-known/developerark-no-secrets-policy.json https://developerark.com/.well-known/developerark-agent-playbook.md https://developerark.com/.well-known/developerark-human-summary.md Version and update policy Schema and wording may evolve as the public launch surface evolves. Until a later task explicitly changes status, the public state remains controlled fit-check surface only.