CAPTCHA: make OSINT domain servers opportunistically use captcha.solve #172
Labels
No labels
bug
design
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/starintel-auto-research#172
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Adopt the approved CAPTCHA Domain Server across OSINT domain servers and actors that can encounter web challenges.
The integration is optional at runtime. A caller should use
captcha.solvewhen the domain server is registered, healthy, authorized, and supports the exact challenge. The CAPTCHA service must not become a hard startup dependency.Init-file policy
Whether a caller automatically invokes
captcha.solveis controlled by the normal StarIntel init/config file through the CAPTCHA domain-server configuration.Callers must honor at least:
Callers must not embed provider preferences or private-solver knowledge. They delegate policy resolution to
CaptchaDomainServer.Initial caller families
Apply the pattern where relevant to:
Do not add a provider-specific dependency to these callers.
Required caller behavior
captcha.solvethrough the capability/domain-server registryDomain server unavailable or disabled
If the CAPTCHA Domain Server is disabled by init, missing, unhealthy, unauthorized, or has no matching solver:
notFoundblockedByChallenge,unsupportedChallenge, orpartialresult as appropriateStarLang requirements
Prefer expressing this as reusable StarLang continuation/orchestration semantics rather than duplicating Common Lisp control flow in every actor.
Required primitives include:
If StarLang lacks one, open/implement the StarLang gap before introducing an ad-hoc Python controller.
Private solver boundary
Callers know only the public
captcha.solvecontract. They must not know whether the selected implementation is NoneCap, NopeCHA, 2Captcha, another public adapter, or the private in-house solver.The private in-house solver remains non-OSS.
Design authority:
roam/design/star-server/STAR-CAPTCHA-002-domain-server-repository-boundary.org.