Manifests and linked wallets
Manifest generation
Optional AI-assisted manifest generation in the dev portal:
- Requires source content first (GitHub fetch and/or upload).
- Safety screening runs on the source before any model call.
- Output is validated against protocol rules before it is accepted.
- Cooldowns limit how often you can regenerate.
- Repeated abusive input can lock generation for a period; use Support if the UI says the account is restricted.
The active model and limits are set per deployment. Operators configure them; integrators should follow whatever the live portal exposes.
GitHub source fetch
The portal can pull source from GitHub server-side instead of relying only on a pasted link—use the in-app flow. For high-risk releases, still review manifests manually; deep Git provenance checks may not cover every edge case.
Linked wallets
Wallet linking uses a short-lived signing challenge: you connect a wallet, sign once, and the portal stores the verified link. That prevents trivial address spoofing compared to typing an address by hand.
Drafts and pricing snapshots
Drafts keep a category and complexity so quotes stay reproducible. When you pay or submit, a pricing snapshot may be stored so operators and auditors can see why a price applied later.
Support and human intervention
- Support threads let you talk to operators from the dashboard.
- Human intervention may appear on a submission when category policy allows escalation (for example after retries are exhausted).