01
Public destinations only
Local, private, reserved, credential-bearing, and unsafe network targets are blocked.
Trust Center
Permission, evidence, and reversibility are product features.
Genesis Code Doctor AI is designed to make its access boundary, certainty, data source, risk, and action authority visible before a customer relies on a result.
Read-only means read-only.
02
Limited crawl surface
Redirects, page count, response size, time, and anonymous frequency are bounded.
03
No private inference
A public link never proves account ownership or unlocks private source code, analytics, messages, or customer records.
04
Minimum permission
Connections use official authorization flows and the least access required for the selected service.
05
Private by default
Authenticated diagnostics, artifacts, billing, and uploaded code are excluded from public discovery.
06
Human approval gates
Production, payment, authentication, customer-data, DNS, infrastructure, and destructive changes require explicit authority.
A repair is not complete when code is merely generated.
- Root cause and affected surface are documented.
- Approved requirements and protected journeys are checked.
- Tests, limitations, and failed checks are retained.
- Artifacts are versioned and checksummed where supported.
- Rollback instructions accompany implementation packages.
- Before-and-after tests use comparable conditions.
Security-sensitive material stays out of the public forum.
Do not post secrets or exploit details publicly
Passwords, API keys, tokens, private customer data, proprietary code, exploitable production details, and security reports belong in restricted diagnostic or support channels. The public community provides reporting and quarantine workflows; it never executes untrusted uploads on the production application server.
This website is still in controlled build and test.
Final pricing, refund eligibility rules, live payment processing, legal terms, external platform permissions, security certification claims, and production publication require separate approval and verification. Interfaces must describe those dependencies honestly until they are complete.