Platform access

Start with a new app, an existing repo, or one reviewable PR.

The first conversation is about scope: the product to create, the codebase to continue, or the finding to fix. Do not include source code, credentials, or secrets in this form.

Create a new appStart from a product brief and return a full-stack app scaffold, preview, tests, and governed PR history.

Fix one active findingStart from a scanner, GRC, or policy finding and return a patch PR with evidence.

Open one build PRTurn a bounded product task or spec into a reviewable CI-backed PR.

Review the repo boundaryValidate permissions, secrets, egress, merge policy, and evidence requirements first.

Babysit a foreign PRUse Boetica to inspect, test, repair, and explain a PR opened by someone else.

Scope review

Confirm whether the first path starts from a blank product brief, an existing repo, a security finding, or a live PR.

First governed artifact

Create the app scaffold or run one build/remediation task, then review the diff, checks, policy state, preview, and rollback note.

Evidence packet

Inspect hash, timestamp, reviewer state, CI result, and control-family mapping where relevant.

Publish only with approval

Customer artifacts and logos are never implied. They publish only when the customer approves them.

Production submissions require a durable backup sink. If backup is missing, the API refuses the request instead of accepting it silently.

NameThe name we should use in the first review.Work emailNo mailing list import without consent.CompanyHelps us understand the operating context.RoleEngineering, AppSec, compliance, or founder roles are all valid.Repo hostChoose the source-control system for the new app or existing repo.First proof pathThe first artifact we should make concrete.UrgencyHelps us understand why now.

What should Boetica prove first?Do not include secrets, credentials, or proprietary code in this public form.Boetica may contact me about platform access and retain this request for evaluation under the privacy and retention pages.

Tell us the first product or workflow worth proving. Access is discussed only after scope is clear.